Cross-Domain Tracking in GA4: Setup, Validation, and Common Failures

How cross-domain tracking works in GA4

Google documents that cross-domain measurement passes Analytics identifiers between domains by adding a_glparameter when users navigate through a link or a form between configured domains. When the destination page uses the same web data stream and tag ID, Analytics can continue the same user and session instead of starting over. The configuration lives alongside the rest of yourGA4 property configuration checks, so audit it together with timezone, currency, and data stream settings.

That does not mean every multi-domain journey works automatically. Redirects, embedded flows, consent timing, and inconsistent tagging can still break continuity, which is why browser verification matters.

What cross-domain tracking does not require

Cross-domain measurement is configured at the web data stream level. Google's documentation says the tag on each included page must use the same tag ID from the same web data stream. If different domains are sending data to different properties or streams, standard cross-domain measurement will not stitch them into one journey.

You should also keep separate questions separate. Cross-domain measurement handles your own connected domains. Unwanted referrals from payment providers or unrelated third parties are a different configuration review handled through theGA4 referral exclusion list.

Setting up cross-domain tracking

The setup is done entirely in the GA4 Admin panel. Follow these steps in order:

How to validate cross-domain tracking is working

Check for the _gl parameter in urls

Navigate to the source domain and click a link or submit a form that should carry the user into the second domain. Verify that the destination URL contains a_gl=parameter during the handoff. If it does not appear, review the configured domains and the source-page tag behavior first.

Check the traffic acquisition report for self-referrals

In GA4, go to Reports and open the Traffic Acquisition report. Add Session source/medium as a dimension and filter for sessions where the source matches your own domain names. Any sessions showing your own domain as the referral source indicate that cross-domain tracking has failed for those users. The session broke at the domain boundary and GA4 recorded the transition as a new session arriving from your own domain. This pattern often shows up alongside otherGA4 conversion tracking setupissues that fragment the user journey.

Use DebugView to watch real-time sessions

Enable Debug Mode by adding?debug_mode=true to your source domain URL or by using the Google Analytics Debugger Chrome extension. Navigate to GA4 Admin and open DebugView. Perform a test journey from the source domain to the destination domain. You should see a single continuous stream of events for the same debug device. If a new session_start fires on the destination domain, the session has broken and cross-domain tracking is not working.

Common failures and how to fix them

• Domain not listed in GA4 settings: The most common cause. Double-check that every domain in the user journey is listed. Pay close attention to country-specific TLDs. If you list yourdomain.com but users also navigate to yourdomain.co.uk, you need both listed.
• Redirects stripping the _gl parameter: If a link on domain A redirects before reaching domain B (for example, a tracking redirect via a click shortener or a JavaScript redirect on the landing page), the _gl parameter is often stripped during the redirect chain. Use a browser extension like Redirect Path to check whether the parameter survives the full redirect chain.
• Typos in domain configuration: A single character error in the domain list causes complete tracking failure for that domain. Verify every entry carefully.
• Different tag IDs or web streams: If domain A and domain B are not tagged with the same tag ID from the same web data stream, standard cross-domain measurement will not treat them as one journey. Verify each container in yourGTM GA4 configurationuses the same Measurement ID.
• iFrame navigation: If users navigate between domains through an iframe rather than a direct link click, the _gl parameter is not automatically appended. You need to build a custom solution that reads the client ID from the parent page and injects it into the iframe URL as a parameter.
• Consent timing changing the handoff: If consent logic delays the relevant tag behavior on the source page, test whether the cross-domain handoff still happens as expected in pre-consent and post-consent states.