UTM Governance: Naming Conventions and Rules for Clean Data

Marketing lead setting UTM campaign values

UTM governance is the set of rules, owners and checks that keeps every tagged link in your company consistent. It covers which values are allowed, who approves new ones, how links get built and how mistakes get caught before a campaign launches. Without it, one channel shows up as “LinkedIn,” “linkedin” and “li_paid” in the same report, and nobody trusts the numbers.

This guide walks through a practical system: the parameters, a naming convention you can adopt today, roles, a pre-launch QA routine, what to leave untagged and how to audit. It is written for marketing and revenue operations leads who have inherited a messy spreadsheet and need to make it stick.

Quicktoimpress
Build cleaner data systems
Quick To Impress helps marketing and revenue teams connect their technology systems, including revenue operations and workflow automation.
Explore growth engineering

TL;DR

  • Pick one owner, not a committee, and give that person authority to approve every new source and medium value.
  • Write a short convention: lowercase only, one separator, a fixed list of mediums, and a campaign name pattern everyone can parse.
  • Put the rules into a builder or shared sheet people actually open, instead of a PDF nobody reads.
  • Run a QA check before launch and an audit monthly or quarterly, so errors are caught while they are cheap to fix.
  • Never add UTMs to internal links. They can reset the original source of a session.

Table of Contents

Why UTM data breaks as teams grow

UTM tagging is easy to learn and hard to keep consistent. The five standard parameters are utm_source, utm_medium, utm_campaign, utm_term and utm_content, and anyone with a browser can type them into a URL. That is the problem. Each person makes reasonable, slightly different choices, and your analytics tool treats every variation as a different value.

Google’s own documentation notes that values are case-sensitive and recommends all lowercase to avoid fragmented reports. It also says a consistent approach keeps traffic from being categorized incorrectly in default and custom channel groups. In practice, the damage looks like this:

  • Paid social spend that cannot be tied to pipeline because the medium was typed “paidsocial” by one agency and “paid-social” by another.
  • Email clicks landing in “(not set)” because a parameter was missing.
  • Reports that need an analyst to hand-clean values every month before anyone can present them.
  • A former agency’s links that nobody can decode, because the logic left with the agency.

Governance does not make tagging slower. It moves the thinking to one place, once, so each person building a link only has to choose from a list.

The parameters you are governing

Three parameters do the real work, and two are optional detail.

Parameter What it identifies Governance stance
utm_source Where the click came from (a platform, a publisher, a list) Required. Controlled list.
utm_medium The type of channel (email, paid social, cpc) Required. Small controlled list that maps to your channel groups.
utm_campaign The initiative or promotion Required. Follows a naming pattern.
utm_term The paid keyword Optional. Usually filled automatically by ad platforms.
utm_content Which creative or link variant Optional. Free-form within a pattern, used for A/B tests.

Official guidance from the CDC also treats source, medium and campaign as the required fields for campaign link tracking, which is a useful baseline if you need to justify a minimum standard to a skeptical stakeholder.

Google Analytics also supports utm_id and utm_source_platform. If you report in GA4, decide whether to require utm_id. A stable campaign ID tied to a row in your campaign list is far more reliable than a human-typed campaign name when you need to join analytics data to CRM or spend data.

A correctly formed URL starts parameters with a question mark, separates them with ampersands and contains no spaces, as this university guide to UTM codes spells out. A clean example from Google’s documentation: https://www.example.com/?utm_source=summer-mailer&utm_medium=email&utm_campaign=summer-sale. Source is the mailer, medium is email and the campaign is the summer sale.

A naming convention that survives contact with real teams

Most convention documents fail because they are too clever. Keep the rules few enough that a new hire can recall them without opening the document.

Core formatting rules

  1. Lowercase everything. No exceptions, including campaign names and content tags.
  2. Choose one separator. Hyphens or underscores, never both. Hyphens are common in readable values; underscores are common when you pack several fields into one string. Pick one and write it down.
  3. No spaces, no special characters. Spaces break links or turn into encoded characters that look like different values.
  4. No personal data. Never place an email address or a name in a parameter.
  5. Use full words, not private abbreviations. If a value needs a legend to decode, it will be misread within a year.

Controlled lists for source and medium

Source and medium should come from a dropdown, not free text. Keep the medium list short, and make each entry map cleanly to a channel group in your analytics. A starter set:

utm_medium Use for
email Newsletters, lifecycle and sales sequences
cpc Paid search and other cost-per-click ads
paid-social Paid placements on social platforms
social Organic posts from your own accounts
affiliate Partner and referral programs
display Banner and programmatic placements
qr Print, packaging and in-store codes

Your list will differ. The point is that adding to it is a decision, made by the owner, not a side effect of someone’s Tuesday afternoon.

A campaign name pattern

A pattern lets anyone read a campaign name and a script split it into fields. One workable shape: year-quarter_region_goal_theme, such as 2026q4_us_demo_pricing-update. Or skip the clever name and rely on a campaign ID that maps to a row in your campaign tracker, with the name kept short and human.

For utm_content, agree on what it encodes. Usually that is the creative variant or the link position, such as hero-button versus footer-link in an email. Keep it descriptive, not sequential.

Who owns it: roles and approvals

The single most common governance failure is shared ownership. One practitioner argues that a single owner rather than a committee is the best predictor of whether a convention survives, because it prevents the suggestion-box effect where every request gets accommodated. We agree.

The research on workflow design converges on a few roles, which can be one person in a small team:

  • Strategy owner. Usually in marketing operations or analytics. Maintains the convention, approves new source and medium values and audits consistency.
  • Link creators. Campaign managers and agencies who build links from the approved list.
  • Channel stewards. Leads for email, paid, social and partners who confirm their channel’s values map to reporting.
  • Analytics auditor. Someone who reviews exports on a schedule. TrackFunnels describes this split among owner, stewards, link creators and auditors, with analytics running recurring audits.

One rule makes the model work: creators choose from the list; they do not add to it. A request to add a value goes to the owner, gets answered within a day and is logged. If approvals take a week, people will route around them.

Tools can enforce what documents cannot

A convention in a PDF is a suggestion. A shared builder with dropdowns and locked values is a rule. A shared spreadsheet with data validation works for smaller teams. Larger teams often build a small internal tool tied to the campaign list and the CRM, so links, IDs and campaign records stay in sync.

If you manage tags in Google Tag Manager, its access controls help too. Users can be limited to editing rather than publishing, access can be bounded by pages, and zones can combine with approvals. That keeps tracking changes behind a reviewer, the same principle as approving a new UTM value.

When an ad platform supports it, Google also suggests dynamic URL parameters to automate tagging and remove human error in hand-built URLs. Use them for ad platforms and reserve manual tagging for email, partners, social posts and offline codes.

Governing agencies and outside teams

Agencies are where conventions most often fall apart. Each one arrives with its own habits and its own spreadsheet. A few rules help:

  • Put the tagging standard in the statement of work, with the builder or sheet attached.
  • Give agencies access to the same builder your team uses, rather than emailing them a document.
  • Require that links are logged in your system, not theirs, so you keep them when the contract ends.
  • Run the same pre-launch check on their links as on yours.

The same applies to sales, events, partner and product teams. Anyone who creates a tracked link is a link creator, and onboarding them is part of the job.

Pre-launch QA: a checklist that takes two minutes

The cheapest place to catch an error is before the link goes out. Attributy’s guidance on UTM governance says QA should confirm the destination, required parameters, taxonomy, case, separators, absence of personal data, redirect preservation and analytics capture. Turned into a checklist:

  1. The link opens the intended page, not a 404 or a staging URL.
  2. Source, medium and campaign are present and come from the approved lists.
  3. Everything is lowercase, with the agreed separator and no spaces.
  4. No personal data appears in any value.
  5. If the link passes through a redirect or shortener, the parameters survive it.
  6. A test click appears in analytics with the expected values.

That last step is the one teams skip. Open your analytics real-time view or, after processing, check Session source/medium, Session campaign and related dimensions under Acquisition and Traffic acquisition. Google notes that missing parameters can produce “(not set)” values, so a “(not set)” in a report is a signal to look for incomplete tagging.

The destination matters as much as the tag. A perfectly tagged click that lands on a slow, confusing page wastes the spend you tracked so carefully. If the links point at campaign pages, pair this checklist with a review of high-converting landing pages, and see our own B2B landing page optimization playbook for the testing side.

What not to tag

Tagging more is not tagging better. Two rules prevent most self-inflicted damage.

Never tag internal links. GitLab’s public handbook says to add UTMs when linking to a site it controls from outside, but not to internal links on the same domain, because an internal UTM can start a new session and override the original source. Its digital strategy page requires tagging for URLs promoted on external sites and in email, and excludes internal links because they reset attribution. If your homepage banner links to a pricing page with UTMs, you have just erased the fact that the visitor came from search.

Do not tag links you cannot interpret. Do not tag links to properties your company does not control, where the data will never reach your analytics. Do not tag organic search or links where the platform already passes reliable referrer data, unless your convention says otherwise.

Write these exclusions into the document. They are the questions new people ask first. Use internal link tracking through events or data layer pushes instead of UTMs when you need to measure on-site promotions.

What not to tag — overview diagram

What the governance record should contain

Keep the system of record small, but complete. It should hold:

  • The approved lists of sources, mediums and, if used, content tags.
  • The campaign name pattern with two or three real examples.
  • The named owner and the approval process.
  • The exclusions: what never gets tagged.
  • A change log of approved additions and corrections.
  • A store of every generated URL, ideally linked to the campaign ID.
  • The QA checklist and the audit schedule.

The change log matters more than it looks. When someone asks in a year why “partner-email” exists, the answer is in the log, not in anyone’s memory.

Auditing and cleaning up

Governance without audits drifts. Export your campaign data from analytics on a schedule, monthly or quarterly with named responsibility, and look for:

  • Values that are not on the approved lists.
  • Near-duplicates (case differences, hyphen versus underscore, plural forms).
  • Sessions with a source but no medium, or a medium but no campaign.
  • High-traffic campaigns with no matching record in your campaign tracker.
  • Large “(not set)” shares.

Fix the cause first, then the data. If an agency keeps tagging wrongly, update the builder or retrain; do not just map their values in the report. Where you must clean history, use channel group rules or reporting-layer mappings, and document them so the next analyst understands why.

Moving from clicks to revenue

UTMs record the first touch of a session. Revenue lives in your CRM. Governance only pays off fully when campaign values pass into form fields, the CRM stores them on the contact or deal, and reporting can tie a source and campaign to pipeline and closed revenue. That takes a deliberate setup: hidden form fields, consistent field names and lifecycle reporting that does not overwrite original values.

UTM values flowing through CRM to revenue

If your sales cycle includes phone calls, stores or offline closes, pair your UTM standard with a plan for durable offline conversion tracking from CRM and POS. That is where a clean taxonomy starts to inform budget decisions.

Our perspective: governance is a revenue system, not a spreadsheet

We see the same pattern across scaling teams. The tagging document exists. The problem is that it lives apart from the systems where links are made and the systems where results are read. Someone writes a standard, the standard is correct, and six months later three agencies, two regional teams and an intern are each following a slightly different version of it.

We think the fix is engineering, not nagging. Put the rules where people work: a builder that only offers valid values, a campaign record that generates the ID, form fields that carry values into the CRM, and a dashboard that flags values outside the list. Then the convention enforces itself, and the owner spends time on decisions instead of policing.

We also think ownership has to be named and senior enough to say no. A convention nobody can enforce is a wish. And the people who design the taxonomy should stay involved in how it is built and reported, because the first time a pipeline report does not match a campaign list, the design assumptions are what need to be revisited.

— Service

How Quick To Impress can help

If your UTM problem is really a data-flow problem, with links, forms, CRM fields and reports that do not agree, that is the work our revenue operations team does. We embed with your marketing and revenue teams, build the taxonomy and the tooling around it, and stay on to improve it. Engagements run on monthly capacity, with Core capacity at $3,500 to $5,999 per month, Growth capacity at $6,000 to $9,999 per month and Scale capacity from $10,000 per month. Details are on our pricing page.

A 30-day rollout plan

You do not need a quarter-long project. A focused month is enough to get a working standard in place.

Week 1: Inventory. Export the last six to twelve months of source, medium and campaign values. Count the variants. This usually produces the business case on its own.

Week 2: Decide. Name the owner. Draft the formatting rules, the source and medium lists, the campaign pattern and the exclusions. Keep it to one page.

Week 3: Build. Set up the builder or validated sheet, add the QA checklist and set up a place to store generated links. Connect UTM fields to the CRM if they are not already.

Week 4: Launch and train. Brief every link creator, including agencies. Retire old templates. Schedule the first audit and put it on someone’s calendar.

After that, the work is light: approve additions, run the audit, review the log. The payoff is reports that need no cleanup before the meeting.

FAQ

What is UTM governance?

It is the policy and process behind your campaign tags: approved values, naming rules, an owner, a QA step and regular audits. It exists so everyone who builds a tracked link produces data your analytics can group correctly.

What are the five UTM parameters?

The five are utm_source, utm_medium, utm_campaign, utm_term and utm_content. Source, medium and campaign are the ones you should require. Term and content are optional detail for paid keywords and creative variants.

Should UTM values be lowercase?

Yes. Values are case-sensitive, so “Email” and “email” are counted separately. Google recommends using all lowercase, and making it a hard rule is the simplest way to avoid fragmented reports.

No. Tagging links between pages on your own site can start a new session and replace the original source, as GitLab’s handbook explains. Use event tracking for internal promotions instead.

Who should own UTM governance?

One named person in marketing operations or analytics, with authority to approve new values. Shared ownership tends to turn the convention into a suggestion box, so keep the decision with a single owner and give everyone else a clear way to request changes.

Sources