Skip to content
GA4

Own domain or payment gateway showing as a referral in GA4

In GA4 acquisition reports, your own domain, a booking subdomain, or a payment provider such as Stripe or PayPal appears as a referral source, often with key events credited to it instead of the ad or channel that brought the visitor.

Steps checked against the platforms' documentation on November 20, 2026.

Quick answer

A self-referral means the visitor's session was broken when they moved between domains or came back from another site, so GA4 started a new session and credited the previous page as the referrer. For your own domains, check that every domain uses the same GA4 tag ID and is listed under Configure your domains. For payment gateways, add them under List unwanted referrals.

1. Cross-domain measurement is not configured for all your domains

When a visitor moves from your main site to a separate checkout, booking or landing page domain, GA4 cannot share its cookie across domains unless cross-domain measurement passes the IDs along in a _gl URL parameter. Without it, the second domain starts a new session with the first domain as the referrer.

How to check

  1. 1In GA4 go to Admin > Data streams, open the web stream, click Configure tag settings and then Configure your domains.
  2. 2Confirm every domain in the journey is listed. Check the Recommendations area for domains GA4 has already seen with the same tag.
  3. 3On the live site, click a link from one domain to the other and check that the destination URL contains _gl=.

How to fix

  1. 1Add each domain with Add condition, choosing a match type and entering the domain, then click Save. Google allows up to 100 conditions.
  2. 2Repeat the click test and confirm _gl is present on the destination URL.
  3. 3If the journey moves between domains through a form post, make sure the form is decorated too. In a gtag.js setup that means decorate_forms, which is off by default.

2. The domains use different GA4 tags or measurement IDs

Cross-domain measurement only works when every domain sends data with the same G- tag ID from the same web data stream. Agencies often find a booking engine, shop or old landing page builder sending data to a different stream or property.

How to check

  1. 1Open each domain with Tag Assistant connected and note which G- IDs load on the page.
  2. 2Check the page source or GTM container on each domain for hard-coded gtag snippets with a different ID.
  3. 3Look for a second GA4 tag fired by a plugin, theme or third-party platform in addition to the one in GTM.

How to fix

  1. 1Use one tag ID from one web stream on every domain in the journey.
  2. 2Remove leftover tags from old properties or plugins so each page sends data to the intended stream once.
  3. 3Re-test the cross-domain click and confirm one continuous session in DebugView.

3. A payment gateway or third-party service sends users back to your site

Visitors who pay on Stripe, PayPal or a similar hosted checkout, then return to your thank-you page, arrive with that provider as the referrer. GA4 starts a new session credited to the provider, and the purchase or lead loses its original source.

How to check

  1. 1In Reports > Acquisition > Traffic acquisition, set the dimension to Session source / medium and look for payment domains such as checkout.stripe.com or paypal.com.
  2. 2Note which key events are credited to those sources.
  3. 3Run a test payment and watch the return in DebugView or Realtime to confirm the referrer.

How to fix

  1. 1In GA4 go to Admin > Data streams, open the web stream, click Configure tag settings, click Show all and then List unwanted referrals.
  2. 2Add each payment domain with Add condition and click Save. Google allows up to 50 unwanted referrals per data stream.
  3. 3Google notes that a user who previously arrived from an excluded domain can still be attributed to it on a later return, so expect the source to fade out rather than disappear on day one.

4. Subdomains are tagged inconsistently

Moving between www and a subdomain such as shop or book should not normally start a new session, but it can when the subdomain is untagged, uses a different tag or sets cookies on a different cookie domain. Google lists this as a common source of self-referrals.

How to check

  1. 1Visit each subdomain with Tag Assistant and confirm the same tag ID loads on every page.
  2. 2Check whether any custom code sets a specific cookie_domain on one subdomain but not the others.
  3. 3Look in traffic acquisition reports for your own subdomain listed as a source.

How to fix

  1. 1Tag every page on every subdomain with the same tag ID.
  2. 2Use the same cookie domain for all subdomains, and remove custom cookie settings that differ between them.
  3. 3Add your subdomains to the cross-domain configuration as Google recommends, and add them as unwanted referrals if self-referrals persist.

5. A redirect or script strips the _gl parameter

The _gl parameter only carries the session across if it reaches the destination page. Redirects that drop query strings, or scripts that stop link clicks from bubbling up to the page, break the hand-off even when the domains are configured correctly.

How to check

  1. 1Click the cross-domain link and watch the address bar and network panel. If _gl appears on the first URL but not on the final one, a redirect is stripping it.
  2. 2Check whether the link is triggered by JavaScript instead of a normal link, which can stop it being decorated.
  3. 3Note that Google says linker parameters expire after two minutes, so a link copied and opened later will not carry the session.

How to fix

  1. 1Ask the developer to make redirects preserve query parameters.
  2. 2Use normal links or have the developer decorate JavaScript-driven navigation.
  3. 3Re-test until _gl is visible on the final landing URL of the second domain.

Stop it happening again

  • Keep a list of every domain and subdomain in each client's journey, including booking and payment steps, and the GA4 tag ID each one should use.
  • Add payment providers to unwanted referrals when a new checkout or payment method goes live.
  • Run a cross-domain click test after any redirect, checkout or booking engine change.
  • Review the top referral sources each month and investigate any of your own domains or payment providers that appear.

Questions

4 questions

No. It applies to data collected after you save it. Past sessions keep the referral source they were given.

Fix the cause first: same tag ID everywhere, cross-domain measurement and consistent cookie domains. Unwanted referrals hides the referrer but does not repair a broken session, so treat it as a backstop rather than the fix.

Google recommends including subdomains in the configuration. Moving between subdomains is usually fine on its own, but different cookie domains or missing tags on a subdomain can still create self-referrals.

The visitor returned from the payment page to your thank-you page, so GA4 started a new session with the provider as the source. Add the provider under List unwanted referrals so the return is not treated as a new referral.

Got an account that doesn't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.