UTM governanceGA4Marketing analytics
UTM governance: a naming system that keeps channel data clean
By The MB Data Automation team··5 min read
TL;DR
- →Inconsistent UTMs break channel grouping and make reports disagree.
- →Fix it with a naming convention everyone follows and a single reference sheet.
- →Lowercase, consistent values, and a fixed taxonomy do most of the work.
If your channel report lumps the same source into three different buckets, the culprit is almost always UTMs. When team members tag links differently - Facebook, facebook, FB - the data cannot roll up cleanly. UTM governance is the cheap fix.
The rules that matter most
- Lowercase everything - GA4 is case-sensitive, so Facebook and facebook are different.
- Fix a vocabulary for source and medium and do not deviate.
- Use a consistent campaign naming pattern (for example, objective_audience_date).
- Keep one reference sheet of approved values the whole team uses.
| Parameter | Rule | Example |
|---|---|---|
| utm_source | Where the traffic comes from, lowercase | google, meta, klaviyo |
| utm_medium | The channel type, fixed vocabulary | cpc, email, social |
| utm_campaign | A consistent naming pattern | blackfriday_prospecting_2026 |
Why it pays off
Clean UTMs mean channel and campaign data reconciles across platforms, dashboards group traffic correctly, and you stop spending report time untangling naming mistakes. It is one of the fastest fragile-to-scalable upgrades.
The Agency Reporting Automation Kit includes a UTM governance system - the naming convention and reference sheet to keep channel data clean across clients.