On this page
concept

UTM Parameters

Created 2026-10-05 32 connections

UTM Parameters

UTM (Urchin Tracking Module) parameters are plain URL labels that identify the source, channel, and campaign of a visitor arriving on a site. Named after Urchin Software — acquired by Google in 2005 — they survive ad blockers, iOS click-ID stripping, and platform walls because they label a campaign rather than identifying a person. For ecommerce retailers they are the foundational layer of campaign attribution, powering both GA4 and Shopify marketing reports.


How UTM parameters work

There are nine supported parameters — five core and four extended — appended to a landing URL after a ? or &:

Core five (Google / GA4 universal):

ParameterWhat it labelsRequired?
utm_sourceTraffic origin (google, meta, klaviyo, newsletter)Yes
utm_mediumMarketing channel type (cpc, email, organic_social, sms)Yes
utm_campaignCampaign name or IDYes
utm_termKeyword or audience segmentOptional
utm_contentCreative or link variant for A/B testingOptional

Extended (GA4 reporting dimensions):

ParameterWhat it labels
utm_idCampaign ID — required for data import into GA4
utm_source_platformBuying platform (e.g. Search Ads 360, Display & Video 360)
utm_creative_formatFormat type (responsive, video, banner)
utm_marketing_tacticTargeting approach (retargeting, prospecting)

GA4 supports all nine; each maps to a dedicated reporting dimension (adbeacon.com, 2026-09-29; registry source via OpenUTM / GA4 community docs, 2026).

When a visitor clicks a UTM-tagged URL, GA4 captures the parameter values at session start and attaches them to all events in that session, populating Session source, Session medium, and Session campaign dimensions (YouTube source via MeasureSchool, date unconfirmed).


How ecommerce platforms read UTMs

Shopify reads UTM parameters directly into the order's conversion summary; it attributes traffic to marketing channels only when utm_campaign is present. A link tagged with only utm_source and utm_medium — but no utm_campaign — is a well-formed GA4 session that Shopify's marketing reports do not count (WeltPixel, 2026-09-21). Shopify uses last-touch attribution by default, crediting the most recent UTM-tagged source before purchase; untagged traffic lands as "direct" and no channel receives credit (AdBeacon, 2026-09-29).

GA4 runs on 14.2 million websites with 81.4% market share among analytics platforms (as-of 2025 per Improvado via linkutm.com, 2025-12-15). Its default attribution model is data-driven (DDA), which distributes conversion credit across multiple touchpoints using machine learning — meaning a paid Meta click that was part of a multi-touch journey may not receive full credit (linkutm.com, 2025-12-15; GA4 practitioner analysis via giantcreates.com, 2025).

"GA4 DDA is default" — confirmed across 2025–2026 sources but GA4 model defaults may change with product updates. Last confirmed: 2026 (YouTube snippet metadata).

Ad platforms (Meta, Google Ads, TikTok) report off their own click identifiers — gclid, gbraid, wbraid, fbclid, ttclid — not UTM strings. UTM parameters affect only the retailer's GA4 and Shopify reports; they have no measurable effect on ad platform reporting or bidding (WeltPixel, 2026-09-21).


Naming conventions and governance

GA4 is case-sensitive: utm_source=Facebook and utm_source=facebook are recorded as two distinct sources, fragmenting reports permanently (WeltPixel, 2026-09-21; Digital Applied, 2026). All UTM values must be lowercase.

utm_medium must match GA4's paid channel regex ^(.*cp.*|ppc|retargeting|paid.*)$ for traffic to group correctly as Paid Search or Paid Social in default channel reporting. Values like social-paid, fb-ads, or sponsored do not match (WeltPixel, 2026-09-21).

For paid campaigns, utm_campaign should carry the campaign ID rather than the campaign name, because names can be renamed and split historical data; IDs are stable (AdBeacon, 2026-09-29).

Dynamic macros should fill utm_campaign, utm_term, and utm_content automatically at click time to eliminate typos:

PlatformMacro for campaign ID
Meta{{campaign.id}}
Google Ads{campaignid}
TikTok__CAMPAIGN_ID__

[!unverified] TikTok macro naming is counterintuitive: __AID__ resolves to the ad group and __CID__ to the creative — the campaign ID is specifically __CAMPAIGN_ID__. Substitution never errors, so mislabelled setups file data under the wrong level silently (AdBeacon, 2026-09-29).

Internal links must never carry UTM parameters. Adding UTMs to links between pages on the same website overwrites the original traffic source, re-attributing organic search sessions to an internal "blog" or "homepage" source in GA4 (linkutm.com, 2025-12-15).

Google Ads auto-tagging takes priority over manual UTM tagging when accounts are linked to GA4; adding hand-written UTM strings to Google Ads destination URLs does not change the GA4 acquisition report and fragments Shopify reports (WeltPixel, 2026-09-21).

"30% of companies skip UTM markup in 30%+ of campaigns" — attributed to Improvado via linkutm.com (2025-12-15). Benchmark volatile; verify before citing.

"Teams that standardise UTM naming conventions see a 29% improvement in campaign attribution accuracy" — attributed to CXL Institute via linkutm.com (2025-12-15). Original CXL source not fetched directly; treat as second-hand.


UTMs, server-side tracking, and Conversion APIs

Server-Side Tagging (sGTM) extends UTM-linked cookie persistence beyond Safari's 7-day JavaScript cookie cap imposed by Apple's Intelligent Tracking Prevention (ITP), because cookies set server-side are treated as first-party and subject to longer retention (Terminus Blog, 2026; registry source). sGTM Transformations also allow selective stripping or redacting of UTM parameters before forwarding to vendor endpoints, enabling privacy-compliant data pipelines (Google Tag Platform developer docs, ongoing).

Conversion APIs — Meta Conversions API, Google Enhanced Conversions, TikTok Events API — accept server-side event data and match it to user profiles using hashed emails, phone numbers, or other identifiers, keeping conversion data accurate even when client-side pixels fail (Tealium, 2025-10-24). These complement UTM data by recovering conversions that UTM tracking misses.

UTM parameters do not require cookie consent under GDPR because they reside in the URL and write nothing to browser storage — described in 2026 sources as "the most privacy-resilient attribution signal available" (GDPR Analytics, 2026).

Tealium source is from October 2025 — included because no newer source covers server-side + UTM interaction in the same depth.


Privacy landscape (2025–2026)

Consent Mode (Google) v2 was enforced for EEA and UK traffic from 21 July 2025. Sites without it can no longer track conversions or build remarketing audiences for non-consented users. Four signals are required: ad_storage, analytics_storage, ad_user_data, ad_personalization; without ad_user_data, Enhanced Conversions (hashed customer data recovery) is blocked (Hello Partner, 2025-07-30; Net Profit Marketing, 2025). Sites with non-compliant consent banners reportedly saw GA4 metrics drop 90–95% after enforcement (as-of July 2025 — Digital Applied, 2026).

The 90–95% drop figure is from a practitioner/vendor source (Digital Applied), not a first-party Google source. Use as directional only.

Privacy Sandbox Attribution Reporting API was retired on 17 October 2025; deprecation begins in Chrome 144 (January 2026) and full removal targets Chrome 150 (July 2026). Three Privacy Sandbox APIs survive: CHIPS (partitioned first-party cookies), FedCM (federated login), and Private State Tokens (anti-fraud). Google is pursuing an interoperable attribution standard via W3C instead (Secure Privacy, 2025-10-17; Usercentrics, 2025).

Apple's Link Tracking Protection (LTP) in iOS 26 / Safari does not strip standard UTM parameters (utm_source, utm_medium, utm_campaign). WebKit has confirmed these pass through in regular and private browsing; click IDs (fbclid, gclid) may be stripped only in Private Browsing or Advanced Tracking Protection mode (Northbeam Blog, 2026; Stape.io, 2026).

iOS tracking protection scope: Cometly (2026-05-10) states "iOS 17+ link tracking restrictions strip many UTM and click-ID parameters from links opened on Apple devices." AdBeacon (2026-09-29), Northbeam (2026), and Stape.io (2026) all state UTM parameters are left intact, with only click IDs at risk in restricted modes. The latter group aligns with Apple's documented LTP behaviour targeting cross-site tracking identifiers rather than campaign labels. Both claims are recorded; neither is resolved here.

Apple's App Tracking Transparency (iOS 14.5+) requires explicit opt-in for cross-app tracking; most users decline, reducing conversion linking for mobile ad clicks (Cometly, 2026-05-10).


Limitations of UTM tracking

UTMs have several structural blind spots that all ecommerce teams must account for:

Last-click undervalues top-of-funnel. Last-click UTM attribution systematically undervalues top-of-funnel and mid-funnel channels — paid social campaigns that create intent appear to produce no conversions, while branded search (which captures demand social created) takes all credit. This leads teams to cut social, eventually eroding branded search performance (Cometly, 2026-05-10).

Cross-device journeys fracture attribution. A user who sees an ad on mobile, researches on a work laptop, and converts on a home desktop generates three unconnected UTM sessions; mobile campaigns appear to produce no conversions and direct traffic inflates (Cometly, 2026-05-10).

Dark Social is invisible. UTM parameters only track clicked links; content shared in private Slack channels, WhatsApp groups, or direct messages arrives in analytics as direct traffic with no UTM data (Cometly, 2026-05-10).

View-through conversions leave no trace. Users who see an ad but do not click generate zero UTM data (Cometly, 2026-05-10).

Ad blockers strip parameters. Ad blockers frequently strip tracking parameters from URLs before the page loads (Cometly, 2026-05-10).

ITP shortens cookie lifespan. Apple's Intelligent Tracking Prevention restricts JavaScript-set first-party cookies to seven days in Safari; UTM data stored in cookies during a session may expire before a multi-session journey converts (Cometly, 2026-05-10).

AI assistants create new gaps. When users research products via AI assistants (ChatGPT, Perplexity, Google AI Overviews) then arrive on site days later, traditional UTM analytics cannot connect discovery-to-conversion (Tealium, 2025-10-24).

Tealium source October 2025 — no newer source found on AI assistant attribution gaps specifically.


UTM parameters in the modern measurement stack

Sources from 2026 describe UTM tracking as one layer in a combined measurement architecture:

  1. UTM parameters — campaign labelling (URL-level, no consent required)
  2. Server-Side Tagging — reliable event capture bypassing browser restrictions
  3. Conversion API (CAPI) — platform signal enrichment for consented/identifiable users
  4. Multi-touch attribution — full-journey credit across UTM touchpoints
  5. Incrementality Testing — geo holdouts or audience exclusion tests for ground-truth lift measurement, including channels invisible to UTM (e.g. AI assistant discovery)
  6. Post-purchase surveys / HDYHAU (How Did You Hear About Us?) — zero-party data filling blind spots

No single method is sufficient alone (Cometly, 2026-05-10; Tealium, 2025-10-24).


Platform-specific notes

Klaviyo changed its default utm_medium value in June 2025 from campaign / flow to the actual message channel type (email, sms, whatsapp, push). Klaviyo also introduced automatic UTM parameters for WhatsApp in January 2026 and for push deep links in May 2026 (Klaviyo What's New changelog, 2025-06-02 / 2026-01 / 2026-05).

utm_content for A/B testing. utm_content is underused; it enables testing creative variants within the same campaign (e.g. hero_cta vs sidebar_cta, video_ad vs carousel_ad) without a separate testing tool (linkutm.com, 2025-12-15).


Key terms

TermMeaning
UTMUrchin Tracking Module — URL parameters for campaign attribution
DDAData-Driven Attribution — GA4's default model as of 2026, distributing credit via ML
ITPIntelligent Tracking Prevention — Apple's Safari cookie-restriction framework
LTPLink Tracking Protection — iOS 17+ feature stripping click IDs in restricted modes
sGTMServer-side Google Tag Manager — routes events through a retailer-controlled server
CAPIConversion API — server-to-server event delivery for Meta, Google, TikTok
gclidGoogle Click ID — Google's own click identifier, separate from UTM strings
fbclidFacebook Click ID — Meta's own click identifier
Consent Mode v2Google's four-signal consent framework, mandatory for EEA/UK since July 2025

Benchmarks (as-of 2025–2026)

  • GA4 market share among analytics platforms: 81.4% (as-of 2025 — linkutm.com citing Improvado)
  • Companies skipping UTM markup in 30%+ of campaigns: 30% (as-of 2025 — linkutm.com citing Improvado)
  • Practitioner threshold for sGTM investment: above €50K/month ad spend or when Meta EMQ drops below 7.0 (as-of 2026 — codeloomtechnologies.com, low confidence — practitioner estimate only)
  • First-party data reliance increase: 67% of marketers increased reliance in 2025 (as-of 2025 — linkutm.com citing Influencer Marketing Hub, medium confidence)

What practitioners report

  • UTM naming consistency is a recurring failure point across teams; centralised UTM builder tools are recommended to enforce governance at scale (MeasureSchool via YouTube source, date unconfirmed)
  • Server-side GTM is the dominant 2026 architecture answer to ITP cookie caps for UTM persistence (registry synthesis)
  • Privacy Sandbox Attribution Reporting API retirement removes the browser-native cookie-free attribution path; W3C interoperable standard is the replacement direction (Secure Privacy, 2025-10-17)
  • Post-purchase surveys with AI assistant options are being added to HDYHAU (How Did You Hear About Us?) instruments as of 2025–2026 (Tealium, 2025-10-24)
Research agent · 2026-10-05