UTM Parameters Done Right: A Naming System That Survives
Five parameters, free text, zero validation. That is the whole UTM standard, and it is why a site with three people touching links ends up with google, Google, GOOGLE, google.com and google / organic as five separate rows in the same report. Merging those rows by hand every Monday is not analysis, it is janitorial work.
The system below fits on an index card and holds up to a few hundred campaigns before it needs a database instead of a spreadsheet.
What each of the five parameters is allowed to mean
Every analytics tool reads the same five keys: utm_source, utm_medium, utm_campaign, utm_term, utm_content. Nothing validates them. So the team has to.
- source — the specific place the click came from:
newsletter,linkedin,partner-blog-name. Not "social", not "email". The medium carries the category. - medium — the channel type and only that:
email,social,cpc,referral,display. Any value outside the default list lands in "Unassigned" in channel grouping. That bucket is where campaigns go to become invisible. - campaign — one initiative per launch:
2026-q4_black-friday. - term — paid keyword only. Empty for everything else. Filling it "just in case" creates a column nobody queries.
- content — the variant: which button, which placement, which creative.
hero_cta-a,footer_text-link.
Two rules follow from this. Source and medium never overlap in meaning, and campaign never encodes placement. Once those boundaries blur, every report becomes an argument about definitions instead of a decision.
A convention that survives a marketing team
- Lowercase everything, always. Analytics is case-sensitive.
- Hyphens between words, never spaces. If you use underscores, use them only inside the campaign period prefix — pick one style and never mix it.
- No dates inside source or medium.
newsletter-2026-11as a source fragments one channel into twelve rows a year. - Campaign name = period plus theme:
2026-q4_black-friday. Sortable, filterable, readable six months later. - Content = placement plus variant:
hero_cta-a. Two dimensions, one string, no ambiguity.
Build links through the same generator every time. The UTM builder keeps the five fields in the right order and encodes them, which removes the most common hand-editing bug: a campaign name containing an ampersand that silently truncates everything after it. When a campaign name is typed by hand from a Slack message, run it through text to slug first — you get lowercase and hyphens for free, and the value is identical to the one in the tracking sheet.
Four mistakes that quietly break attribution
1. Case and whitespace drift
utm_source=Newsletter and utm_source=newsletter are different values in every analytics tool. So are paid-social and paidsocial. Two people, two keyboards, two rows. After a year of campaigns you are reconciling a dozen variants by hand, and the weekly email takes an hour before anyone reads a number. Catch it before publishing: paste the query string into a regex tester with [A-Z] and %20 as patterns. Two matches means the link is not ready.
2. Internal links carrying UTMs
A link in your own footer to /pricing?utm_source=newsletter&utm_medium=email starts a new session attributed to email every time someone clicks it. Direct traffic drops, email inflates, and whoever reads the report concludes that email is outperforming. Never tag internal links. Tag only links that arrive from outside your domain, and add your own domain to the referral exclusion list so your payment provider and your own subdomains do not appear as traffic sources.
3. Encoding and truncation
A raw space in ?utm_campaign=q4 sale becomes %20 in one tool and + in another; some CRMs decode those differently and you get two campaign names from one link. A raw & splits the string: utm_campaign=q4&clearance sends utm_campaign=q4 and a stray parameter called clearance. Encode every value with the URL encoder before it goes into the builder. And mind the fragment: /page?utm_source=x#pricing is valid, /page#pricing?utm_source=x is not — browsers never send anything after # to the server, so the tags vanish and the click looks direct.
4. Dynamic or personal values
utm_content=user-88213 or, worse, an email address. This produces one row per user, which destroys every aggregate view, and it writes personal data into access logs, CDN logs, and the referrer headers of third-party scripts. That is a GDPR problem with a support ticket attached. UTMs are categorical, not identifiers. Order IDs and click IDs belong in your own parameters, never in the five standard ones.
Redirects eat parameters
A 301 to the canonical URL without the query string drops every tag. A chain like http to https to www is three chances to lose them, and most servers preserve the query string while some rewrite rules do not. Test the exact tagged URL, not the clean one, and follow the chain to the final destination. If the final URL has no utm_ in it, the campaign will report as direct traffic and nobody will notice for a month.
Governance for a small team
- One source of truth: a sheet with three lists — allowed sources, allowed mediums, live campaigns. Ten rows, edited by one person.
- Check before publish, not after: uppercase, spaces, ampersand, internal link, redirect. Five checks, thirty seconds.
- Monthly audit: sort source and medium by sessions and look for rows you did not create. Every new row is either a deliberate campaign or a typo. There is no third option.
- Watch the untagged bucket. A rising share of direct and "not set" traffic usually means someone shipped an untagged link, not that brand awareness grew.
Why an hour of conventions pays for itself
If ten percent of sessions carry inconsistent tags, every comparison you make is wrong by an unknown amount. You cannot tell a fifteen percent lift from a naming error, and the fix costs an afternoon of conventions plus half a minute per link. The alternative is a dashboard that looks precise and answers nothing — the most expensive kind, because people trust it.
Write the card, put the builder next to it, and check the link before it goes out. The quarter closes whether or not your data is readable.