Definition
Cross-domain tracking, which Google Analytics calls cross-domain measurement, is the configuration that lets an analytics tool treat a visit spanning two or more domains owned by the same business as one continuous SessionA group of one user's interactions with a site or app in one visit, ended by inactivity.. It is needed whenever a journey crosses a domain boundary the business controls: a brochure site with a shop on a hosted platform, a site that hands bookings to a separate booking domain, or a group of brand sites sharing one checkout. Subdomains of one domain are a lighter case: they belong in one data stream, and need checking after launch rather than a separate setup. Third-party payment pages the visitor merely passes through are a different problem again, handled by listing them as unwanted referrals.
Google's help documentation for GA4 is the reference for the exact settings, which sit in the web data stream's tag configuration.
How the identifier is carried across
Analytics keeps a client identifier in a first-party cookie on the domain where the visit began. Cookies belong to their domain, so the next domain cannot read it. With cross-domain configured, the analytics tag decorates links and form submissions that point to the other listed domains, adding a short-lived linker parameter that holds the identifier. The tag on the receiving domain reads that parameter, adopts the identifier, and continues the same visit with its original source intact.
Two things follow. Every domain in the journey must run the same analytics tag configuration, or there is nothing on the other side to read the parameter. And anything that drops query parameters in transit, such as a redirect, a link built by script after the page loads, or a form that posts without them, breaks the hand-over even when the domain list is correct.
In practice
The GA4 setup walkthrough handles cross-domain in one step: list every owned domain the journey passes through, then list the payment and identity providers as unwanted referrals, then test by clicking from the main site to the other domain and watching the linker parameter appear in the address. The Google Analytics hub places the setting among the stream configuration that has to be right before any report is trusted. For shops, the GA4 e-commerce tracking guide makes cross-domain a precondition where checkout runs on another domain, because otherwise the purchase funnel restarts at the hand-over.
Site architecture decides whether the question arises at all. Content kept in subfolders of one domain never crosses a boundary, which is one of the analytics points in the comparison of subfolders and subdomains.
Symptoms of a missing setup
- Self-referrals. The business's own domain appears as a referral source, often credited with a large share of conversions.
- Payment providers as sources. Sessions that return from a payment page are attributed to the provider.
- Doubled sessions and users. One journey is counted twice, once per domain.
- Conversions without campaigns. Paid and email traffic look weak because the purchase session lost the UTMURL tags identifying traffic source. values or click identifier that arrived on the first domain.
The marketing data quality guide lists self-referrals and split sessions among the routine checks, and the analytics implementation audit scorecard scores whether sessions survive moves to checkout, booking and payment domains.
A ski school's bookings credited to itself
Rimeloft Ski School runs its website on one domain and takes payment on a booking platform's domain. In January, GA4 credits 312 of 420 lesson bookings to a referral from the school's own website, and only 41 to the paid social campaigns that spent £3,800 that month. The booking domain has the same GA4 tag, but neither domain is listed for cross-domain measurement. The analyst adds both domains to the stream's list and the card processor to unwanted referrals, then confirms the linker parameter appears on the booking links. In February, self-referrals fall to 9 of 395 bookings, and paid social is credited with 118, a figure that finally resembles the booking codes customers quote on the phone.
Related terms
A SessionA group of one user's interactions with a site or app in one visit, ended by inactivity. is the unit cross-domain tracking protects from being split. GA4Google's event-based analytics platform. is where the setting lives for most sites, as a list of domains in the web data stream. AttributionAssigning conversion credit to touchpoints. of any kind depends on the original source surviving the hand-over, and UTMURL tags identifying traffic source. values on the first landing are exactly what a broken setup loses.
Common confusions
- Same tag is not same session. Installing one property on both domains is necessary but not enough; the domains must also be listed.
- Unwanted referrals are not cross-domain. Excluding a domain as a referral stops it taking credit; it does not carry the identifier across.
- Subdomains are not separate sites. Subdomains of one domain belong in one stream; separate streams split users.
- The linker parameter is not a tracking leak. It is a short-lived value meant to be read once by the receiving tag.
- Fixing it now does not repair history. Earlier reports keep their self-referrals.
