Skip to main content
Beginner7 min readUpdated March 22, 2026

Lowercase vs Mixed Case UTMs: Pick One Convention and Enforce It

Case sensitivity fragments reports. Standardize casing with practical enforcement steps.

UTMData Quality
Published March 22, 2026

Treat UTMs as case-sensitive identifiers: pick lowercase (recommended) and enforce it everywhere links are authored.

Overview

Many tools treat `Twitter` and `twitter` as different sources. That silently splits metrics.

Why it matters

Lowercase is the most copy-paste friendly and reduces human error in hand-built links.

Implementation playbook

Encode enforcement in your builder and in code review checklists for engineering-owned pages.

Next steps

Backfill legacy mixed-case rows in BI with normalized dimensions when historical cleanup is impractical.

Frequently asked questions

Who should read this guide on Lowercase vs Mixed Case UTMs?
Treat UTMs as case-sensitive identifiers: pick lowercase (recommended) and enforce it everywhere links are authored.
How do DemandLinks-style structured links help analytics?
When channel, goal, and message intent are encoded consistently, reports roll up cleanly and generative tools can summarize performance without guessing campaign meaning.
What should we document alongside UTMs?
Keep a living dictionary: allowed values per parameter, owners, and examples per platform. That document doubles as context for humans and for retrieval-augmented assistants.

Ready to implement what you've learned?

Start building intent-based tracking links and get insights that drive real business results.

Start Building Links
View All Guides

Stay Updated

Get the latest guides and marketing insights delivered to your inbox.