WebmasterID logoWebmasterID
Referrers

Campaign vs referrer precedence

A single visit can arrive with both a Referer header and UTM campaign parameters. Most analytics tools let the explicit campaign parameters take precedence over the inferred referrer, because a deliberate utm_source is a stronger signal than a host guess. Knowing the precedence order explains why a tagged link shows your campaign source even when the referrer differs.

Verified against primary sources

How precedence usually works

When a visit carries explicit campaign parameters, analytics tools generally treat those as the source of truth: utm_source and utm_medium define source/medium, and the Referer header is set aside for that visit. The reasoning is that a campaign tag is a deliberate declaration, while a referrer is an inference from a host.

This is why a link you tagged utm_source=newsletter shows up under your newsletter campaign even though the click physically came from an email client or webmail host. The campaign signal wins, and the referrer does not separately create a second visit.

Edge cases to watch

Precedence varies by tool and by what is present. If only some UTM parameters are set (for example utm_source without utm_medium), tools may fill the gap differently, so set a complete, consistent set. Auto-tagging systems (such as ad-platform click IDs) can also take precedence over manual UTM tags, which surprises people who expected their utm_source to win.

The practical rules: tag links completely and consistently so precedence is predictable; do not also expect a referral entry for a tagged click; and when an ad platform auto-tags, learn its precedence rather than assuming your manual tags dominate.

How it appears in analytics and logs

When both signals are present, the explicit campaign parameters usually override the referrer for source/medium. A visit is not both a campaign and a separate referral; precedence resolves it to one source.

Diagnostic use case

Explain why a tagged link is attributed to its UTM source rather than the Referer host, and avoid double-counting a single visit as both a campaign and a referral.

What WebmasterID can help detect

WebmasterID applies a clear precedence between UTM parameters and the referrer server-side, so a tagged campaign click is counted once under its campaign source rather than being split or double-counted.

Common mistakes

Privacy and accuracy notes

Precedence logic uses only the Referer host and campaign parameters on the URL. No visitor is identified. WebmasterID resolves the source for traffic, never for a person.

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.