When a user moves between two different domains, GA4 can treat the second domain as a new user or session. GA4 cross-domain tracking helps preserve the user's journey across multiple domains by transferring client and session information between them.
What is GA4 cross-domain tracking?
GA4 cross-domain tracking connects user journeys across separate registrable domains. It uses the _gl linker parameter to transfer identifying information from the source domain to the destination domain.
For example:
marketing-site.com → shop.example-store.com
Without proper configuration, the second domain can create a new user journey and cause attribution problems.
Do subdomains need cross-domain tracking?
Usually, no.
If both websites use the same root domain, such as:
www.example.com → shop.example.com
GA4 can use the same root-domain cookie, so additional cross-domain configuration is generally unnecessary.
Cross-domain tracking becomes important when the registrable domains are different.
How do you configure it?
In GA4:
- Open Admin.
- Go to Data Streams.
- Select your web stream.
- Open Configure tag settings.
- Select Configure your domains.
- Add the domains involved in the user journey.
- Make sure the same GA4 measurement ID is deployed on both domains.
Using precise domain-matching rules is important to avoid accidentally decorating links to unrelated websites.
What problems can cross-domain tracking solve?
Correct configuration can help prevent:
- Broken user sessions
- Self-referrals
- Incorrect traffic attribution
- Duplicate users
- Split conversion journeys
For example, a customer who moves from a marketing website to a separate shopping domain should ideally remain part of the same journey rather than appearing as a referral from the company's own website.
When can automatic tracking fail?
GA4 can automatically decorate standard links and form submissions, but certain navigation methods may require additional implementation.
These include:
- JavaScript redirects
window.open()- Server-side redirects
- Iframes
- Custom navigation logic
These cases may require manually passing the necessary information between domains.
How should you validate the setup?
After implementation, verify that:
- The
_glparameter appears when moving between domains. - The client ID remains consistent.
- A new session is not unnecessarily created.
- Your own domains no longer appear as referral sources.
- GA4 DebugView shows the expected journey.
What about payment gateways?
If a third-party payment provider hosts the checkout and you cannot install your GA4 tag there, standard cross-domain measurement cannot preserve the session through that domain.
Instead, configure the payment provider under Unwanted Referrals so the payment gateway does not receive inappropriate referral attribution when the user returns to your website.
Final takeaway
GA4 cross-domain tracking is essential when a customer journey moves between different registrable domains. Proper configuration helps preserve user and session continuity, reduce self-referrals, and maintain more accurate attribution.
Read the complete guide:
https://www.brillmark.com/ga4-cross-domain-tracking-how-to-keep-one-user-journey-across-two-domains/
Top comments (0)