1 November 2026 · 9 min read

UTM Parameters in GA4: A Naming Convention That Holds Up

Open Traffic acquisition on an account that has run campaigns for a year and count the rows for one platform. facebook, Facebook, fb, facebook.com, and one more reading (not set). Five rows, one audience, one budget. The spend sits in one place and the results are spread across five.

The ad platform did not cause that. Someone typed a string into a spreadsheet, a second person built a link with different capitalisation, and a third pasted a URL straight from the browser bar after a redirect had already stripped the tag. The reporting did what it was told.

A naming convention fixes this, but only if it accounts for how GA4 reads the parameters. Most conventions stop at "use lowercase" and then fall apart on the first paid social campaign.

What GA4 does with a tagged URL

Six parameters are read. utm_source fills the source dimensions, utm_medium fills medium, utm_campaign fills campaign name, utm_id fills campaign ID, and utm_term and utm_content fill the manual term and manual ad content dimensions (Traffic-source dimensions, manual tagging, and auto-tagging). Each one exists at three scopes: event, session and first user. Acquisition reports default to session scope, which is where most arguments about numbers begin.

Scope matters because the values are written once, when the session starts. A visitor who arrives from a newsletter and later clicks a paid ad begins a new session with new values, so the campaign report counts two sessions for one person. Anyone reconciling campaign sessions against a pageview total will find a gap for that reason alone.

Two rules overrule whatever you type. When a destination is auto-tagged by a Google integration and you also add UTMs, GA4 uses the auto-tagged values for source, medium and the other traffic classification dimensions. Tagging a Google Ads final URL with utm_source=google changes nothing in Google Ads reporting. It only adds a second, unused description of the same click.

The second rule is less forgiving. Where the click identifier cannot be used, the presence of any UTM parameter makes GA4 derive all cross-channel traffic source values from UTMs exclusively, and any parameter you left out reports as (not set). A half-tagged link is worse than an untagged one, because an untagged click at least falls back to the referrer.

Where a sloppy value gets punished

Channel groups are decided by rules that read the source and medium strings. The rules are case insensitive, fixed, and cannot be edited. The default group is what every report and every client conversation uses, so knowing two or three of the patterns saves a lot of explaining.

Paid Social requires the source to match a list of social sites and the medium to match the pattern ^(.*cp.*|ppc|retargeting|paid.*)$. A Facebook campaign tagged utm_medium=social fails the second test. Organic Social accepts the medium values social, social-network, social-media, sm, social network and social media. The same campaign therefore lands in Organic Social and the paid spend vanishes from the paid view (Default channel group).

Email matches when the source or the medium is one of email, e-mail, e_mail or e mail. A tag using utm_source=newsletter with utm_medium=newsletter matches neither, and with no other rule catching it the session reports as Unassigned. Referral covers medium referral, app and link. Display covers display, banner, expandable, interstitial and cpm. Unassigned is the value you get when nothing matches, and it is a useful alarm: every Unassigned row is a link that broke a rule.

One value is worth knowing because it is recent and easy to break: AI Assistant needs the medium to be exactly ai-assistant. Google sets it from the referrer when traffic arrives from ChatGPT, Gemini, DeepSeek, Copilot or Grok, and it excludes Google's own AI Overviews and AI Mode, which stay in Organic Search. Inventing your own value for an AI visibility campaign puts that traffic somewhere else entirely.

The convention itself

Five rules cover most of the damage.

  1. Lowercase every value. Stored values are case sensitive even though channel definitions are not, so Facebook and facebook sit in separate rows and map to the same channel. That is the worst of both outcomes: two rows and no useful distinction between them.
  2. Use hyphens between words. Whichever single separator you choose, keep to it and never mix. Spaces get percent-encoded in the URL, read badly in a spreadsheet, and invite the next person to type the value a slightly different way.
  3. Keep one closed list of allowed values per parameter in a shared sheet. If a value is not on the list, the link does not go out.
  4. Never reuse one source string for two different things. If utm_source=newsletter covers both your weekly digest and a partner's mailout, no report can separate them and the campaign field becomes the only lever left.
  5. Version the convention and date it. Conventions drift because the person who wrote them moves on.

The parameter list that belongs in that sheet, with the allowed values written down rather than assumed:

Two parameters exist but do not report. utm_creative_format and utm_marketing_tactic are collected and are not exposed as dimensions in GA4, so a convention that relies on them for reporting will disappoint whoever builds the dashboard.

Five failures that keep coming back

Capitalisation is the first and the cheapest to fix. A single uppercase letter splits a row, and it usually arrives from a spreadsheet column where someone typed the platform name the way they would write it in a sentence.

The second is paid traffic tagged as organic. utm_medium=social on a paid social campaign is the most common version, and it moves real budget into the organic channel. The rule is not intuitive, which is why the medium list has to be written down rather than remembered.

The third is the email platform rewriting the medium. Some senders default to values such as campaign or flow, and neither matches a channel rule, so the traffic lands in Unassigned while the send report shows a healthy click rate. Check what the platform actually writes into the URL once, with a test send, and then stop trusting the template.

The fourth is a redirect that drops the query string. A http to https hop, a trailing slash rule or an authentication bounce can rebuild the location header without the parameters. The click still arrives, the session still happens, and the campaign is gone. Test the full path from ad to landing page rather than the tagged URL on its own.

The fifth is a wrapper that does not forward the tag. Link shorteners, some ad platform click trackers and a few affiliate networks wrap the destination. If the wrapper reconstructs the URL rather than passing it through, GA4 sees a direct visit with no source. The symptom looks like a traffic quality problem and the cause is a redirect chain.

Where utm_id earns its keep

Cost data import is the one place where a parameter does measurable work beyond description. The join for campaign data import runs on utm_source, utm_medium and date, which means the values in your imported file have to match the values on the landing URLs exactly, character for character (Import campaign data). Campaign links in that setup need utm_id, utm_source, utm_medium and utm_campaign.

That is the argument for a convention that is boring. A clever scheme with abbreviations works until the first import, and then the join silently matches nothing and the cost column reads zero for a month before anyone notices.

History cannot be rewritten

A new convention applies to future traffic only. Every session already recorded keeps the string it came with, so the report will show both old and new values side by side for as long as the retention window allows. Two approaches work.

The first is a cutover with a date. Publish the convention, name the day it takes effect, and tell everyone who builds links. Tag a release note in the analytics property on that date so the discontinuity is documented where someone will look for it.

The second is a mapping table downstream. Build the case statement in Looker Studio or the CASE expression in BigQuery that folds facebook, Facebook and fb into one value, and label it as a mapping rather than a fix. The distinction matters: cleaning values in the reporting layer hides the upstream problem from the next person who opens the account, and if the mapping is not documented the old strings get reintroduced by someone who never saw it.

What never goes in a UTM

No email address, customer ID, order number or name. Campaign URLs are not private. They appear in server logs, in browser history, in the referrer header sent to third parties whose content sits on the landing page, and in analytics exports that leave the building. Putting an identifier in utm_content spreads personal data wider than the consent on that campaign ever covered.

The same applies to internal identifiers that look harmless, such as a CRM contact reference or an account number. If the value identifies a person or a specific transaction, it belongs in a data layer push or a back end join, not in a URL that gets pasted into a chat window.

Eight checks before the next campaign

  1. List every source value currently in the property for the last 90 days, sorted by sessions. The tail is where the duplicates live.
  2. Group the list by channel and look for paid campaigns sitting in organic channels.
  3. Count the Unassigned rows and open three of them to find the broken rule.
  4. Check one live paid campaign URL for the medium pattern against the paid channel definitions.
  5. Test a full redirect chain from ad click to landing page, and confirm the parameters survive.
  6. Send one test email and read the URL the platform actually generated.
  7. Confirm the cost data import join keys match the values on your landing URLs.
  8. Write the allowed values into a shared sheet, give it an owner and a review date.

None of this is difficult. It gets skipped because a tagging problem never shows up as an error. It shows up as four rows where there should be one, a channel report that contradicts the media plan, and a client asking why the paid social budget did not appear in the paid social column.

Inherited a property where the campaign report does not match the media plan? Book a free tracking audit and we will audit the UTM values in the property, the channel rules they hit and the import joins that depend on them.