Glossary Term

Self-Referral

glossary self referral featured

A self-referral is a session that Google Analytics credits to your own website as the referring source. It shows up in reports as a row like yourdomain.com / referral or checkout.yourstore.com / referral. Self-referrals take credit away from the channel that actually brought the visitor, so they distort both traffic and conversion reports.

Why Self-Referrals Matter

A self-referral replaces the real source of a visit with your own domain. A visitor who arrived from a Google Ads click, completed checkout on a second domain and returned can end up with the purchase credited to that second domain instead of the ad.

The damage shows up in three places:

  • Inflated referral traffic: your own domains appear among top referrers.
  • Lost campaign credit: paid, email and social conversions shift to a referral row.
  • Extra users and sessions: when the visitor gets a new identity on the second domain, GA4 counts one person as two users.

A self-referral is a configuration problem, not a traffic trend. Any row where the referrer is a domain you own needs a fix.

How GA4 Handles Self-Referrals by Default

GA4 already ignores most same-site referrers. Google’s documentation says Analytics doesn’t record a new referrer when “the referring website matched the same domain of the current page or any of its subdomains.” It also ignores the referrer when the page URL contains the cross-domain linker parameter, _gl.

So a click from /blog to /pricing on the same domain never creates a referral. Self-referrals that still appear usually involve a second root domain, a page missing the Google tag, or a third-party site you send visitors through.

Universal Analytics handled this with a Referral Exclusion List in property settings. GA4 replaced it with a per-stream list called List unwanted referrals.

Common Causes of Self-Referrals

  1. Multiple root domains without cross-domain tracking. A journey from brand.com to brand-checkout.com breaks when the second domain cannot read the first domain’s _ga cookie. GA4 issues a new client ID and starts a fresh session credited to brand.com / referral.
  2. Payment processors and booking engines. Visitors who leave for PayPal, Stripe Checkout or a hosted booking page and return can be attributed to that domain. Google lists third-party payment processors as the typical case for unwanted referrals.
  3. Pages missing the Google tag. If a landing page, app domain or help center lacks the tag, or uses a different Measurement ID, the next tagged page records that domain as the referrer.
  4. Redirects that strip _gl. A redirect hop that drops query parameters removes the linker, so the receiving domain cannot match the visitor.

A related mistake: tagging internal links with UTM parameters. It does not create a referral, but it overwrites the original source in the same way. The guide to tracking free tool traffic with UTMs explains why internal links should stay untagged.

How to Fix Self-Referrals in GA4

  1. Find them. In Reports > Acquisition > Traffic acquisition, switch the dimension to Session source / medium and filter for referral. Note every domain you own or control.
  2. Configure your domains. For domains you own, set up cross-domain tracking: Admin > Data streams > your web stream > Configure tag settings > Configure your domains. GA4 then decorates links between them with _gl.
  3. List unwanted referrals. For domains you cannot tag, such as payment processors, go to Configure tag settings > Show all > List unwanted referrals. Google allows up to 50 conditions per data stream, evaluated with OR logic, and requires Editor access.
  4. Tag every page. Confirm each domain and subdomain loads the same Measurement ID.
  5. Verify. Click from one domain to the other and confirm the destination URL carries _gl, then check Realtime for the original source.

Both settings apply going forward only. Sessions already recorded as self-referrals stay that way.

Frequently Asked Questions

What is a self referral in Google Analytics?

A self-referral is a session where Google Analytics lists your own domain as the referring source. It usually means a visitor crossed between two of your domains, or returned from a payment page, and GA4 lost track of where they first came from. The original channel loses credit for that visit and any conversion in it.

Does GA4 exclude self-referrals automatically?

Partly. GA4 ignores referrers on the same domain as the current page or its subdomains, and any page that carries the _gl linker parameter. It does not automatically ignore separate root domains you own or third-party checkout domains. Those need cross-domain tracking or the unwanted referrals list.

What is the difference between cross-domain tracking and unwanted referrals?

Cross-domain tracking passes the visitor’s client ID between domains you own, so GA4 keeps one user and one session. The unwanted referrals list only tells GA4 to ignore a referrer for attribution. Use cross-domain tracking for your own tagged domains and the unwanted referrals list for domains you cannot tag.

Can you remove historical self-referral data?

No. GA4 does not reprocess sessions after you change cross-domain or referral settings. Annotate the date of the fix and compare referral and campaign numbers before and after it. Explorations can filter out the self-referral rows for past analysis, but the underlying attribution stays unchanged.

To confirm a tagged landing page keeps its campaign source in GA4, run it through linkutm’s free GA4 URL tester.