GA4 Unwanted Referrals: How to Exclude Self-Referrals and Payment Domains
Quick fix
GA4 unwanted referrals happen when traffic returning from a payment processor, an email link or one of your own domains is treated as a new source. Create conditions listing the domains you don't want counted as referrals, then check every page is tagged and cross-domain measurement and cookie domains are set up. Earlier sessions may keep their old attribution.
- Identify the domains showing as referrals that are really part of your journey.
- Add conditions for those domains in the unwanted referrals list.
- Check every page is tagged and cross-domain is configured.
- Check subdomains share a cookie domain.
Can't fix it yourself? Send me the details
What this error means
A referral is traffic that arrives from another site. When users leave to pay or reset a password and come back, that return trip can look like a new referral, replacing the real source. An unwanted referrals list tells GA4 to ignore those domains.
Why it happens
1Payment processors
Returning from a third-party checkout counts as a referral.
How to tell if this is you: The payment domain appears as a top referral.
2Website-managed interactions
Password recovery and similar emails can return traffic.
How to tell if this is you: An email domain shows as a referral.
3Your own subdomains or domains
Different cookie domains or missing cross-domain setup create self-referrals.
How to tell if this is you: Your own domain shows as a referral.
4Earlier attribution
Sessions already attributed to a domain can carry it forward.
How to tell if this is you: Returning users still show the excluded domain.
How to fix it
List the unwanted referrals
For: Payment processors, Website-managed interactions
- Create conditions for the domains you do not want counted as referrals.
- They apply on every page with the Google tag.
Fix self-referrals
For: Your own subdomains or domains
- Make sure all pages are tagged and cross-domain measurement is set up on all of them.
- Check all subdomains use the same cookie domain.
How long it takes
Google doesn't publish a timeline for this.
How to stop it happening again
- Review the referral list when you add a payment provider or tool.
- Use cross-domain measurement for multi-domain journeys.
- Keep subdomains on one cookie domain.
From my desk
Payment gateways come up most, because customers leave to pay and return as a new referral. After that it's the client's own booking or login domains, and sometimes the email domain after password resets. I add those to the unwanted referrals list, then check cross-domain setup so the real source survives the trip.
Muhammed Abdul Kalam
When to get help
- You've worked through the checks and the status still isn't changing.
- The account has many campaigns and ad groups and you cannot tell which change caused the problem.
- Results are suffering during a launch or sale and every day costs real money.
Stuck on this? Send me the details.Tell me what the platform shows and what you've tried so far.
Send me the detailsFAQs
What is a referral?
Traffic arriving through another source, such as a link on a third-party domain.
How do I exclude a domain?
Create conditions that identify domains whose traffic you do not want counted as referrals.
What does GA4 add to matching events?
An ignore_referrer parameter set to true.
Why do payment gateways show up?
Users returning from a third-party checkout arrive as referral traffic.
Does GA4 handle self-referrals?
By default it does not treat self-referring traffic as a new referrer.