Lowercase UTM enforcement
UTM parameter values are case-sensitive in most analytics tools, so Email, email, and EMAIL count as three separate sources. Enforcing lowercase at the point links are created is the simplest way to stop a report from fragmenting into near-duplicate rows. This page covers why casing matters, where to enforce it, and how to clean up an existing mess.
Why casing fragments reports
Most analytics platforms compare UTM values as exact, case-sensitive strings. So utm_source=Facebook and utm_source=facebook are two different sources, each with its own slice of traffic. Across a team that hand-edits links, casing drift is one of the most common causes of messy acquisition reports.
Lowercase is the conventional choice because it is unambiguous and easy to enforce — there is no judgement call about which word gets a capital.
- UTM values are case-sensitive in most tools
- Email / email / EMAIL = three separate sources
- Lowercase is the simplest unambiguous rule
Enforce at creation, clean up legacy
The durable fix is to enforce lowercase where links are built — a builder that lowercases automatically, plus a governance rule. Relying on people to remember casing by hand does not scale.
For existing mixed-case data, you can normalise at the reporting layer (a calculated field that lowercases for display) but treat that as a stopgap; the real fix is consistent creation going forward.
How it appears in analytics and logs
Seeing both Newsletter and newsletter as separate sources means casing was not enforced at creation. Each casing variant is a distinct value to the analytics tool, splitting the campaign's traffic across rows that should be one.
Diagnostic use case
Prevent duplicate, near-identical rows in campaign reports by enforcing lowercase UTM values when links are built, and normalising legacy mixed-case values.
What WebmasterID can help detect
WebmasterID records UTM values as received, so lowercase enforcement upstream directly reduces the duplicate sources it has to show; consistent casing keeps the server-side campaign view tidy.
Common mistakes
- Assuming UTM values are case-insensitive — they usually are not.
- Capitalising for looks (Email) and splitting the channel.
- Only normalising in reports, while new links keep arriving mixed-case.
- Lowercasing some parameters but not others, leaving partial drift.
Privacy and accuracy notes
Casing rules apply to link metadata only — the source, medium, and campaign labels. Enforcing lowercase has no bearing on visitor data; it is purely a consistency measure for the link.
Frequently asked questions
- Are UTM parameters case-sensitive?
- The values usually are — most analytics tools treat Email and email as different sources. Enforcing lowercase at link creation is the simplest way to keep them unified in reports.
Related pages
- UTM casing and consistency
Casing is the single most common UTM data bug. Because tools match values as exact strings, utm_source=Reddit and reddit are two separate rows, so one campaign quietly fragments. This page makes the lowercase rule concrete and shows how to deepen it into real consistency.
- UTM builder tools and workflows
A UTM builder is a tool that assembles a tagged URL from your source, medium, campaign, and optional content/term values, so people do not hand-edit query strings and introduce typos. Builders range from Google's free Campaign URL Builder to spreadsheet templates and governed internal tools that lock taxonomy. This page covers the builder spectrum and how a builder enforces consistency at the point of creation.
- UTM governance and templates
UTM data degrades when everyone builds links by hand. This page covers the governance that prevents it: a shared builder or spreadsheet, documented allow-lists for source and medium, and a review step so new values are deliberate rather than ad-hoc.
- Campaign links docs
Enforce lowercase UTM values at link creation.
Sources and verification notes
- Google Analytics Help — Collect campaign data with custom URLsNotes that campaign values are case-sensitive; consistency is required.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.