A UTM naming convention that only works if everyone remembers every rule, perfectly, on the fortieth campaign of the year, doesn't actually work. Here's a structure built around what people realistically forget, not what a style guide hopes they'll remember.
The rules themselves are rarely the problem — most teams can agree on a sensible structure in a single meeting. What breaks it is drift: a new hire who never saw the original doc, a rushed campaign launched at 11pm, an agency partner using their own convention. Six months later, "facebook", "Facebook", and "FB" are all sitting in the same report as three different sources.
| Parameter | Rule | Example |
|---|---|---|
| utm_source | Lowercase, from a fixed short list — never freeform | google, facebook, klaviyo, tiktok |
| utm_medium | Lowercase, from a fixed short list of channel types | cpc, email, social, organic, affiliate |
| utm_campaign | [year]_[initiative]_[detail], all lowercase, underscores only | 2026_summer_sale_mens |
| utm_content | Optional — [placement]_[variant] | carousel_v2, story_ad |
| utm_term | Paid search only — the actual keyword | running shoes |
The single highest-leverage change most teams can make isn't a smarter naming scheme — it's turning utm_source and utm_medium from freeform text fields into a fixed, shared list everyone picks from. A dropdown in a shared campaign-builder spreadsheet, or a simple internal wiki page listing the exact approved values, removes almost all of the casing and spelling drift that causes channels to fragment into duplicates in your reports.
The [year]_[initiative]_[detail] structure is deliberately boring — the goal isn't cleverness, it's that anyone on the team, looking at a report a year from now, can read 2026_summer_sale_mens and immediately know what it was, without needing to ask whoever set it up (who may not even work there anymore by then).
Every downstream report — journey analytics, multi-touch attribution, revenue by channel — is built entirely on top of this tagging data. A naming convention that actually holds up is the cheapest, highest-leverage fix available for almost every attribution accuracy problem a team runs into later.
Conversion tracking and attribution consultant. Spends most days inside Google Tag Manager, GA4, and server-side tracking setups, helping ecommerce and B2B teams figure out where their customers actually came from. More about Abdul →