Google Analytics UTM Parameters: Naming Conventions

Google Analytics UTM Parameters Break Down Without a Naming Convention

A SaaS client came to me in June spending EUR 22,000 per month across Google Ads, Meta, LinkedIn, and email. Their GA4 Source / Medium report had 47 unique source values. Seventeen of those were variations of Facebook: facebook, Facebook, fb, FB, facebook.com, Facebook_Ads, meta, ig, instagram. Each one created a separate row in every report. Their marketing lead was pulling numbers for board decks by manually adding up rows she thought looked like the same channel.

If you have ever built a UTM-tagged URL and thought "close enough," this post is for you. I am not going to explain what UTM parameters are or how the five tags work -- I wrote that in What Are UTM Parameters? The No-Nonsense Guide. This post is about the part that actually breaks: the naming convention, the campaign tracking template, and the governance process that prevents your taxonomy from rotting within six months.

Why Naming Conventions Fail (and When They Fail)

The first three months are never the problem. Somebody sets up a spreadsheet, defines the values, shares it with the team. Everyone follows it because the memory is fresh.

Then a new hire joins and builds a Meta campaign without reading the wiki. An agency tags email links with Email instead of email. A developer adds UTM parameters to an internal promotion banner, restarting sessions and overwriting attribution. Nobody notices because GA4 does not throw an error when your taxonomy drifts -- it just quietly fragments your data.

I call this taxonomy drift, and it follows a predictable arc:

1. Month 1-3: Clean data. The person who built the convention is still enforcing it.
2. Month 4-6: First inconsistencies appear. A new channel launches with values nobody agreed on.
3. Month 7+: The spreadsheet is outdated. Three people use three different naming styles. Reports require manual cleanup before every meeting.

The fix is not more discipline. It is a system that makes the right values the easy values. The rest of this post covers how I build that system around google analytics utm parameters for my clients.

Building a Campaign Tracking Template That Scales

A campaign tracking template is a shared document -- spreadsheet, Notion database, or internal tool -- where every UTM-tagged URL is generated from controlled values. It is the single source of truth for how to use utm parameters across your team.

Here is the structure I set up for clients:

Controlled columns with dropdowns

Lock the values that matter most. Source and medium should never be free-text fields.

Column	Input type	Example values
utm_source	Dropdown	google, facebook, linkedin, newsletter, partner-name
utm_medium	Dropdown	cpc, paidsocial, email, display, social, affiliate
utm_campaign	Structured text	{initiative}-{audience}-{quarter} pattern
utm_term	Free text	Keyword or targeting (paid search only)
utm_content	Free text	Ad variant, creative name, or link placement

The campaign column is structured text, not a dropdown, because campaign names change with every launch. But it follows a pattern: summer-sale-prospects-q3, webinar-retargeting-aug26, brand-awareness-eu-q3. The pattern makes campaigns filterable and sortable in GA4 without requiring a lookup table.

URL output with validation

The template concatenates the base URL and parameters into a complete UTM-tagged link. Add a validation column that flags:

• Any uppercase character in source, medium, or campaign.
• Spaces (which become %20 in URLs and create messy dimension values).
• Missing required parameters (source, medium, campaign).
• Known bad values -- anything not in your approved dropdown list.

Google provides a basic Campaign URL Builder, but it has no validation, no history, and no access control. It is fine for one person. It falls apart for a team. Your campaign tracking template replaces it.

Who owns the template

Assign one person -- typically the analytics lead or the person responsible for reporting -- as the template owner. Their job is not to build every URL. Their job is to review new values, approve additions to the dropdowns, and run a monthly check for rogue values in GA4.

This is the same governance principle I apply to GTM container naming: one owner, documented rules, periodic review.

The UTM Values Cheat Sheet: What to Standardize First

If you only standardize two things, standardize source and medium. These are the dimensions GA4 uses to classify traffic into default channel groups. Get them wrong and traffic lands in "Unassigned" -- invisible to anyone using the standard reports.

Here is the google analytics utm parameters cheat sheet I give to every client:

Source values

Use the platform's root domain name, lowercase. Match what GA4 already assigns to auto-classified traffic.

Platform	utm_source	Why this value
Google Ads	google	Matches GA4's auto-tagging source
Meta (Facebook + Instagram)	facebook	GA4 recognizes facebook for channel grouping
LinkedIn Ads	linkedin	Consistent with organic LinkedIn referrals
Email (any provider)	newsletter or ESP name	Separates email from other owned channels
TikTok Ads	tiktok	Matches GA4's recognized source
X (Twitter) Ads	twitter	GA4 still maps twitter to the social channel group
Partner / affiliate	{partnername}	Lowercase, no spaces, unique per partner

Do not use meta as a source for Facebook Ads. GA4's default channel grouping rules still reference facebook and instagram as recognized source values for the Paid Social channel. Using meta pushes that traffic into Unassigned unless you create a custom channel group.

Medium values

Medium determines the channel group. These are the values GA4's default channel definitions expect:

Channel type	utm_medium	GA4 channel group it maps to
Paid search	cpc	Paid Search
Paid social	paidsocial	Paid Social
Display ads	display	Display
Email	email	Email
Organic social	social	Organic Social
Affiliate	affiliate	Affiliates
Referral partners	referral	Referral
SMS campaigns	sms	SMS

I have seen paid-social, Paid_Social, paid_social, and social_paid across a single account. GA4 treats each of those as a different medium. Only paidsocial (one word, no separator) maps correctly to the Paid Social default channel group without custom rules.

Campaign naming pattern

Campaign names are where teams go creative. Too creative. I enforce a pattern:

{initiative}-{audience}-{quarter}

Examples:

• brand-launch-smb-q3
• retargeting-abandoned-cart-q3
• webinar-data-leaders-aug26

Rules: lowercase, hyphens between segments, no abbreviations that only one person understands. If someone reading the campaign name in GA4 cannot figure out what it refers to without asking, the name is too opaque.

Diagnosing UTM Data in Google Analytics 4

Once your google analytics utm parameters are tagged correctly, the real work is knowing whether they are flowing into GA4 as expected. I use two surfaces for this.

In standard reports, go to Reports > Acquisition > Traffic acquisition and switch the dimension to "Session source / medium." Add "Session campaign" as a secondary dimension. If you immediately spot casing variants like summer_sale and Summer-Sale, your convention is already leaking.

For deeper diagnosis, build an Exploration with Session source, Session medium, and Session campaign alongside your key event metrics. Explorations let you filter and segment by UTM dimensions, which is how I identify attribution gaps during tracking audits.

If your google analytics utm parameters appear correct but traffic still lands in "Unassigned" or "direct / (none)," the cause is usually one of three things: redirect chains stripping query parameters before the landing page loads, consent mode blocking the GA4 request entirely, or a cross-domain tracking gap dropping the parameters during a domain hop.

Preventing Taxonomy Drift: A Quarterly Review Process

Setting up a naming convention is a one-day project. Maintaining it is ongoing. Here is the process I recommend -- and the one I run for retainer clients.

Monthly: automated scan

Export your GA4 Source / Medium report for the past 30 days. Sort by sessions. Look for:

• New source values you did not approve. Someone tagged a URL with a source that is not in your template.
• Casing mismatches. Filter for uppercase characters.
• One-off values with fewer than 10 sessions. These are usually typos or one-time tags from an agency.

If you are comfortable with BigQuery, query the traffic_source fields in your GA4 BigQuery export to detect rogue values programmatically instead of eyeballing reports.

Quarterly: full reconciliation

Compare your campaign tracking template against GA4. Every source, medium, and campaign value in GA4 should trace back to a row in your template. Values that do not trace back are either unauthorized (fix the process) or legitimate additions that were never documented (update the template).

This is also when I update the dropdown values in the template. New channels launch. New partners come on board. The template is a living document, not a set-and-forget artifact.

When to call for help

If, in my experience, your quarterly review reveals more than 15 percent of traffic arriving with non-standard UTM values -- or if "direct / (none)" accounts for more than 30 percent of sessions and you know those visitors came from tagged channels -- you likely have a systemic problem beyond naming conventions. It could be redirect chains stripping parameters, consent configuration suppressing data, or platform-level tagging failures. That is the kind of diagnostic work I do in a tracking audit engagement.

Common Mistakes That Wreck Your UTM Taxonomy

I covered the most common UTM tagging errors in the UTM basics guide. Here are the governance-specific mistakes I see repeatedly:

Letting agencies tag independently. If your performance agency uses fb while your email agency uses facebook, your data is fragmented from day one. Share your campaign tracking template with every vendor and make it a deliverable requirement.

No versioning on the template. Someone changes a dropdown value, and last month's tags now point to a value that does not exist in the current version. Use a spreadsheet with version history or a tool that logs changes.

Tagging everything, including what should not be tagged. UTMs on internal links restart sessions in GA4 and overwrite the original traffic source. UTMs on Google Ads links override auto-tagging and can break Google Ads reporting in GA4. Know when not to tag.

Ignoring how UTMs flow into downstream tools. Your CRM captures the last UTM on a form submission. Your attribution model reads source and medium as inputs. If those values are messy, every system downstream inherits the mess. Clean google analytics utm parameters are not just a GA4 concern -- they are a data infrastructure concern.

FAQ

Not sure your UTM data is trustworthy? Get in touch -- I will tell you exactly what is broken and what to fix first.