How to Fix Self Referrals in Google Analytics

Seeing your own website listed as a top traffic source in Google Analytics is a classic "wait, what?" moment for anyone tracking their marketing performance. This strange issue, known as a self-referral, can quietly sabotage your data, making it incredibly difficult to know which channels are actually driving traffic and conversions. This tutorial will walk you through exactly what self-referrals are, why they're harmful, and how to fix them for good in Google Analytics 4.

Graphed

Still Building Reports Manually?

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

Watch the Demo

What Are Self-Referrals in Google Analytics?

A self-referral happens when Google Analytics records a new session as coming from your own domain or one of your subdomains. In a perfect world, a user’s entire visit from start to finish - no matter how many pages they view on your site - should be counted as a single session tied to their original traffic source (like Google Search, a Facebook Ad, or an email campaign).

However, when a self-referral occurs, Analytics mistakenly ends the original session and starts a brand new one, attributing it to your own website. It’s like a person walking into your store, and halfway through their shopping trip, you mark them down as a "new customer" who was referred by your own store. It doesn't make sense, and it seriously messes up your records.

Here’s a common example:

• A user clicks a link from your newsletter and lands on yourblog.com/new-post. Their source is correctly identified as "Email."
• They click a "Shop Now" button that takes them to your e-commerce platform on a subdomain: shop.yourblog.com.
• They complete their purchase and are redirected back to your main site on a thank-you page: yourblog.com/thank-you.

If not configured properly, GA4 might see the jump from shop.yourblog.com back to yourblog.com as a new referral. It ends the "Email" session and starts a new one with the source listed as shop.yourblog.com, breaking the connection to the original marketing campaign that brought the customer in.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Why Self-Referrals Are Such a Problem

At first glance, self-referrals might seem like a minor annoyance, but they cause a domino effect of data integrity issues that can lead to poor marketing decisions. Here's why you need to fix them immediately.

1. They Break 'Source of Truth' Attribution

The number one job of your analytics is to tell you what's working. Self-referrals destroy that ability. The original traffic source that deserves credit (Organic Search, Paid Social, Email, Direct, etc.) gets discarded midsession. Instead, your own domain gets the credit for any conversions that happen after the break. This leads you to think your marketing channels are underperforming and your "Referral" traffic is higher than it actually is.

2. They Skew User Behavior Metrics

Self-referrals don't just create a new session, they artificially inflate your total session count. This has a direct impact on other important metrics:

• Average Session Duration: An individual's real 10-minute visit might be split into two 5-minute sessions, dragging your average duration down.
• Pages Per Session: Similarly, a single 8-page journey might get split into two 4-page sessions.
• Bounce Rate (in older Universal Analytics) / Engagement Rate (in GA4): By breaking a single engaged session into two, you can get misleading signals about user engagement.

3. It's Impossible to See the Full Customer Journey

Trying to understand how users navigate your site becomes impossible. You can't connect the dots between that initial Facebook ad click, their browsing session on the blog, and their final purchase on your Shopify subdomain. The journey is broken, leaving you with incomplete and frustrating reports.

How to Find Self-Referrals in a GA4 Report

Before you can fix the problem, you need to confirm it exists. Finding self-referrals in GA4 is simple.

1. Navigate to your Google Analytics 4 property.
2. In the left-hand menu, go to Reports > Acquisition > Traffic acquisition.
3. The default report shows "Session default channel group." Below the chart, you'll see a search bar above the data table. Type your website's domain name into the search bar (e.g., yourwebsite.com).
4. Look at the results. If you see your own domain or any of your subdomains (like shop.yourwebsite.com or blog.yourwebsite.com) listed as a traffic source with sessions attributed to it, you have a self-referral problem.

Now that you've identified the issue, let's explore why it's happening.

Common Causes of Self-Referrals

Understanding the root cause will help you confidently apply the fix. Most self-referrals stem from a handful of common setup issues.

Graphed

Still Building Reports Manually?

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

Watch the Demo

Cross-Subdomain Tracking

This is the most frequent cause. If your website experience involves users moving between your main domain (www.brand.com) and one or more subdomains (blog.brand.com, checkout.brand.com, portal.brand.com), GA4 needs to be explicitly told that these are all part of the same entity. Without proper configuration, it treats each subdomain as a separate website.

Third-Party Payment Gateways

Sometimes, users are sent off-site to a payment processor like PayPal Standard or Stripe Checkout and then redirected back to your "thank you" page. If the payment gateway domain isn't correctly excluded, the user’s return to your site can be seen as a new referral session originating from the payment provider.

Improper GA4 Tagging

Cross-domain or cross-subdomain tracking relies on the same GA4 Measurement ID (G-XXXXXXXXXX) being implemented across all relevant pages. If different tags are used on different parts of your site, Analytics will never be able to stitch together the sessions correctly.

How to Fix Self-Referrals in Google Analytics 4

Thankfully, GA4 has made fixing this much easier than it was in Universal Analytics. GA4 uses something called the "unwanted referral list". This list tells Google Analytics which domains it should ignore as traffic sources. When a user arrives at your site from a domain on this list, GA4 will not start a new session. Instead, it will preserve the original session's source, medium, and campaign information.

For example, by adding yourwebsite.com to this list, you are telling GA4: "If a user is already on my site and then comes back from shop.yourwebsite.com, don't count it as a new referral. Let the original session continue."

Graphed

Still Building Reports Manually?

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

Watch the Demo

Step-by-Step Guide: Adding Your Domains to the Unwanted Referral List

Follow these steps carefully to resolve your self-referral issues.

1. Log in to Google Analytics 4 and navigate to the Admin section (click the gear icon in the bottom-left corner).
2. Make sure you have the correct Account and Property selected. In the 'Property' column, click on Data Streams.
3. Click on the specific web data stream that needs fixing.
4. Scroll down and at the bottom of the 'Web stream details' page, click on Configure tag settings under the 'Google tag' section.
5. This will open the Google tag configuration screen. Under the 'Settings' section, click Show more to expand all the options.
6. From the expanded list, find and click on List unwanted referrals.
7. You'll now see the configuration screen for your referral list. Under 'Match type,' leave the default selection "Referral domain contains."
8. In the 'Domain' field, enter your core domain name. For example, if your site is www.coolbrand.com and you have a subdomain at shop.coolbrand.com, you only need to enter coolbrand.com here. The "contains" match type will automatically cover "www", all subdomains, and the root domain.
9. Click the Add condition button. If you use a third-party payment system like PayPal that you also want to exclude, add another condition for paypal.com.
10. Once you've added all relevant domains, click the Save button in the top-right corner.

That's it! Your update is saved and GA4 will now start ignoring those domains as referral sources moving forward.

How to Check if Your Fix Worked

It's important to remember that this change is not retroactive. It will not fix your historical data. It will only apply to the data collected from this point on.

Wait at least 24-48 hours for new data to accumulate. Then, return to your Traffic acquisition report (Reports > Acquisition > Traffic acquisition). Check for your domain again. Over the new date range, you should see sessions from your self-referrals drop to zero. Your other marketing channels, like Organic Search, Email, and Paid, should now be getting the full credit they deserve for driving conversions and engagement.

Final Thoughts

Fixing self-referrals is a fundamental step toward achieving data clarity in Google Analytics. By adding your own domains to the unwanted referral list, you ensure sessions are attributed correctly, user behavior is tracked accurately, and your marketing decisions are based on a true picture of performance.

We know firsthand how agonizing it is to fight with data misconfigurations or spend half your Monday manually pulling reports. At Graphed, we're building a solution to end that process. By connecting your sources like Google Analytics, Shopify, and your ad platforms, we automatically pipe in clean, real-time data so you can just ask questions in simple English - like "Which marketing channels drove the most sales this month?" - and get instant dashboards and answers you can trust.