UTM Naming Conventions: The One Rule for Clean Analytics

You've set up UTM tracking. Your team is tagging links. The data is flowing into Google Analytics. And then you open your campaign report and see five different rows for the same email campaign because of inconsistent spelling and capitalization.

This is the UTM naming convention problem — and it quietly ruins analytics for thousands of marketing teams every single day. This guide will show you how to fix it, prevent it, and build a system that keeps your campaign data clean no matter how many people are building links.

Why Naming Conventions Matter More Than You Think

UTM parameters are case-sensitive and exact-match. Your analytics platform doesn't know that Facebook and facebook are the same thing. It treats them as two completely different traffic sources.

When your data is fragmented, you undercount channel performance, make budget decisions based on incomplete numbers, and your attribution models break down. The fix isn't technical; it's organizational.

The One Rule: Always Lowercase, Always Consistent

If you implement nothing else from this guide, implement this: Every UTM parameter value must be lowercase, with no spaces, and spelled the same way every time.

❌ Avoid

utm_source=Facebookutm_medium=Paid Social

✅ Standardize

utm_source=facebookutm_medium=paid_social

Step 1: Define Your Standard Values

Start by listing every possible value you'll use for utm_source and utm_medium. These should be finite, controlled lists — not freeform fields.

Channel Type	Standard Medium Value
Paid Search	`cpc`
Paid Social	`paid_social`
Organic Social	`social`
Email Marketing	`email`

Step 2: Establish a Campaign Naming Format

Campaign names are where the most inconsistency happens. A good format balances being descriptive with being readable.

Recommended Format:

[type]_[description]_[month][year]

Example: email_welcome_series_jan2026

Step 3: Document in a Style Guide

Write your rules down. A UTM style guide should include your core rules, approved source/medium values, and examples of correct vs incorrect usage. Keep this document central and mandatory for all team members.

UTM Naming Convention Template

UTM NAMING CONVENTION — [COMPANY NAME]

CORE RULE: All UTM values must be lowercase, no spaces.

APPROVED SOURCES:
- google (Google Ads)
- facebook (Facebook Ads)
- newsletter (Email list)

APPROVED MEDIUMS:
- cpc (Paid search)
- paid_social (Paid social ads)
- social (Organic posts)
- email (Email campaigns)

CAMPAIGN FORMAT: [type]_[desc]_[date]
Example: email_promo_may2026

How to Enforce Conventions

Documentation helps, but it doesn't prevent every mistake. Use a centralized builder like our Free UTM Builder Tool to ensure everyone starts from the same clean foundation.

Additionally, create a pre-launch checklist for campaigns that requires a UTM audit before any link goes live.

Frequently Asked Questions

Why should I use underscores instead of spaces in UTMs?

Spaces in URLs are encoded as %20 or +, which can be handled inconsistently by different browsers, platforms, and analytics tools. Underscores (_) or hyphens (-) are standard URL-safe characters that ensure your values are read correctly everywhere.

Are UTM parameters case-sensitive?

Yes. Google Analytics treats 'Email', 'email', and 'EMAIL' as three completely different mediums. This is why a 'lowercase only' rule is the single most important part of any naming convention.

How do I fix historical messy UTM data?

You can't change data already collected in Google Analytics, but you can use 'Custom Channel Groupings' in GA4 to map inconsistent values (like 'fb' and 'facebook') into a single bucket for your reports.

What is the best format for campaign names?

A common and effective format is [type]_[description]_[date], such as 'email_summer_sale_june2026'. This ensures the campaign is easily identifiable and sortable in your reports even months later.

Build Clean Tracking Links

Ready to implement your naming convention? Use our free tool to generate clean, validated UTM links for your team.

Go to UTM Builder →