Self-referrals and lost attribution
A self-referral is when your own site shows up as a referring source in your reports. It usually means a session was broken and a new one started attributed to your domain, often when a visitor crosses subdomains or returns from a payment provider. Self-referrals fragment sessions and steal credit from the real source. This page explains the causes and the fix.
Why your own domain becomes a referrer
Analytics decides the source of a session from the referrer. If a visit crosses from one part of your property to another in a way the tool treats as a new session — different subdomain, a return from an off-site payment page, or a redirect that drops campaign data — the referrer becomes your own domain. The original external source is lost and a fresh, self-referred session begins.
The symptom is your domain (or a payment provider) ranking as a top 'source'.
- Cross-subdomain navigation without shared measurement
- Return from an off-site payment or auth provider
- Redirects that strip the referrer or campaign tags
How to prevent it
Add your own domains and trusted intermediaries (such as payment providers) to the referral-exclusion or unwanted-referrals list so a return from them does not start a new session. Configure cross-domain measurement if a journey legitimately spans domains. Then verify that your domain no longer appears as a source.
How it appears in analytics and logs
Your own domain appearing in the referrer or source report means sessions are breaking mid-journey, usually at a subdomain or payment boundary.
Diagnostic use case
Eliminate self-referrals so sessions are not split and acquisition credit stays with the genuine external source.
What WebmasterID can help detect
WebmasterID's first-party model keeps a journey within one property, so crossing your own subdomains does not manufacture a new referred session.
Common mistakes
- Leaving a payment provider out of the referral exclusion list.
- Not configuring cross-domain measurement for multi-domain journeys.
- Treating self-referral sessions as genuinely new acquisitions.
Privacy and accuracy notes
Diagnosing self-referrals inspects referrer fields and configuration, not visitor identity. No personal data is required.
Related pages
- Referral spam and ghost traffic
Referral spam and ghost traffic are fake hits crafted to appear in your reports. Crawler spam loads pages to leave a referrer in your logs; ghost spam sends hits straight to a measurement endpoint without ever visiting your site. Both add phantom sessions with no engagement. This page explains the mechanics and the filtering that removes them.
- Direct traffic as a catch-all bucket
Direct traffic is often misread as 'people who typed the URL'. In practice it is a catch-all for any session with no usable referrer or campaign: untagged links, stripped referrers, app and messaging clicks, and redirects that lose data. When other attribution fails, direct swells. This page explains what really lands in the direct bucket and how to shrink it.
- Last-click attribution: simple, and what it hides
Last-click attribution assigns 100% of a conversion's credit to the last touchpoint before it. It is simple, deterministic, and the historical default — which is exactly why it misleads: it ignores every earlier touch that created demand, systematically overrating bottom-funnel channels and underrating discovery.
- Attribution analytics
Keep acquisition credit with the real source.
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.