Definition
UTM parameters are a set of named query-string parameters, utm_source, utm_medium, utm_campaign,
utm_content and utm_term, that an analytics tool recognises as campaign data. The name comes from Urchin,
the web analytics product that became Google Analytics, and the convention has since been adopted by most
analytics and marketing tools. The parameters describe the link, not the visitor: where it was placed
(source), what kind of channel it is (medium), which initiative it belongs to (campaign), which variant it is
(content) and, for paid search, which keyword triggered it (term). Google's URL builder documentation adds a
few further parameters for its own reports, such as utm_id and utm_source_platform, and documents which
fields are required for a campaign to be recorded. Consistent naming is the essential point: analytics treats
each distinct value as a distinct row, so Email, email and e-mail become three channels.
How it works
When a browser requests a page whose URL carries UTM parameters, the analytics tag on that page parses them
and attaches the values to the session as traffic-source dimensions. From then on the session is reported
under that source, medium and campaign, regardless of which pages follow. Default channel groupings are
derived from the source and medium values, using rules the tool documents, so a medium such as cpc lands
in a paid channel and email in the email channel while an unrecognised value falls into an "other" bucket.
The parameters are read only at the point of entry; a UTM-tagged link clicked within the same site starts a
new traffic source and breaks the session's history.
| Parameter | What it should carry | Example value |
|---|---|---|
utm_source | The property or platform the link was placed on | newsletter, facebook, partner-site |
utm_medium | The channel type, matching the tool's channel rules | email, cpc, paid_social, affiliate |
utm_campaign | The initiative or promotion | spring_sale, product_launch |
utm_content | The variant: placement, creative or link position | hero_banner, footer_link |
utm_term | The paid keyword, or an audience label where keywords do not apply | running_shoes |
Platform click identifiers work alongside UTMs rather than replacing them. Google Ads auto-tagging appends its own identifier so that a linked Google Analytics property imports campaign, ad group and keyword detail from the account, and the Google Analytics help centre documents how manual tags and auto-tagging interact when both are present. The naming conventions and UTMs guide covers case rules, separators and governance; the Google Ads naming conventions guide shows how campaign names and UTM values can be kept aligned.
In practice
UTMs matter most for links the platform cannot otherwise identify: email, SMS, QR codes, partner placements, influencer posts, offline materials and any paid channel that has no integration with the analytics tool. For those, the parameters are the only way a visit gets a source other than "direct" or a bare referrer. The practical routine is a single builder or spreadsheet that every team uses, a short list of permitted medium values, lowercase everywhere, and a periodic check of the acquisition report for values that do not belong to the convention.
One newsletter, two links, one lesson
A publisher sends a newsletter to 180,000 subscribers with a hero banner tagged
utm_source=newsletter&utm_medium=email&utm_campaign=spring_sale&utm_content=hero_banner and a footer link
whose utm_content is footer_link. The acquisition report shows 3,240 sessions from the hero banner and
410 from the footer, a split of 89% to 11%. A third row appears with the medium Email, holding 260 sessions
from a regional team's version that capitalised the value, so the true campaign total is 3,910 sessions, not
the 3,650 that the clean rows suggest. The convention is updated to force lowercase in the shared builder.
What it is not
UTM parameters are not a tracking technology in the sense of identifying a person. They label a link, not a visitor, and they are visible in the address bar and in the server log. They are not a ranking signal, and they are not harmful to search visibility provided the canonical URL excludes them. They are not a substitute for platform click identifiers: a Google Ads click carries more detail through auto-tagging than a manual tag can, and adding UTMs on top is a choice to be made deliberately. They are not for internal links, where they overwrite the real source of the visit. And they are not an AttributionAssigning conversion credit to touchpoints. model: they supply the touchpoint labels an attribution model consumes, but the rules for sharing credit between touchpoints live elsewhere.
Related terms
GA4Google's event-based analytics platform. is where most people meet UTMs, and its documentation defines which parameters it reads and how they map onto the traffic-source dimensions shown in the GA4 reports and dimensions guide. AttributionAssigning conversion credit to touchpoints. depends on UTMs for every touchpoint that lacks a native integration, so a gap in tagging becomes a gap in credit. The reporting KPIA metric tied directly to an objective. set for a channel is only as reliable as the tagging that feeds it; when email or affiliate sessions are missing from a dashboard, untagged links are the first place to look. The naming conventions and UTMs guide turns these points into a working standard, and the Google Ads naming conventions guide shows how the same fields can be carried in campaign names so that platform reports and analytics reports describe the same thing in the same words.
Common mistakes
- Inconsistent values. Capitalisation, spaces and synonyms split one channel into several rows and ruin period-over-period comparisons.
- Tagging internal links. A tagged link from one page of the site to another resets the source and starts a new session in some tools.
- Using
utm_mediumfor the platform name. Medium is the channel type; the platform belongs in source. - Leaving UTMs out of non-platform channels. Email, partner and offline traffic then appears as direct.
- Forgetting the canonical tag. Tagged URLs that get indexed or shared should resolve to one canonical page so search signals are not spread across variants.
- Encoding campaign strategy in the values. Budgets, targets and owners belong in a campaign register; the parameters should carry only what the report needs to group sessions.
