How to Configure Google Analytics 4 Unwanted Referrals List

Seeing a boost in referral traffic usually feels like a win, but sometimes those numbers hide a data-messing secret. If you've ever seen payment gateways like PayPal or even your own website showing up in your traffic reports, you're looking at unwanted referrals that skew your data. This article will walk you through exactly how to clean up your reports by configuring the unwanted referrals list in Google Analytics 4.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What is Referral Traffic, Anyway?

Before we start excluding traffic, let's quickly define what we're talking about. In Google Analytics, referral traffic is recorded whenever a user clicks a link from another website to get to yours. Think of referrals as digital word-of-mouth. Someone found your content or product valuable enough to link to, and a visitor followed that link.

In a perfect world, your referral report would be full of high-quality sources, including:

• Blogs or publications that have featured your business.
• Partner websites you collaborate with.
• Social media platforms where your content is shared.
• Forums or communities discussing your products.

This is the good stuff. It tells you who is sending you valuable visitors and helps you understand where your brand has an impact online. But not all referral traffic is created equal.

Data Dirtying: Why You Must Exclude Unwanted Referrals

Ignoring unwanted referrals is like leaving muddy footprints all over a clean floor, it just makes a mess of your data. The core problem is that these incorrect sources get credited for sessions and, more importantly, conversions that they didn't actually generate. Let's look at the three most common culprits.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

1. Misattribution from Payment Gateways

This is arguably the most critical referral issue for any e-commerce or lead-generation site. Imagine this common user journey:

1. A user clicks on one of your Facebook Ads and lands on your product page. From GA4's perspective, this session source is correctly identified as facebook.com with a medium of cpc.
2. They love the product, add it to their cart, and proceed to checkout.
3. For payment, they choose PayPal. Your site redirects them to paypal.com to securely log in and approve the payment.
4. After approving, PayPal redirects them back to your your-site.com/thank-you page to confirm the order.

Here’s where it gets messy. When the user returns from paypal.com, GA4 can mistakenly see this as the start of a new session. It attributes the source of this "new" session to paypal.com because that's the last site the user came from. If your conversion event (like purchase) fires on that thank you page, GA4 will wrongly give credit for the sale to PayPal, not the Facebook Ad that actually brought the customer to your store.

Suddenly, your reports will suggest that PayPal is a major marketing channel driving sales, while the true drivers like your ads, email campaigns, or organic search efforts are being severely under-credited. This leads to poor marketing decisions because you're allocating budget based on faulty data.

Common payment gateway referrals to watch for include: paypal.com, stripe.com, klarna.com, shop.pay.com, authorize.net, and many others.

2. The "Self-Referral" Problem

A self-referral happens when your own domain (e.g., your-brand.com) appears as a referral source in your traffic reports. This is like getting a letter in the mail from yourself - it’s just weird and shouldn't happen.

Self-referrals are a red flag indicating session breakage. It typically occurs when a user moves between different subdomains without proper cross-domain tracking setup (e.g., from shop.your-brand.com to blog.your-brand.com) or if a session times out and the user re-engages by clicking a link on your own site. When this happens, GA4 thinks the user left your site and came back from a new source, which was just another page on... your site. This breaks the original attribution and hides the true entry point of the user.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

3. Spammy and Misleading Third-Party Interactions

Sometimes, the redirects aren't from payment processors but from other third-party tools integrated into your website. This could be anything from a third-party login service (like login.microsoftonline.com), a booking engine, or an external support portal. Just like with payment gateways, as the user is passed from your site to the third-party and back again, GA4 can lose the original source and incorrectly attribute the session to the third-party service, polluting your reports.

Step 1: How to Find Unwanted Referrals in GA4

You can't fix what you can't find. First, you need to audit your referral traffic to identify which domains are causing problems. Don't worry, this only takes a few clicks.

1. Log in to your Google Analytics 4 account.
2. On the left-hand navigation panel, go to Reports.
3. Under the Life cycle section, click on Acquisition → Traffic acquisition.
4. The default table groups traffic by Session default channel group. Click the dropdown arrow on this primary dimension and change it to Session source / medium. This will give you a more granular view of exactly where your traffic is coming from.
5. Scan this report for any suspicious or known troublemakers. Look specifically for payment processor domains (paypal.com), your own domain, or any third-party app domains that you know are part of your user flows but aren't legitimate marketing channels. If you have a lot of traffic, you can use the search bar above the table to look for specific sources like "paypal".

Take note of any domains that shouldn’t be there. This is your "hit list" for the next step.

Step 2: How to Configure the GA4 Unwanted Referrals List

Once you’ve identified the domains you want to exclude, adding them to the unwanted referrals list is straightforward. This simple configuration tells Google Analytics, "If a user arrives from one of these domains, don't treat it as the start of a new session. Instead, carry over the attribution from the previous session."

Here’s how to set it up, step by step:

1. In the bottom-left corner of your GA4 interface, click the Admin icon (the gear symbol).
2. Make sure you’re in the correct Account and Property. In the Property column, click on Data Streams.
3. You'll see a list of your data streams. Click on your primary web data stream (the one for your website).
4. Scroll down to the bottom of the Web stream details page and click on Configure tag settings under the Google tag section.
5. This will open a new screen. Under the Settings block, it will show a few options by default. Click the Show all button to expand the list.
6. Now you'll see more options. Find and click on List unwanted referrals.
7. You're here! This is where you'll build your exclusion list. For each domain you wish to add, you need to configure two things:
8. Click the Add condition button to add another domain to the list. Repeat this process for all the unwanted referral domains you identified in the previous step, such as paypal.com, stripe.com, and even your own website’s domain to prevent self-referrals.
9. Once you’ve added all the domains, click the blue Save button in the top-right corner.

That's it! Your tag is now configured to ignore traffic from these referral sources, which will preserve the true attribution for users who pass through them.

Important Things to Know Before You Finish

Configuring the unwanted referrals list is a powerful step towards data accuracy, but there are a few key things to keep in mind to have the right expectations.

This setting is NOT retroactive.

The changes you just made will only apply to data collected from this point forward. It will not go back in time to clean up your historical reports. This is a crucial point - don't expect last week's data to suddenly change. You'll start seeing cleaner data moving forward.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

'Unwanted Referrals' vs. 'Define Internal Traffic'

GA4's admin panel also has a feature called Define internal traffic. This might sound similar, but it serves a very different purpose. The internal traffic filter is designed to exclude activity from your own team, agency, or developers by filtering out specific IP addresses. The unwanted referrals list is for correcting traffic attribution from legitimate third-party websites involved in a user's session. Don't mix them up!

Regularly Audit Your List

Your business evolves. You might add new payment options, integrate new software, or change service providers. Make a habit of checking your Traffic acquisition report once a quarter to spot any new unwanted referrals that might have popped up and add them to your exclusion list.

Final Thoughts

Setting up your GA4 unwanted referrals list is one of the most impactful 10-minute tasks you can do for your data integrity. By excluding payment gateways and preventing self-referrals, you ensure that credit for your hard-earned conversions goes to the correct marketing channels, giving you a crystal-clear picture of what's actually working.

Wrestling with GA4 setup and attribution can sometimes feel like just one more task on a never-ending list. At Graphed , we automate the hard parts. By connecting directly to your tools like Google Analytics, Shopify, and your ad platforms, we instantly bring all your data into one place. From there, you can just ask questions in plain English, like "which campaign drove the most revenue last month?" and get an interactive, real-time dashboard in seconds, with all the attribution already sorted out.