Referral exclusions and self-referrals in GA4, explained
If your own payment provider, booking tool or even your own domain is showing up as a traffic source in GA4, you have a self-referral problem, and it is quietly taking credit away from the campaigns that actually earned the sale. Here is what is happening and how to fix it.
What a self-referral is
A self-referral is when GA4 records a visit as coming from a domain that is really part of your own journey, most often a payment gateway, a booking engine, or a second domain of yours. Because GA4 sees a new referring domain mid-session, it can start a new session and credit that domain instead of the original ad, email or search that brought the person in.
Why it matters
Every self-referral is a conversion stolen from a real channel. Your paid and organic numbers look weaker than they are, your payment provider looks like a top “source”, and your budget decisions get made on distorted data.
How referral exclusions fix it
A referral exclusion tells GA4 to ignore traffic from a given domain as a source, so the session continues and the original source keeps the credit. In GA4 this lives under Admin, in the web stream’s tag settings, as the list of unwanted referrals.
- Open GA4 Admin, your web data stream, then Configure tag settings.
- Open List unwanted referrals.
- Add your payment providers, booking tools and any other domains in your journey (for example stripe.com, paypal.com, your checkout domain).
- Save, then confirm over the next few days that those domains stop appearing as sources.
Is a payment provider stealing your conversions?
We’ll check your live setup for self-referrals and attribution leaks. Free 10-second scan.
Check my tracking freeReferral exclusions and cross-domain go together
Referral exclusions stop the wrong domain getting credit; cross-domain tracking keeps the session joined up as the user moves. For a journey that spans a checkout or booking domain you usually need both, or attribution still leaks.
A quick health check
In GA4’s Traffic acquisition report, look for payment providers, your own domains, or obviously internal tools listed as sources. Anything there that is part of your own funnel is a self-referral to exclude.
Get your GA4 attribution cleaned up
We set referral exclusions and cross-domain correctly so your real channels keep their credit. The audit comes off any build.
See how it works & pricingRelated guides
Cross-domain tracking in GA4 Why paid shows as organic in GA4 GA4 attribution explained PricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Ads, Meta and server-side tracking. See pricing · All guides · Back to datahound.agency
Referral exclusions: common questions
What is a self-referral in GA4?
A self-referral is when GA4 records traffic as coming from a domain that is actually part of your own journey, such as a payment gateway or a second domain of yours. It restarts the session and takes credit away from the real source.
How do I stop my payment provider showing as a source?
Add it to the list of unwanted referrals in GA4 Admin, under your web data stream’s tag settings. That tells GA4 to ignore it as a source so the original channel keeps the conversion credit.
Is a referral exclusion the same as cross-domain tracking?
No, but they work together. Referral exclusions stop a domain being counted as a source; cross-domain tracking keeps the user’s session joined up across domains. Journeys that span a checkout domain usually need both.