Product launch campaign tracking
A product launch spans many channels at once. This page shows how to use a single utm_campaign across all of them while varying utm_source per channel, so you get a clean total for the launch and a per-channel breakdown without fragmenting the campaign.
One campaign, many sources
Fix the utm_campaign string once and use it on every launch link, then vary only utm_source (and medium) per channel. This is what makes the launch aggregate while staying breakable by channel:
- utm_campaign=<one launch name, e.g. v2-launch> on every link
- utm_source=email / linkedin / x / youtube … per channel
- utm_medium matching each channel (email, social, paid)
- utm_content=<optional, for variants within a channel>
Clean rollup discipline
The rollup only works if the utm_campaign string is byte-for-byte identical everywhere. If one team writes v2-launch and another writes V2_Launch, the launch splits into two campaigns and the total is wrong. Distribute the exact strings before launch day and treat them as fixed.
Keep utm_source values drawn from your documented allow-list so each channel lands in the right bucket, and reserve utm_content for variant testing rather than channel identity.
How it appears in analytics and logs
Every launch visit shares one utm_campaign, so summing it gives the true launch total. The varying utm_source tells you which channel each visit came from within that total.
Diagnostic use case
Coordinate a multi-channel launch under one utm_campaign so every channel rolls up into a single launch total with a per-source breakdown.
What WebmasterID can help detect
WebmasterID reads the shared utm_campaign and per-channel utm_source at ingest, so a launch appears both as one rollup and as a channel breakdown without manual log stitching.
Common mistakes
- Different teams writing the launch campaign name slightly differently, splitting the rollup.
- Encoding the channel in utm_campaign instead of utm_source, breaking the total.
- Adding personal data while coordinating across many contributors.
Privacy and accuracy notes
Keep launch UTM values to generic campaign and channel labels. No personal data in any parameter, even when coordinating across many teams. UTM values are public and logged.
Related pages
- UTM naming conventions that survive reporting
Most UTM data problems are naming problems. Because tools treat utm_source=Reddit and reddit as different values, inconsistent casing and spelling fragment one campaign across many rows. This page gives a convention — lowercase, hyphenated, documented allow-list — that keeps reports clean.
- UTM parameters explained: the five tags and how to use them
UTM parameters are query-string tags you add to a link so analytics can attribute the visit to a campaign even when the referrer is missing. This page explains the five tags, a consistent naming convention, and the hard rule that UTM values are public — so they must never contain personal data or secrets.
- Campaign links (docs)
Distribute one consistent campaign name across channels.
Sources and verification notes
- MDN — URL search paramsA shared utm_campaign string aggregates across channels.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.