Without the right exclusion list, GA4 can count a visitor’s own journey between your payment gateway and your site as a “referral” from that gateway, or count your own domain as if it referred traffic to itself — both of which quietly inflate referral numbers and misattribute traffic that was never actually external in the first place.
Check your Referral traffic report for your own domain
In GA4, look at the Traffic acquisition report and check whether your own domain name appears as a source. If it does, that’s a direct, confirmable sign of self-referral, distinct from a genuine third-party referral source that legitimately sent you traffic.
Referral exclusion & self-referral fix
Your own domain or payment gateway showing up as a referral source, fixed at the exclusion-list level.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Your own domain, or a payment gateway you use, appears as a referral source | This fix covers it |
| Referral sources look accurate and this isn’t actually a concern | No fix needed; worth a second look to confirm before ordering |
| Cross-domain tracking between two of your own sites isn’t working | Cross-domain tracking configuration, a related but different fix |
| GA4 numbers are wrong for a different reason entirely | GA4 not tracking – diagnosis & fix, a broader diagnosis |
What you are seeing
- Your own domain name listed as a referral source in GA4 reports
- A payment gateway or third-party checkout appearing as a referral source
- Referral traffic numbers that seem implausibly high for genuinely external sites
- Session counts that seem inflated compared to what direct or other channels would suggest
Common causes
- The payment gateway or checkout domain not added to GA4’s referral exclusion list
- Cross-domain tracking not configured for a legitimate related domain you operate
- A subdomain being treated as an external referrer rather than part of the same site
- Single-page application behaviour causing GA4 to misread internal navigation as a new referral
- The referral exclusion list simply never having been configured since GA4 setup
What we do
- Identify every domain incorrectly appearing as a referral source
- Determine whether each needs referral exclusion or proper cross-domain configuration
- Configure the referral exclusion list correctly in GA4
- Set up cross-domain tracking if a legitimate related domain is involved
- Verify with test traffic that the domains no longer appear as referrals
- Confirm genuine third-party referral sources are still tracked correctly
What is included
- Self-referral and gateway domains correctly excluded
- Cross-domain configuration if that was part of the cause
- Verified testing that genuine referrals still track correctly
- A written note on what was misconfigured
Not included
- Correcting historical reports already affected — that data stays as recorded
- Setting up GA4 itself, if not already connected
- Auditing every traffic source for accuracy beyond referral exclusion
- Ongoing adjustment as you add new payment gateways or related domains later
Questions about this fix
Can you fix the referral numbers I've already got in my reports?
No — this stops it happening going forward, but GA4 doesn't allow retroactively reclassifying how historical sessions were attributed.
How would I even notice this was happening?
Usually by looking closely at referral sources and spotting something oddly familiar, like your own domain or checkout provider — it rarely announces itself any other way.
Does this affect my Google Ads or other paid attribution too?
It can, if misattributed sessions are being counted as referral rather than the correct channel, which affects how you'd judge which channels are actually working.
Will excluding my payment gateway hide genuinely useful data?
No — excluding it from referral attribution doesn't stop the purchase itself from being tracked, it just stops the checkout handoff from being miscounted as a new traffic source.
Is this a common issue, or unusual?
Common enough, particularly for sites using an external payment gateway or checkout — it's one of the more frequently overlooked parts of initial GA4 setup.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.