TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-023

SYMPTOM FILE SYM-023 FILED 05 NOV 2026 · REVISED 19 NOV 2026

GA4 cross-domain tracking not working: how to set it up and why sessions still split.

ALSO FILED AS
  • “GA4 cross-domain tracking not working”
  • “how to set up cross-domain tracking in GA4”
  • “GA4 Configure your domains”
  • “GA4 sessions split across domains”
  • “GA4 cross-domain _gl parameter missing”
  • “_gl parameter not added to links”
  • “_gl parameter stripped by redirect”
  • “cross-domain set up but sessions still split”
  • “one user counted as two users across domains in GA4”
  • “GA4 cross-domain not working with Google Tag Manager”
  • “GA4 cross-domain tracking form submit”
  • “booking or checkout on a different domain breaks GA4 sessions”
  • “GA4 shows my own domain as a referral”

Baris Asa, tracking consultant, London · Last checked: 19 November 2026

To set up cross-domain tracking in GA4, list every domain under Configure your domains in your web stream’s tag settings, and run the same G- tag on every page of both. If GA4 still splits one visit into two sessions at the hop, the second domain never got the visitor’s ID, or got it and lost it. The ID travels in a URL parameter called _gl. Click across and read the address bar: no _gl means the link was never decorated, _gl gone after a redirect means it was stripped.

In GA4 it looks like this: your first domain listed as a referral, sessions that start on a basket, booking or checkout page, and one visitor counted as two users. The order or lead is real. It is credited to your own site instead of the ad or email that brought the visitor.

Some split is normal. A visitor who declined analytics cookies has no _ga cookie to carry. Safari’s cookie limits drop returning visitors (F-401 ). A split that follows one hop, on every browser, usually points to a fault.

This split is on file as F-205 , self-referrals and session fragmentation. If the referral row reads paypal.com or stripe.com rather than your own domain, that is the other branch of the same fault: see payment gateway showing as a referral in GA4. This note covers the cross-domain branch: two root domains you own, such as a shop and a checkout, a site and a booking engine, a brand domain and a regional one.

How does GA4 join two domains?

Each domain has its own cookies. Without help, the second domain sets a new _ga cookie, and GA4 files a new user and a new session. Cross-domain measurement fixes that by adding _gl to links between the domains you list. The tag on the destination reads it and keeps the same IDs. Google says linker parameters expire after two minutes, so the tag adds _gl at the moment of the click.

How do I set up cross-domain tracking in GA4?

Google’s recommended route is the Admin screen, not code. You need the Editor role or above in Google Analytics.

  1. Open the domain list. GA4 Admin, Data collection and modification, Data streams, Web, your stream. At the bottom, Configure tag settings. Under Settings, Configure your domains.
  2. Add every domain in the journey. Domains already sharing your tag show under Recommendations: click Add. Add the rest with Add condition, a match type and the domain (example.com). A domain matching any one condition counts. Up to 100 conditions. Save.
  3. One tag, one stream. Every page on every domain loads the same G- tag ID from that web data stream, including the page the visitor lands on after the hop.
  4. Check for a GTM override. If the Google tag in Tag Manager has a linker setting, it replaces this list. Remove it, or make it list every domain.
  5. Test the hop. Click a link or submit a form from one domain to the other. The destination page loads normally and its URL carries _gl=1.... If your site offers downloads, start one from a page with _gl in its URL and check it still works.

Google notes that the list also decides which links stop counting as outbound clicks, and that changing it can affect other Google tags on the page. Sessions recorded before the change stay split.

If step 5 shows no _gl, or _gl that vanishes, the rest of this note finds where it breaks.

A check you can do yourself

No developer needed. Use Chrome on a laptop.

  1. The report. In GA4, Reports, Acquisition, Traffic acquisition, set the primary dimension to Session source / medium and search for your first domain. A row reading yourshop.com / referral is the split.
  2. The click. Open your first domain, accept analytics cookies, and click the link or button that takes you to the second. Read the address bar on arrival.
  3. The cookie. On each domain, open DevTools, Application, Cookies, and find _ga. The numbers after GA1.1. or GA1.2. should be identical on both.

Read it like this:

  • _gl=1*... in the URL and the same _ga on both sides. Linking works. If the referral row persists, look at the hops that aren’t links (below).
  • No _gl at all. The link wasn’t decorated. See Why isn’t _gl added?
  • _gl on the first URL, gone after the page settles. A redirect stripped it. See Why does _gl disappear?
  • _gl present but a different _ga on arrival. The destination isn’t reading it: a missing tag, a different tag ID or a different stream.
  • Only your subdomain shows as a referral. Same fault, different cause: the cookie domain, covered under F-205 .

Found the split? The rest of this note is for whoever manages your tags. If nobody does, tracing the hop and fixing it is my work as a GA4 consultant.

What you seeWhere it breaksFirst check
No _gl on arrivallink never decorateddomain list, GTM linker
_gl, then goneredirectDevTools, Preserve log
_gl, new _gadestination tagsame G- ID, same stream
Split on a form or button onlynot a link clickform decoration, JS navigation
Subdomain as referralcookie domaincookie_domain, F-205
Two domains, one visit · what each test result points to · worked example, illustrative, not a client account
  • The domain isn’t in the list. Check Configure your domains for every domain in the journey, including the one the visitor lands on after the hop. A typo, or an old domain the visitor no longer reaches, fails quietly: nothing errors, the link just goes out bare.
  • A GTM linker setting overrides the list. Google’s developer guide says a linker setting on the Google tag, in gtag code or in the tag’s settings in Tag Manager, overrides the domains configured in GA4 Admin. A linker field left from an older setup, listing one domain, wins over the Admin list. Remove it, or add every domain to it.
  • The hop isn’t a link click. Google says the linker depends on user-initiated clicks and doesn’t cover navigation triggered by JavaScript. A button that sets window.location, or a script that builds the URL after the click, sends the visitor across with nothing attached.
  • A script stops the click. Google names scripts that call Event.stopPropagation() as able to stop the linker. Check custom menus, sliders and widgets that intercept clicks.
  • The hop is a form. Google’s help says the linker carries IDs through a link or a form. If you or GTM set a manual linker config, forms are decorated only when decorate_forms is true. With the Admin list alone, still test the form hop on its own: a form that submits by script, or posts through a redirect, can lose _gl.

Where the hop can’t be made a plain link, Google’s fallback is manual: read client_id and session_id with gtag’s get command on the source, append them to the destination URL, and pass them as client_id and session_id in the config command there. That is developer work, and it needs testing on every route.

Why does _gl disappear?

Google warns that if the destination redirects, or drops query parameters it doesn’t recognise, _gl can be removed. Check booking engines, regional redirects (.com to .co.uk), trailing-slash rules and login walls.

To see it, open DevTools, Network, tick Preserve log so entries survive each redirect, and click across. Read each request in the chain. The one where _gl stops appearing is the redirect to fix: it has to pass the query string on. The same fix keeps UTM tags and the Google Ads click ID alive. If those are being stripped too, that loss is F-204 .

The two-minute expiry matters here too. A link with _gl baked into a page, an email or a cached redirect arrives stale. The tag must add it at the click.

The destination isn’t reading _gl

When _gl arrives and the _ga cookie still changes:

  • No tag on the landing page. The tag must load on the page the visitor lands on, not only on later steps.
  • A different tag ID or stream. Google says every domain must use the same G- tag ID from the same web data stream. A second property on the booking engine, or a separate stream for it, starts its own visitor.
  • A third-party platform with its own GA setup. Many booking and checkout platforms load GA4 through their own settings field. Check which ID it loads, and whether it loads on the first page after the hop. If the engine sits inside an iframe on your page rather than on a page the visitor goes to, there is no link or form for the linker to decorate: see booking widgets and iframe forms.

How do I fix GA4 cross-domain tracking?

Run the setup steps above first: domain list, one tag and stream, no stray GTM linker. Then fix what the hop test showed.

  1. Make the hop a link. Where it is a JavaScript redirect, change it to a real link, or use the manual method above. Test any form hop on its own.
  2. Keep the query string through every redirect on the destination side.
  3. Put the tag on the landing page after the hop, with the same G- ID.
  4. Add your own domains to the unwanted-referrals list as a backstop, under Configure tag settings, Show all, List unwanted referrals. It stops the referral row. It doesn’t join the sessions: only the linker does that.
  5. Publish and date it. Sessions recorded before the fix stay split.

How do I know it’s fixed?

  • Walk the journey with Tag Assistant connected to both domains (add the second if it doesn’t follow the click) and GA4 Admin, Data display, DebugView open: one session_start from landing to conversion.
  • The destination URL carries _gl, and _ga reads the same on both domains.
  • Over the first week or so after the fix, your own domain no longer appears in Session source / medium, and conversions sit under the channels that drove them.
  • The destination page loads correctly with _gl in the URL, and a download started from that page still works (Google’s verification steps).

Common questions

How do I set up cross-domain tracking in GA4?

In GA4 Admin, open Data streams, your web stream, Configure tag settings, Configure your domains. Add every domain in the journey, from Recommendations or with Add condition, and save. Every page on every domain needs the same G- tag ID from that stream. Then click across and check the destination URL carries _gl. You need the Editor role or above in Google Analytics.

Why is GA4 cross-domain tracking not working?

The second domain isn’t receiving the visitor’s ID. Click across and look at the destination URL. No _gl means the link was never decorated: the domain is missing from Configure your domains, the hop is a JavaScript redirect or form rather than a link, or a GTM linker setting overrides the list. _gl present on the click but gone on the final page means a redirect stripped it.

How do I know if cross-domain measurement is working?

Click a link from one domain to the other and check that the destination URL contains _gl. Then compare the _ga cookie in DevTools on both domains: the numbers after GA1.x. should be the same. In DebugView the whole walk should show one session_start.

Does cross-domain tracking need setting up in GTM as well as in GA4?

Usually not, as long as GTM loads the Google tag with the same G- ID. One exception: Google says a linker setting on the Google tag, in gtag code or in the tag’s settings in GTM, overrides the domains in GA4 Admin, so if someone set one, every domain must be in it too.

Do I need cross-domain measurement for subdomains?

Google recommends listing them. Because Google tags write the _ga cookie on the highest-level domain by default, www and shop usually share it even without the list. They split when the cookie domain is hard-coded to one hostname, filed as F-205 .

Why does _gl appear and then disappear?

A redirect on the destination side dropped it. Google warns that a destination that redirects, or rejects unknown query parameters, can remove _gl. Trace the hop in DevTools with Preserve log on and fix the redirect so it keeps the query string.

Will fixing cross-domain repair past data?

No. Sessions already recorded stay split, still credited to your first domain as a referral. Note the date of the fix so month-on-month comparisons read correctly.

Sources

Read on 19 November 2026:

  • Google Analytics Help, Set up cross-domain measurement (Editor access or above; the Admin path to Configure your domains; Recommendations and Add condition; conditions combine with OR, up to 100; the same G- tag ID from the same web data stream on every domain; _gl carries the IDs through a link or a form; verify by checking _gl on the destination URL and that downloads still work; the linker depends on user-initiated clicks, not JavaScript navigation; Event.stopPropagation() can stop it; redirects or rejected query parameters can remove _gl; manual setup with get and config; subdomains on different cookie domains can create self-referrals)
  • Google for Developers, Measure activity across multiple domains (linker parameters expire after two minutes and are added at the click; hostname “contains” matching; decorate_forms defaults to false; linker set in Tag Manager’s Google tag settings overrides the domains in GA4 Admin)
  • Google Analytics Help, Configure your Google tag settings (Configure your domains enables cross-domain measurement and sets which links don’t trigger outbound click events; detected domains appear under Recommendations; changes can affect other Google tags on the page)
  • Google Analytics Help, Identify unwanted referrals (referrers on the same domain or its subdomains are ignored by default; matching referrals get ignore_referrer=true; up to 50 per stream)
  • Google for Developers, Customise cookies (automatic cookie domain writes on the highest-level domain; cookie_domain)
  • Google for Developers, Consent mode overview (while analytics_storage is denied, Analytics tags don’t read or write first-party analytics cookies)

← back to the reading room