Referral Exclusion in GA4

February 6, 2026
  • First Published: February 6, 2026
  • Last Modified: February 7, 2026

When you dive into Google Analytics 4 (GA4) to see which channels are driving conversions, you see something frustrating: a huge chunk of your sales is being attributed to paypal.com or stripe.com or another referrer that you didn’t want.

Unless PayPal has suddenly started running ads for you out of the goodness of their heart, you have an attribution problem.

This happens because GA4 sees these third-party domains as the “last non-direct click” before a conversion.

Instead of seeing that a customer came from your LinkedIn ad, GA4 thinks they came from the payment processor they used to finish the checkout.

In this guide, we’ll walk through how to plug these “attribution leaks” using the List Unwanted Referrals feature in GA4.

Table of Contents

Key Takeaways

    • Accuracy is Everything: Referral exclusion ensures credit goes back to the original marketing source (like Email or PPC) rather than a utility domain.

    • Common Culprits: Third-party payment processors and password recovery email domains are the most frequent offenders.

    • Self-Referrals are History: Unlike the old days of Universal Analytics, GA4 handles your own subdomains automatically.

    • The 50-Domain Limit: You can exclude up to 50 domains per data stream.

Why care about excluding referrers?

By default, GA4 identifies where traffic was immediately before it landed on your site. If that source is a different domain, it’s logged as a “referral.” Unless of course it matches a different condition e.g. from Google Search.

While that’s usually helpful, it becomes a headache when the third-party domain is actually part of your user journey.

When a user hops over to Stripe to pay and then bounces back to your “Thank You” page, GA4 triggers a new session.

A huge way to see this is if your revenue data is attributed to referral in your traffic reports. Or if you check your landing page report, and you see loads of checkout confirmation pages as landing pages.

When you configure an unwanted referral, GA4 appends a special parameter -ignore_referrer=true – to every event.

This tells the system: “Don’t start a new session here, and keep the original source alive.”

The Most Common Use Cases

Payment Processors: If you use PayPal, Stripe, or Klarna, these need to be on your list.

Authentication Tools: Think of password recovery emails or third-party login portals.

Cross-Domain Business Tools: Any external site that is essentially an extension of your business rather than a source of new traffic.

How to Configure Unwanted Referrals

Ready to clean up your data? Follow these steps within your GA4 interface.

  1. Head to the Admin section.
  2. Under Data collection and modification, click on Data Streams.
  3. Select your primary Web data stream.
  4. Scroll down and click on Configure tag settings.
  5. Click Show all to reveal the full menu, then select List unwanted referrals.
  6. Under Include referrals that match ANY of the following conditions, choose your match type (usually “Domain contains”) and enter the URL (e.g., paypal.com).
  7. Click Save.
Referral Exclusions

Common Payment Processors to exclude

Here are some common payment processors domains to exclude (I do these especially for Shopify set ups)

  • payments.amazon.co.uk
  • klarna.com
  • paypal.com
  • hooks.stripe.com

Why Am I Still Seeing Excluded Domains in My Reports?

It’s a common frustration –  you’ve added paypal.com to the list, but it’s still showing up in your reports today.

Before you throw your laptop out the window, remember two things:

Historical Data: Referral exclusions are not retroactive. They only apply to traffic moving forward from the moment you hit save.

Last non-direct click: If a user first arrived via a referral before you excluded the domain, and then they return via a bookmark (Direct), GA4’s last non-direct click model will still attribute that new session to the old referral. 

Best Practices for a Clean Data Set

Keeping your GA4 house in order isn’t a “set and forget” task. Here’s how to stay on top of it:

  • Audit Your Referrals Monthly: Go to your Reports > Acquisition > Traffic acquisition and filter by “Session source/medium.” If you see a domain that looks like a tool rather than a source, add it to your exclusion list.
  • Manage Your IP Filters: While we’re talking about clean data, don’t forget to exclude internal traffic from your office or agency IP addresses so your own clicks don’t skew the results.
  • Test and Verify: After adding a domain, perform a test transaction. Use the GA4 DebugView to ensure the ignore_referrer parameter is firing as expected.

Ready to Fix Your Attribution?

Accurate data is the bedrock of every good marketing decision.

If you haven’t checked your referral list lately, there’s a good chance your ROI figures are being skewed by your own tech stack.

Frequently Asked Questions

Does excluding a referral delete the traffic data?

No. The traffic still arrives at your site, but GA4 won’t start a new session or change the attribution source. It simply treats the visit as a continuation of the previous session.

How many domains can I exclude?

You can configure a maximum of 50 unwanted referrals per data stream.

Do I need to exclude my own subdomains?

No. GA4 automatically recognises traffic between your subdomains (like shop.yoursite.com and yoursite.com) as internal, so they won’t trigger new referrals.

What match type should I use?

“Domain contains” is usually the safest bet for payment processors, as it covers various regional subdomains (like uk.paypal.com and us.paypal.com) in one go. Be careful with regex because you might exclude stuff you don’t want to.

Kyle

Author

Hello, I'm Kyle Rushton McGregor!

I’m an experienced GA4 Specialist with a demonstrated history of working with Google Tag Manager and Looker Studio. I’m an international speaker who has trained 1000s of people on all things analytics.

Find out more About me
Scroll to Top