Latest Blog Posts

Explore practical insights, SEO strategies, digital marketing tips, and web analytics guides to help your business grow online.

How Configuring GA4 Unwanted Referrals Improved Traffic Attribution

Accurate traffic attribution is essential for making informed marketing decisions. During a recent Google Analytics 4 (GA4) audit, I discovered an issue that caused a significant portion of website traffic to be incorrectly classified as Referral traffic.

 

The website had recently migrated to a new domain while the old domain continued to redirect visitors to the new one. Although the redirect was functioning correctly, GA4 interpreted those redirected visits as referrals, resulting in inaccurate acquisition reports.

The Challenge

After reviewing the Traffic Acquisition report in GA4, I noticed an unusually high volume of referral traffic. A closer look at the Session Source / Medium report revealed that the redirected domain was being recorded as a referral source instead of preserving the user’s original acquisition channel.

This meant that visitors who originally came from sources such as Google Organic Search, Direct, or Social Media were being attributed as referral traffic after the redirect.

As a result:

  • Traffic attribution became inaccurate.
  • Marketing channel performance was distorted.
  • Organic search performance appeared lower than it actually was.
  • Referral traffic was artificially inflated.

The Solution

To resolve the issue, I configured GA4 Unwanted Referrals by adding the old domain to the referral exclusion list.

 

This configuration ensures that redirected visitors are no longer treated as referral traffic. Instead, GA4 preserves the original acquisition source, providing a much more accurate view of how users discover the website.

The Results

After implementing the configuration:

  • Future traffic is attributed to the correct acquisition source.
  • Organic, Direct, and Social traffic are reported more accurately.
  • Referral traffic no longer includes redirected domain visits.
  • Marketing reports provide more reliable insights for decision-making.
  • Historical data remains unchanged, while all future data benefits from the improved attribution.
Why This Matters

Many businesses migrate to a new domain but overlook GA4 referral attribution. Even when redirects are configured correctly, analytics data can become misleading if the old domain is not excluded from referrals.

 

A simple GA4 configuration update can significantly improve data accuracy and ensure your marketing decisions are based on reliable information.

Final Thoughts

If your website has undergone a domain migration, it’s important to review your GA4 Traffic Acquisition reports and Session Source / Medium data. Unexpected referral traffic may indicate that redirected visits are being misclassified.

 

Taking a few minutes to configure GA4 Unwanted Referrals can dramatically improve the accuracy of your analytics and help you better understand where your users are truly coming from.

Frequently Asked Questions (FAQs)

1. What are GA4 Unwanted Referrals?

GA4 Unwanted Referrals prevent specific domains from being counted as referral traffic, ensuring users are attributed to their original traffic source.

2. When should I configure Unwanted Referrals?

Configure them after a domain migration, website redesign, payment gateway integration, or whenever users are redirected through another domain before reaching your website.

3. Does configuring Unwanted Referrals affect historical data?

No. The configuration only applies to future data collection. Previously recorded data remains unchanged.

4. How can I identify unwanted referral traffic in GA4?

Go to Reports → Acquisition → Traffic Acquisition, then change the primary dimension to Session source / medium. If your old domain or your own website appears as a referral source, it may indicate an attribution issue. 

5. Why is my own domain showing as a referral in GA4?

If your own domain or a previous domain appears as a referral source, it may indicate a redirect, cross-domain tracking, or referral attribution issue. Configuring Unwanted Referrals can help ensure traffic is attributed to the correct acquisition source.