GA4 Cross-Domain Tracking Not Working: How to Find Session and Referral Problems
When GA4 cross-domain tracking is not working, a visitor who moves between your domains starts a new session or loses attribution. Cross-domain tracking is about maintaining session continuity and referral behavior across domains. The problem is usually in the cross-domain configuration, the linker or how the domains are connected.
Table of Contents
- 01.What cross-domain tracking maintains
- 02.What to check first
- 03.Same property and cross-domain configuration
- 04.Linker behavior where relevant
- 05.Session continuity and referral traffic
- 06.Payment or booking domains where relevant
- 07.Consent and testing
- 08.How to test it
What cross-domain tracking maintains
Cross-domain tracking keeps a single visitor session continuous as the visitor moves between domains. Without it, each domain starts a new session and the second domain may show as a referral from the first. The goal is to maintain the same client ID and the original campaign attribution across the domain boundary. When it fails, you see session breaks and self-referrals.
| Symptom | What it usually means | What to check |
|---|---|---|
| New session on second domain | Client ID not carried over | Linker configuration |
| First domain as referral | Referral not excluded | Unwanted referrals config |
| Lost campaign attribution | Original source not preserved | Linker and referral handling |
| Works on some links only | Not all links use the linker | Link decoration on all links |
| Payment domain breaks session | Third-party domain in flow | Domain configuration |
What to check first
- Confirm both domains use the same GA4 property and measurement ID.
- Confirm the cross-domain configuration includes all relevant domains.
- Check whether the linker decorates links between the domains.
- Check whether the second domain shows as a referral.
- Confirm the same client ID persists across the domain boundary.
Same property and cross-domain configuration
Cross-domain tracking requires both domains to use the same GA4 property. If each domain uses a different property, no cross-domain continuity is possible. Confirm the measurement ID is the same on both domains. Then confirm the cross-domain configuration in GA4 includes all the domains in the flow. A domain missing from the configuration will not be linked.
Linker behavior where relevant
The linker passes the client ID and campaign information across the domain boundary by decorating links with a linker parameter. If the linker is not configured, or if the links between domains are not decorated, the second domain starts fresh. Confirm the linker is set up and that the links users actually click between domains are decorated. Not every multi-domain setup requires the same configuration, so confirm what applies to your domains.
Session continuity and referral traffic
When the linker works, the session continues on the second domain with the same client ID and the original attribution. When it fails, the second domain may show the first domain as a referral, which is a self-referral. GA4 has configuration to handle unwanted referrals, but you should understand the role of the referral in the journey before excluding it. This is covered in the guide on GA4 showing unwanted referrals.
Payment or booking domains where relevant
Many sites send visitors to a third-party payment or booking domain during a flow. If that domain is not part of your cross-domain configuration, the session can break when the visitor returns. Confirm whether the payment or booking domain needs to be included, and whether you control it. Domains you do not control may not support the linker, which limits what cross-domain tracking can do.
Consent and testing
Consent can affect cross-domain tracking because the linker parameter depends on storage that may require consent. If consent is not given, the linker may not work, and the session breaks at the domain boundary. Test the full flow across domains with consent accepted and confirm the client ID persists. Attribution problems across domains connect to the broader source and medium issues covered in the guide on GA4 source and medium being wrong.
How to test it
- 1.Start on the first domain and note the client ID in the cookie.
- 2.Click a link to the second domain and check the client ID persists.
- 3.Confirm the second domain does not start a new session.
- 4.Check that the first domain is not shown as a referral.
- 5.Confirm the original campaign attribution is preserved.
Frequently Asked Questions
Does every multi-domain setup need cross-domain tracking?
Not necessarily. It depends on whether visitors move between the domains in a single journey and whether you want to maintain session continuity. Confirm what applies to your domains before configuring it.
Why does my second domain show the first domain as a referral?
The linker is not carrying the session across the boundary, so the second domain starts a new session and counts the first domain as the referrer. Check the cross-domain configuration and that links are decorated.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
GA4 Showing Unwanted Referrals: How to Diagnose Referral Attribution Problems
Do not exclude a referral until you understand its role in the customer journey. Exclude only the ones that distort attribution, like payment processors in your own flow.
GA4 Source and Medium Are Wrong: How to Diagnose Attribution Problems
Wrong source and medium usually come from missing UTMs, redirects stripping parameters or self-referrals. Find where the wrong value originates before changing attribution settings.
GA4 Sessions Dropped After a Tracking Change: What to Check
Separate actual traffic decline from measurement decline before you fix anything. A real decline is a marketing problem. A measurement decline is a tracking problem. Check other data sources to tell them apart.