The same launch appears as AutumnLaunch, autumn_launch, and fall-promo in three team spreadsheets. The campaign may be one coherent piece of work, but its analytics report becomes three rows. Fixing that after links are distributed is harder than agreeing the names before production.
Google Analytics’ URL-builder guidance says UTM parameters identify which campaigns refer traffic. It describes utm_source as the referrer, utm_medium as the channel type, utm_campaign as the campaign, and utm_content as a way to distinguish creative variants. Google notes that parameter values are case sensitive. This is a naming problem as much as a technical one.
Give each field one job
For a hypothetical autumn opening, the team could agree:
| Parameter | Example value | Rule |
|---|---|---|
utm_source |
instagram |
Name the actual referring platform or publisher consistently |
utm_medium |
paid_social |
Use one agreed channel label across comparable placements |
utm_campaign |
2026_autumn_opening |
Keep the same value for the same launch across channels |
utm_content |
film_15s_a |
Distinguish the exact creative or placement only when useful |
One resulting link might be https://example.com/opening?utm_source=instagram&utm_medium=paid_social&utm_campaign=2026_autumn_opening&utm_content=film_15s_a. The values are an example, not a universal taxonomy. If the business has an established analytics naming scheme, use that instead of creating a parallel one. Google’s current best-practice table recommends one consistent source per platform, a consistent medium per channel, and a single campaign name for the same marketing effort.
Write the registry, then generate links
Keep one shared row per live destination and placement: campaign ID, owner, approved URL, source, medium, campaign, content, start date, and status. Have one person approve new values. Make the field vocabulary short enough that someone can select a value instead of improvising it. If a partner needs a special link, give that partner a documented source name and a tested URL.
Test the full link on a phone and desktop before an ad, email, or QR code is distributed. Confirm the final page is the intended offer, the next action works, and the test visit appears where expected in reporting. A UTM string does not fix a broken landing page or prove the campaign caused a sale. It only carries campaign information into analytics when the measurement setup captures it.
Separate naming from performance claims
A tagged link can tell you that a visit was recorded under a campaign. It cannot by itself tell you whether the customer would have visited or bought without that campaign. Do not turn a report row into a claim of incremental revenue. Save the campaign’s objective and conversion definition next to the naming registry so the team knows which outcome the links are meant to support.
This guide is for pre-launch naming and ownership. If an existing campaign URL began failing after a redesign, use the separate full-URL troubleshooting checklist. ARCHV can create campaign assets and landing pages; analytics setup and ad-account instrumentation should be explicitly included in the project scope when needed.