This is the whole path: sign up, create a project, answer three questions about what success looks like, add the tracker, watch your events arrive live, go live.

Create an account at launchpulse.dev. The trial is 14 days and doesn’t ask for a card.

2. Create a project

A project is one product or site. You’ll be asked for three things:

Field	Notes
Product name	Required. Whatever you call it.
Website URL	Required. The host of this URL becomes your primary domain — it can’t be removed later, so use the real production domain.
Timezone	An IANA zone, defaulted to your browser’s. This is the day boundary for every chart.

Creating the project is step 1 of a 6-step onboarding rail. The next steps set up what you’re measuring.

3. Say what success looks like

Step 2 — “What does success look like?” Pick the moment that means someone chose you. Each option suggests an event name:

Your goal	Suggested event
Create an account	`account_created`
Buy something	`purchase_completed`
Book something	`booking_confirmed`
Join a waitlist	`waitlist_joined`
Submit a lead	`lead_submitted`
Something else	you name it

There’s also “Just watch traffic for now.” That skips straight to the install step with no conversion configured. Pageviews still work. You can come back to this later.

Step 3 — “How will we know it happened?” Two ways to detect the conversion: an event your app sends, or a page the user reaches (a thank-you page like /thank-you is the classic). If LaunchPulse has already seen event names from your site, they appear as chips you can click to fill the field.

Step 4 — “And when do they get real value?” This is the first-value event — the aha moment, after the conversion. First project created, first invoice sent, first booking received. If your product doesn’t have a meaningful step past conversion, click “Conversion is enough for this product” and move on.

4. Add the tracker

Step 5 — “Add the tracker.” Pick your platform from the dropdown and you get the exact snippet, a copy button, and a hint about where to paste it. There’s also a collapsible “Prefer an AI agent? Copy a ready-made prompt” if you’d rather hand the job to a coding agent.

For a plain HTML site, the snippet is:

<script src="https://collector.launchpulse.dev/lp.js"></script>
<script>LaunchPulse.init("lp_pub_yourkey");</script>

Or with npm:

npm i @basekick-labs/launchpulse

import { LaunchPulse } from "@basekick-labs/launchpulse";

if (typeof window !== "undefined") LaunchPulse.init("lp_pub_yourkey");

Your public key starts with lp_pub_. It’s designed to ship in client code — putting it in your HTML is safe and expected.

Full per-platform instructions are in Installation.

5. Test your signal

Step 6 — “Test your signal.” This is a live debug view. Open your site in another tab and do the thing.

A journey checklist lights up green as each signal arrives:

Pageview — fires automatically on init.
Your conversion event
Your first-value event

Below it, a live log shows the last 20 events, with conversions in orange and first value in green.

It also catches two common mistakes:

First value arrived before conversion. The order is wrong — usually the events are mapped backwards.
First-value event arrived with no user_id. You didn’t call identify() before sending it, so LaunchPulse can’t tie it to the person who converted.

6. Go Live

When the checklist looks right, press Go Live.

This matters more than it sounds: while a project is in setup status, events are never stored. The collector routes them to the debug stream only. Your real data starts at Go Live. See Going live for what that switch does and what can block it.

What’s next

Installation — every supported platform.
Going live — setup vs. live, and debug mode on staging.

Quickstart