Referral Exclusion

Analytics

Also: Referral Exclusion List · Excluded Referrals

What it fixesFalse referral sessions in your data

Common causePayment gateways and third-party redirects

Effect when setSession continues, source preserved

When to setBefore the traffic problem compounds

Quick definition

A referral exclusion tells your analytics platform to ignore a specific domain when it appears as a traffic source. Instead of starting a new session and crediting that domain with the visit, the platform continues the existing session. Most commonly used to stop payment gateways like Afterpay or PayPal from appearing as traffic sources in Google Analytics 4.

How it varies across Australia

Sites with a checkout redirect to a third-party payment gateway and no referral exclusion configured will see that gateway inflate their referral channel, compress their direct and paid traffic shares, and produce conversion data that is structurally wrong. The problem is common across Australian ecommerce and tends to go unnoticed until someone looks closely at the source breakdown.

See data and tracking scores across Australian industries →

What it actually means

Imagine a customer arrives at your store from a Google Ads click. They browse, add to cart, and proceed to checkout. Your checkout redirects them to an external payment page on afterpay.com or paypal.com. They complete the payment and land back on your confirmation page.

Without a referral exclusion, Google Analytics 4 (GA4) sees the return from the payment domain as a brand new session, attributed to that payment domain as a referral. The original Google Ads click loses credit for the conversion. Your attribution data now says Afterpay drove the sale.

A referral exclusion tells GA4 to treat that domain as a pass-through, not a source. The session continues unbroken and the original traffic source, the Google Ads click, keeps its attribution.

This matters for more than just tidy reports. If your conversion rate, CPA and ROAS figures are all feeding from attribution data corrupted by gateway referrals, every budget decision downstream is slightly or significantly wrong depending on how much checkout traffic hits that path.

The fix lives inside your GA4 property under Admin, Data Streams, Configure Tag Settings, List Unwanted Referrals. You add the domain. GA4 stops counting it as a source.

If Afterpay is your top referral source, you do not have a great affiliate. You have a misconfigured analytics account.

How it shows up

Referral exclusion failures show up as payment gateway domains appearing in your acquisition channel reports under Referral. Common culprits in the Australian market include Afterpay, Zip, PayPal, eWAY, Stripe's redirect flows and bank redirect pages for BPAY or POLi.

They also show up indirectly. If your paid search conversion rate looks unusually low and your referral channel shows suspiciously high conversions, the split is often a gateway attribution error. The paid click drove the customer, the gateway got the credit.

In GA4, check the Traffic Acquisition report filtered to Referral. Any domain you do not recognise as an intentional affiliate or partner is a candidate for the exclusion list.

The Australian context

Australia's buy-now-pay-later (BNPL) market is one of the largest per capita in the world, with Afterpay, Zip and Klarna all maintaining separate checkout domains. Every one of those domains can generate false referral attribution if excluded referrals are not configured. Australian ecommerce analytics is disproportionately affected by this compared to markets where BNPL penetration is lower.

Banking redirects via POLi, a direct-debit payment method popular with Australian utilities and government services, add another category of domain that commonly appears in referral reports when it should not.

Where people get this wrong

Adding the exclusion after months of corrupted data without adjusting historical comparisons.Once you fix the exclusion, referral traffic will drop and direct or paid traffic will rise. Year-on-year comparisons will look like a channel collapse unless you document the date the fix was applied.

Only excluding the top-level domain without accounting for subdomain variants.Payment gateways often redirect through subdomains like checkout.afterpay.com or secure.paypal.com. Excluding paypal.com may not catch all variants depending on how your GA4 tag is configured.

Confusing referral exclusions with unwanted referrals in older Universal Analytics setups.The configuration path and behaviour differs between Universal Analytics and GA4. Teams that migrated to GA4 and assumed their old exclusion settings carried across often find the problem has silently returned.

Common questions

Which domains should I add to my referral exclusion list?

Any domain your users pass through during checkout or login that is not your own. Start with your payment gateway, buy-now-pay-later providers and any single sign-on redirects. In the Australian market, common candidates include afterpay.com, zip.co, paypal.com, eway.com.au and any bank redirect domain your payment processor uses.

Does adding a referral exclusion fix historical data?

No. The fix applies from the moment you add the domain. Past sessions attributed to the gateway remain in your historical reports. Document the date you made the change so anyone reading year-on-year comparisons understands why referral traffic dropped and another channel rose.

How is referral exclusion different from a self-referral exclusion?

A self-referral exclusion stops your own domain from being counted as a referral source, which happens when a session crosses subdomains without cross-domain tracking configured. A payment gateway exclusion stops an external third-party domain from being counted. Both are configured in the same place in GA4 but solve different problems.

Will referral exclusions affect my conversion tracking?

Correctly configured exclusions improve conversion tracking accuracy. The session that drove the conversion stays attributed to its real source rather than being split across a gateway bounce. If your conversion numbers change after adding an exclusion, it means the previous numbers were wrong.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →