Cross-domain measurement in Google Analytics 4 lets you measure the user journey across different domains as part of the same session, instead of treating each domain as a separate origin and generating self-referrals.
This is useful in many different situations. For example, a business may have a corporate website on one domain and an ecommerce site on another, while both are part of the same user journey.
Contents
What is cross-domain measurement?
Cross-domain measurement is a configuration that allows Google Analytics to recognize the same user when they move between different domains that belong to the same business journey.
Without this setup, a visit from one domain to another may be treated as a new session, and the second domain may appear as a referral source. With cross-domain measurement in place, GA4 can preserve the session and attribution more accurately across those domains.
Why cross-domain measurement matters
If users navigate between domains during the conversion journey, measuring each domain separately can distort the data.
One of the most common problems is self-referrals. For example, if a user moves from the main site to a checkout domain, GA4 may attribute that second step to a referral from your own domain instead of preserving the original acquisition source.
This can affect session counts, traffic acquisition reporting, and conversion attribution. Cross-domain measurement helps avoid those issues by passing the necessary identifiers from one domain to the other so the journey remains unified.
How cross-domain measurement works in GA4
GA4 uses first-party cookies to identify users on a domain. When a user moves from one domain to another, cross-domain measurement appends linker information to the destination URL so the identifier can be transferred and the user can continue to be recognized correctly on the new domain.
In practical terms, this means the links between the configured domains need to allow that information to pass correctly. If the setup is correct, GA4 can continue the same session across domains instead of starting a new one.
How to configure cross-domain measurement in Google Analytics 4
In GA4, cross-domain measurement is configured from the web data stream settings.
From there, you can define the domains that should be treated as part of the same journey. Google also notes that traffic between configured domains should not be treated as outbound clicks, which is another sign that those domains are being handled as part of the same setup.
If the implementation is done through the Google Tag, the same logic applies: the domains need to be configured so linker parameters can be added and read properly across them.
Things to keep in mind when setting it up
One important point is that this setup is meant for different domains, not for subdomains of the same main domain.
Subdomain measurement is usually handled automatically in GA4 as long as the same tag is installed correctly, because the cookie can already be shared at domain level. Cross-domain measurement is needed when the journey spans truly separate domains.
It is also important to make sure that all the domains involved belong to the same business journey and use the same GA4 property and web data stream. Otherwise, the data will not be unified correctly.
How to check whether it is working correctly
The easiest way to validate the setup is to navigate between the configured domains and review the journey in GA4 DebugView or in the browser.
A correct implementation should preserve the session when the user moves between domains. In practice, this usually means checking that the destination URL receives the linker parameter (_gl) during navigation and confirming that the second domain does not appear as a self-referral in acquisition reports later on.
Another way to check that everything is correct is to use the DebugView in GA4. To do this, you will have to follow the steps in the previous paragraph and check that in the generated page_view events, the page_location parameter contains domains 1 and 2 when applicable, and the ga_session_id parameter is always the same.
Finally, you can also open your browser console and, within the cookies section under Application, verify that the value of the _ga cookie is the same in both domains.
In short, cross-domain measurement in Google Analytics 4 is essential when users move between different domains during the same journey.
Without it, GA4 can break sessions, generate self-referrals, and distort attribution. When it is configured correctly, the data becomes much cleaner and the user journey can be analyzed as a single flow across all the relevant domains.
