Referral Exclusions in GA4: How to Handle Payment Gateways, Booking Systems and External Forms
Unwanted referrals in GA4 help prevent a payment gateway, booking system or external form from overwriting the original traffic source.
Short Answer
Unwanted referrals in GA4 help prevent a payment gateway, booking system or external form from overwriting the original traffic source. But they are not a replacement for cross-domain measurement. If your own domains are part of the same user journey, handle cross-domain first and referral exclusions second.
How the Problem Looks in Reports
In GA4, you see orders coming from comgate.cz, gopay.cz, stripe.com, calendly.com or a booking system. In reality, the customer did not come from the payment gateway. The payment gateway was only an intermediate step. If GA4 counts it as a referral, the original campaign source is lost and marketing evaluation is distorted.
A custom domain or subdomain can appear similarly: checkout.example.cz, app.example.cz, rezervace.example.cz. Here you need to distinguish whether this is a domain you can measure as part of one journey, or an external system you simply do not want listed as the source.
Unwanted Referrals vs Cross-domain
Unwanted referrals tell GA4 that a given referrer should not start new attribution. They are useful for payment gateways and external services that are only technical intermediate steps. Cross-domain measurement ensures that a user stays part of one journey across your domains with connected measurement.
If your website is on example.cz and checkout is on checkout.example.cz or another domain you own, cross-domain typically makes sense. If the user leaves for a payment gateway and returns, you often need unwanted referral handling.
Common Mistakes
The first mistake is adding your own domain to unwanted referrals instead of setting up cross-domain correctly. That may hide the self-referral, but it will not fix broken session and identity continuity. The second mistake is forgetting all payment gateway variants: different subdomains, sandbox, production, payment methods or booking provider.
The third mistake is expecting referral exclusion to repair historical data retroactively. GA4 applies the setting to data from that point forward. Historical reports remain as they were collected.
Practical Process
In the Traffic acquisition report, filter referral sources that appear next to conversions. Label them as own domain, payment gateway, booking system, form tool or real referral. For your own domains, design cross-domain measurement. For technical intermediate steps, set unwanted referrals. Then run a test order or booking and watch the journey in DebugView and Realtime.
Watch UTM parameters. If an external system returns the user with its own UTMs, it may overwrite the original source. In that case, you need to address the return URL behavior and provider settings.
How to Know the Fix Works
After the test, the payment gateway should not be the main source of the order. The original campaign should remain preserved, if measurement worked at the beginning. In reports, the share of technical referral sources for conversions should fall. If it falls to zero but direct or unassigned increases at the same time, the problem may be elsewhere: UTMs, cookie consent or cross-domain linking.
FAQ
Frequently Asked Questions
Next Article
GA4 cross-domain measurement
Cross-domain measurement in GA4: when you need it and how to tell if it is not working correctly
You need cross-domain measurement in GA4 when users move between multiple domains that belong to one journey, such as website -> checkout -> thank-you page.
Looking for someone who can take this off your plate?
We will check self-referrals, payment gateways and cross-domain settings so GA4 does not overwrite conversion sources with technical intermediate steps.