Cross Domain Tracking in GA4: Complete Setup Guide

Cross domain tracking in GA4 is what stops a real customer from looking like two different people in your reports. Without it, someone browsing your main site, then clicking through to checkout.yoursite-payments.com, gets counted as a brand-new visitor the moment the domain changes, and the campaign that actually brought them disappears entirely.

GA4 uses first-party cookies by default, which only work on the single domain that set them. Cross domain tracking passes an identifier between domains through a URL parameter, so the second domain can pick up exactly where the first one left off.

The setup itself is simpler than it used to be in Universal Analytics. Getting it fully correct, especially across cookie consent, redirects, and third-party checkout tools, is where most implementations quietly break.

01Cross Domain Tracking Explained

Google's own documentation defines it plainly: cross-domain measurement allows activity to be accurately attributed to a single user as they move across domains. Without it, a single visitor to different root domains gets assigned new cookies and new IDs on each one.

Refact's guide adds the mechanism behind it: GA4 passes tracking details through a URL parameter called _gl. When someone clicks from Domain A to Domain B, that parameter carries the identifiers needed so the second domain continues the same session instead of starting fresh.

02When You Actually Need Cross Domain Tracking

Analytics-Tips' guide offers the clearest decision rule available: one brand, one strategy, one sales funnel means one GA4 property with properly configured cross-domain tracking. Different businesses or independent teams should stay as two separate properties without it.

Zeo's guide adds a detail worth confirming first: GA4 handles subdomains automatically. You don't need cross domain tracking for something like blog.yoursite.com to shop.yoursite.com, only for genuinely separate root domains.

03Before You Start: What You Need

Devrix's March 2026 guide lists the requirements clearly: all domains must send data to the same GA4 Measurement ID, you need Editor-level admin access across every domain involved, and a clear understanding of your current URL parameters so the _gl tag doesn't conflict with existing query strings.

Analytics Mania's setup guide adds one important limitation: this native solution works when users navigate between domains by clicking a link. It won't work for form submissions or server-side redirects without additional custom handling.

04Step-by-Step Setup in GA4

Markana Media's May 2026 guide walks through the exact path: go to Admin, select your web data stream, scroll to Configure Tag Settings, then click Configure Your Domains under Cross-Domain Measurement. Add every domain in the user journey, without the protocol and without trailing slashes.

The same guide flags a detail people miss constantly: GA4 won't automatically assume www and non-www versions are the same domain. If your journey includes www.yoursite.com, yoursite.com, and checkout.yoursite.com, list each variation separately.

05Verifying the _gl Parameter

KRM Digital's guide gives the simplest confirmation method: click a link from your first domain to your second, then check the destination URL. A parameter starting with ?_gl= or &_gl= followed by a character string means it's working.

ACCS-Net's guide adds an important, easy-to-miss detail: the timestamp inside _gl invalidates after roughly two minutes. That's by design, so users can't bookmark a decorated URL and accidentally impersonate another visitor's client ID later.

06GTM Linker Configuration Example

For teams managing this through Google Tag Manager instead of the native GA4 admin panel, here's the linker parameter structure.

// In your Google tag configuration in GTM
// Configuration Parameter: linker
// Value:

{
  "domains": ["example.com", "checkout-example.com"],
  "url_position": "fragment"
}

// Note: setting the linker parameter this way overrides
// any domains configured in the GA4 Admin interface.
// Choose one method, not both, to avoid conflicts.

07Common Reasons It Breaks

Markana Media's guide, referenced above, describes a real client case: a "URL beautification" script stripped all query parameters from links, silently removing the _gl parameter and breaking funnel tracking for two months before anyone noticed.

ACCS-Net's guide, referenced above, flags mixed protocols as another common failure point. Browsers strip query parameters on HTTPS-to-HTTP downgrades, so any link in the chain going from secure to non-secure will drop the _gl parameter mid-flow. Forcing HTTPS everywhere in the journey avoids this entirely.

08Setup Checklist

Confirm each of these before considering the setup complete.

09Is Your Setup Actually Working?

Answer a few quick questions to check your current implementation.

10Common Questions