Self-Referral
A self-referral is when your own domain shows up as a referral source in your own GA4 reports — your site appearing to send traffic to itself. It happens when something interrupts a visit mid-journey and GA4 restarts the session, crediting the source as your domain instead of where the visitor genuinely came from.
Why it matters
A self-referral is attribution quietly breaking. Every session that lands in that bucket is a session whose real origin — search, a newsletter, a social post — has been erased and replaced with your own domain name. For a small business trying to learn which channels actually work, self-referrals corrupt exactly the report you'd use to make that call.
A concrete example
Say customers pay through an external processor and return to a thank-you page on your site. Without cross-domain tracking, GA4 sees the return as a fresh visit referred by the payment domain — or, on some setups, by your own domain. The purchase gets credited to "self-referral" rather than the Google ad or email that brought the buyer in. Your best channel looks like it converts nobody.
The common misreading
The mistake is reading a self-referral as a real traffic source worth analysing. It isn't — it's a tracking artefact. The fix is to add your own domains, subdomains, and any payment or booking domains to GA4's referral exclusion list, and to configure cross-domain tracking. Sudden self-referral spikes can also signal junk traffic; check it against your bot filtering.
WebSignalytics reads your traffic sources in context and flags attribution that doesn't add up — so a self-referral never gets mistaken for a real channel. No dashboards, no logging in.
See how it works