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.