How to Attribute Signups to a Product Launch
Trace launch signups across channels with consistent campaign links, a baseline, product-use events, and user-reported discovery—while keeping attribution separate from proof of causation.
Decide what you mean by a launch signup
Before sharing a launch link, define the outcome you want to count. A page visit, account creation, first useful action, and paid conversion are different events. Write down the event, counting window, and source of truth so the team does not compare unlike numbers after launch day.
Attribution connects an observed outcome with one or more recorded touchpoints. It can help you compare channels; it cannot prove that a post or directory caused a signup. People may see a post on one device, return through a bookmark, ask a colleague, or use a browser that blocks some tracking.
| Event | Definition to choose | Why it matters |
|---|---|---|
| Landing visit | A human visit to the intended public page | Shows reach, but not intent or signup |
| Signup | One completed account, deduplicated by your own rule | Measures the action the launch announcement invited |
| Activation | The first product-specific useful action | Separates account creation from trying the product |
| Paid conversion | A confirmed payment under the product's billing rules | Measures purchase; keep refunds and trials distinct |
Give each launch channel a consistent campaign link
Use a separate tagged link for each channel or placement when your analytics setup can read it. Keep the destination path stable and test the redirect before posting. Use lowercase, readable names and one naming convention; do not change the product URL or canonical page just to measure a campaign.
| Field | Example | Rule |
|---|---|---|
| utm_source | producthunt | Name the platform or publisher |
| utm_medium | launch | Use a small, consistent channel vocabulary |
| utm_campaign | october-release | Use one campaign name for this launch |
| utm_content | founder-post-a | Use only when comparing distinct placements or creative |
https://example.com/?utm_source=community&utm_medium=launch&utm_campaign=october-releaseRecord a baseline before launch day
Choose a pre-launch period long enough to reflect your normal activity, then record the same events you plan to review after sharing. Include the date range, timezone, tracking configuration, and any known measurement gaps. For a small site, a spreadsheet with daily visits, signups, and first-use actions may be more honest than a complicated attribution model.
Write down the launch time and each material change: new post, email, pricing edit, outage, press mention, or onboarding fix. If several changes happen together, later data will not isolate which one mattered.
Date/time and timezone | Channel | Tagged URL | Visits | Signups | First useful actions | Known gaps | NotesCombine tracked source with what users say
Add an optional, short signup question such as “Where did you first hear about us?” with a few broad choices and an optional free-text answer. Ask only for information you need, tell users why you collect it, and keep it consistent with your privacy notice. Do not require the answer if it creates unnecessary friction.
Tracked campaigns and self-reported discovery answer different questions. A tagged session can show the recorded last visit; a person may report the first place they discovered the product. Keep both fields separate and preserve “unknown” rather than forcing every signup into a channel.
If you want to understand why the person acted, follow up with a neutral question about what they were trying to do, what they use today, and what made them look for a solution. Do not turn one response into a testimonial or universal buying claim.
Compare sources without overstating what the numbers mean
| Pattern | Useful interpretation | What it does not prove |
|---|---|---|
| Visits and signups both rise on one tagged source | That placement is associated with recorded activity | That it alone caused the signups |
| Few tagged visits, but users mention the channel | Some discovery may be untracked or shared elsewhere | That tracking should be bypassed or privacy ignored |
| Visits rise but activation does not | Inspect audience fit and the first-use path | That the channel is worthless from one small sample |
| Many signups appear as direct or unknown | Check redirects, app handoffs, consent, and source retention | That all unattributed users came from the launch |
Use a small decision log after the launch
- Compare equal date windows and separate each channel's tagged traffic.
- Review visits, signups, activation, and paid conversion as separate steps.
- Keep self-reported discovery apart from analytics attribution.
- Show counts and sample sizes; avoid percentage claims based on a handful of users.
- Choose one next action, such as fixing a broken link or clarifying the signup promise, and record when you will review it again.
Frequently asked questions
Can UTM tags track every launch signup? No. Redirects, consent choices, browser settings, cross-device visits, and people sharing links can make attribution incomplete.
Should I credit the last-click channel with the whole signup? Treat last-click as one reporting convention, not causal proof. Keep first discovery, last recorded touch, and user-reported source distinct if each informs a different decision.
How much data do I need before deciding? There is no universal sample threshold for every product. Report raw counts and uncertainty, and treat a small launch batch as directional evidence rather than a stable forecast.
Ready for a pre-launch audit?
Run the public analyzer and get a prioritised report for the URL you are about to share.
Run the SEO audit