Attribution
Sign up free
Tracking

UTM Naming Conventions: A Template Your Whole Team Will Actually Follow

Blog Tracking UTM Naming Conventions: A Template Your Whole Team Will Actually Follow
Abdul Kayium
Abdul Kayium
Tracking & attribution consultant
6 min read

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.

Why most naming conventions quietly fall apart

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.

A template built to survive that drift

ParameterRuleExample
utm_sourceLowercase, from a fixed short list — never freeformgoogle, facebook, klaviyo, tiktok
utm_mediumLowercase, from a fixed short list of channel typescpc, email, social, organic, affiliate
utm_campaign[year]_[initiative]_[detail], all lowercase, underscores only2026_summer_sale_mens
utm_contentOptional — [placement]_[variant]carousel_v2, story_ad
utm_termPaid search only — the actual keywordrunning shoes

Why "a fixed short list" matters more than the exact rule

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.

Making utm_campaign actually readable six months later

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).

What to explicitly avoid
Dates that aren't the year alone (full dates make campaign names hard to group later), spaces (get URL-encoded into unreadable %20 sequences), mixed casing, and internal jargon or abbreviations that won't mean anything to someone outside the team that launched the campaign.

Getting a whole team to actually follow it

Why this is worth the upfront discipline

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.

Frequently asked questions

What's the biggest mistake in UTM naming conventions?
Leaving utm_source and utm_medium as freeform text fields instead of a fixed, shared list. That's what causes the same channel to fragment into multiple differently-spelled or differently-capitalized versions in reports over time.
Should UTM campaign names include the full date?
Generally no — a full date makes campaigns hard to group by year or initiative later. Including just the year, followed by a readable initiative name, tends to age much better in reports.
How do I get a whole marketing team to follow the same UTM convention?
Write the convention down somewhere accessible, provide a shared tool (a spreadsheet with dropdowns or a link builder) rather than relying on manual typing, and spot-check new campaigns periodically, especially in the weeks right after rolling the convention out.
Are UTM parameters case-sensitive?
Most analytics platforms treat them as case-sensitive, meaning 'Facebook' and 'facebook' are read as different values. Standardizing on lowercase for every UTM value is the simplest way to avoid this becoming a problem.
Written by Abdul Kayium

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 →

Related reading

← Back to all articles