Referral path dimension: the page that linked to you
Referral path is the dimension that records the path portion of the referring URL — the specific page on another site that linked to you. It complements the source (the referring host) by showing where on that host the link lived. It is derived from the HTTP Referer header, which Referrer-Policy and cross-origin rules can truncate to the origin or suppress entirely.
What this means
When a visitor clicks a link from another site, the browser may send a Referer header containing that page's URL. Source is taken from the hostname; the referral path is the path-and-query portion — for example '/blog/best-tools' on the referring domain.
Knowing the path, not just the host, lets you identify the specific article or page sending traffic.
Why it is often blank
The Referer header is governed by Referrer-Policy. Many sites now send 'strict-origin-when-cross-origin' (the modern browser default), which exposes only the origin on cross-site navigations — so you get the source host but an empty referral path. HTTPS-to-HTTP downgrades suppress the header entirely, and 'noreferrer' links send nothing.
A blank referral path is therefore expected behavior, not a tracking failure.
- Referral path = path/query of the referring URL
- strict-origin-when-cross-origin hides the path
- noreferrer / HTTPS->HTTP downgrade removes the referrer
How it appears in analytics and logs
A referral path value tells you the linking page on the source site. A missing or '/'-only path usually reflects a strict Referrer-Policy or an HTTPS-to-HTTP downgrade stripping the header, not the absence of a referrer.
Diagnostic use case
Use referral path to find which exact pages on partner sites drive traffic, while accepting that many referrers expose only the origin, not the full path.
What WebmasterID can help detect
WebmasterID captures the referrer the browser provides first-party, so when a full referral path is present you can see the exact linking page without any cross-site tracking.
Common mistakes
- Expecting full referral paths from privacy-conscious referrers.
- Treating a '/' path as a broken integration rather than policy.
- Confusing referral path (their page) with landing page (yours).
Privacy and accuracy notes
The referral path comes from the Referer header the browser chooses to send. Referrer-Policy increasingly trims this to the origin for privacy; WebmasterID records only what is sent and never reconstructs full paths.
Related pages
- Source dimension: the origin half of traffic attribution
Source is the dimension that names where a visit came from: a search engine (google), a referring domain, a named newsletter. It is the origin half of source/medium. Tools set source from the utm_source parameter or, lacking that, from the hostname of the referrer. When neither exists the source becomes '(direct)'. Source is high-cardinality, which has practical reporting consequences.
- Page referrer dimension
Page referrer is the dimension that records the full URL a visitor came from before the current page — captured by GA4 as the page_referrer parameter on page_view. It is event-scoped and granular: it shows the immediate previous page, including internal navigations within your own site. That makes it different from the session-level source/medium, which describes how the whole visit began rather than each hop.
- Direct traffic: what it really means
Direct traffic is the bucket analytics uses when no referrer is available. It includes genuine type-ins and bookmarks, but also a large share of visits whose referrer was stripped — app opens, HTTPS-to-HTTP transitions, shorteners, and privacy settings. Treating 'direct' as a single intent is the classic analytics mistake.
- Web analytics
See referring pages first-party without cross-site tracking.
Sources and verification notes
- MDN — Referrer-PolicyExplains how the Referer header (and thus referral path) is trimmed.
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.