WebmasterID logoWebmasterID
UTM tracking

utm_content vs utm_term: when to use each

The two optional UTM tags get muddled constantly. utm_content distinguishes creatives or links for A/B comparison; utm_term carries the paid-search keyword. This page draws a clean line between them so each does its job and your reports stay legible.

Verified against primary sources

What each tag is for

The two optional UTM parameters answer different questions, and keeping them in their lanes keeps reports readable:

Why conflating them breaks reports

utm_content is the A/B dimension: use it to compare two ad creatives, two button placements, or two post variants under the same campaign. utm_term is historically the paid-search keyword field, populated for search ads. If you put keywords into utm_content, your creative comparison fills with keyword noise; if you put creative labels into utm_term, your keyword report becomes meaningless.

The rule is simple: ask whether the value answers 'which version did they click' (utm_content) or 'which keyword brought them' (utm_term). Most non-search channels never need utm_term at all — leave it empty rather than repurposing it.

How it appears in analytics and logs

utm_content tells you which version of a link or creative was clicked; utm_term tells you which keyword triggered a paid-search click. Swapping them scatters keyword data into the content dimension and vice versa.

Diagnostic use case

Use utm_content to tell two creatives or links apart and utm_term for the paid-search keyword, so neither tag ends up carrying the other's data.

What WebmasterID can help detect

WebmasterID reads both utm_content and utm_term at ingest and keeps them as separate dimensions, so creative comparisons and keyword data do not bleed into each other in your reports.

Common mistakes

Privacy and accuracy notes

Keep both tags to generic labels — a creative slug or a keyword, never personal data. UTM values are public in the URL and logs.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.