UTM

UTM stands for Urchin Tracking Module - named after Urchin, the analytics company Google acquired in 2005 that became Google Analytics. UTMs are the five query-string parameters appended to URLs to track where visitors come from and which specific campaign brought them. The parameters are an unglamorous piece of marketing infrastructure, but they’re the difference between a team that can attribute traffic sources correctly and a team that can’t.

The five UTM parameters

utm_source. Where the click came from. “google”, “newsletter”, “twitter”, “partner-a”. The broadest channel identifier.

utm_medium. The category of channel. “cpc” (paid search), “email”, “social”, “referral”. Distinguishes paid from organic, and channel types from one another.

utm_campaign. The specific campaign name. “spring-launch-2026”, “webinar-march-15”, “black-friday-homepage”. Lets reporting group clicks by marketing initiative.

utm_content. Variation within a campaign. Useful for A/B testing or distinguishing multiple creatives in the same campaign. “headline-a”, “cta-blue”, “hero-image-2”.

utm_term. Mainly used for paid search; captures the specific keyword that triggered the click. Less commonly used outside paid contexts.

A complete UTM example: https://example.com/landing?utm_source=newsletter&utm_medium=email&utm_campaign=spring-launch-2026&utm_content=header-cta

Why UTMs matter

Three operational reasons:

Channel attribution. Without UTMs, Google Analytics has to guess where traffic came from. It handles organic search, direct, and referral reasonably; it handles paid, social, email, and partner traffic badly without UTMs. Adding them lifts attribution from approximate to specific.

Campaign measurement. “Was the April newsletter more effective than the May newsletter?” Answerable only if each send carried distinct UTMs. Without them, both show up lumped into “email” or “direct”.

Cross-tool reporting. Most analytics and marketing platforms read the same UTM parameters. A link UTM-tagged for GA also attributes correctly in HubSpot, Mixpanel, and Segment. Standard parameters unlock cross-tool reporting.

UTM naming conventions

UTMs only work if they’re consistent. Four disciplines:

Use a naming convention document. Writing “Source: Newsletter” in one link and “source=newsletter” in another splits the same traffic across two reports. A written convention - lowercase, hyphenated, specific values - prevents this drift.

Use a UTM builder. Form-based UTM construction (Google’s Campaign URL Builder, or internal tools like a spreadsheet with dropdowns) prevents typos. Hand-typed UTMs have a ~15% error rate in most teams.

Limited, stable source and medium values. A dozen or so canonical source values; five or six canonical medium values. Campaign and content can be more flexible, but the broader dimensions should be stable.

Never UTM-tag internal links. A link from your own blog to your own pricing page with UTMs attached overwrites the user’s true original source. The report attributes them to “blog” instead of “google” - meaningless for acquisition analysis.

Where UTMs go wrong

Five common failure modes:

Inconsistent casing. utm_source=Newsletter and utm_source=newsletter as different records. Most analytics treat them as distinct. Standardise on lowercase.

Spelling variations. utm_medium=cpc and utm_medium=ppc and utm_medium=paid-search. All the same intent; all different in reporting. Pick one; document; audit for drift.

Over-granular campaigns. utm_campaign=2026-03-15-webinar-deliverability-tim-hershey. Impossible to group or roll up. Campaigns should be meaningful clusters, not unique IDs.

UTMs on shared content. UTM-tagged URLs shared across channels carry forward the UTM of the first channel. A newsletter-tagged URL that a subscriber emails to a friend still reports as newsletter traffic from the friend’s click. Minor but common source of attribution error.

Stripping UTMs at redirect. Some URL shorteners or redirect rules drop query parameters. The UTM is present on the click but not on the landing page. Analytics sees the visit but can’t attribute it.

UTMs and privacy

Three considerations in a privacy-tightening landscape:

UTMs are visible in browser history and shared links. Embedded PII in UTMs leaks to every downstream surface. Never put email addresses, user IDs, or other sensitive identifiers in UTM parameters.

Browser privacy protections don’t remove UTMs. Safari’s Intelligent Tracking Prevention and Firefox’s enhanced tracking protection attack cookies, not URL parameters. UTMs continue to work where cookies don’t.

UTMs in GDPR-regulated contexts. Query parameters are data; a UTM attributed to an identifiable user is processing personal data. Consent and data-retention rules apply as they would to any analytics data.

Practical UTM hygiene

Four things worth doing quarterly:

Audit the source/medium table. Look for near-duplicates (“email” vs “Email” vs “newsletter”) and consolidate.

Check for internal UTMs. Site-to-site links carrying UTMs are a signal someone inside the team is using them incorrectly. Audit and fix.

Validate that UTMs reach reports. Click a UTM-tagged link in a campaign; verify it shows up correctly in the analytics report within 24 hours. Silent failures happen and are embarrassing when caught late.

Document the naming convention in a visible place. Every new person who runs campaigns should know the convention before shipping their first link. See tracking code and marketing analytics for the broader attribution picture.

Related terms