What is actually happening
A customer arrives from a Google ad, browses, and goes to checkout. The gateway takes them off your domain to complete payment and returns them afterwards.
Without a referral exclusion, GA4 treats the return as a fresh visit from a new source. The original campaign loses the conversion and the gateway gains one. Your best-performing channel appears to underperform while a payment processor appears to drive sales.
How to check and fix it
- Open your traffic acquisition report and look for a gateway domain in the source list
- Go to Admin, then Data Streams, then your web stream, then Configure tag settings
- Open the list of unwanted referrals and add every gateway domain you use
- Add any other domain customers pass through, such as a booking or scheduling tool
- Verify with a real transaction afterwards rather than assuming it worked
The other settings usually missing alongside it
Properties with this problem usually have company. Internal traffic is not filtered, so your own team inflates the numbers. Key events are either unset or set on a dozen things at once, which dilutes the signal until none of them means anything.
Ecommerce tracking is often partial, firing purchase without the earlier funnel steps, which leaves you unable to see where people drop out.
Why this matters beyond reporting
Misattributed conversions do not only make reports wrong. Where GA4 conversions are imported into Google Ads, the bidding algorithm learns from them, so a broken attribution chain teaches the platform to optimise toward the wrong thing.
That is the expensive version of this problem, and it compounds quietly for as long as the setting is missing.
Key takeaways
- A payment gateway appearing as a traffic source means attribution is broken
- Referral exclusions take two minutes and recover credit for your real channels
- Broken attribution also teaches Google Ads to optimise toward the wrong signal