Cross-Domain Tracking
AnalyticsAlso: Cross-Domain Measurement · Cross-Site Tracking
Quick definition
Cross-domain tracking is the configuration that tells your analytics platform to treat a visitor as the same person when they move between two separate domains, for example from your main site to a hosted checkout or booking tool. Without it, the handoff looks like a new session from a referral source, and your attribution and conversion data breaks.
How it varies across Australia
Across Australian businesses we review, cross-domain tracking is one of the most commonly misconfigured analytics settings. Businesses using third-party checkout platforms, booking engines or hosted forms are most exposed. The symptom is referral traffic from your own checkout domain sitting in the top five acquisition sources.
See data and tracking scores across Australian industries →What it actually means
A session ID lives in a cookie tied to a single domain. When a visitor clicks from yourbusiness.com to checkout.yourbusiness.com or to an entirely separate domain like yourstore.myshopify.com, the cookie does not transfer automatically. Google Analytics 4 (GA4) sees the arrival on the new domain as a fresh session, credits the original domain as a referral, and loses the thread of what channel the visitor actually came from.
Cross-domain tracking solves this by passing the session identifier as a URL parameter when the visitor crosses domains. GA4 reads that parameter on landing, recognises the existing session, and continues it rather than starting a new one. The visitor stays as one user, one session, one acquisition source.
Without it, attribution breaks in specific and predictable ways. Your own checkout or booking tool appears as a referral source. Paid search or paid social campaigns lose credit for conversions that complete on the second domain. Conversion rate looks lower than it is because the completing session has no channel attached.
The fix requires two things: configuring the domains list in GA4's data stream settings, and making sure the links between domains include the session parameter. For most businesses using Google Tag Manager (GTM), the second part is handled automatically once the domains are listed.
If your checkout domain appears as a top referral source, your attribution is lying to you.
How it shows up
The clearest diagnostic is opening the Traffic Acquisition report in GA4 and looking for your own domain or checkout subdomain in the referral source list. If it is there, sessions are being broken at the domain handoff.
A second signal is a conversion rate that looks implausibly low on paid channels despite good click-through rates. The conversions are completing, but the session that completes them has lost its source attribution and is being counted as direct or referral.
For businesses using GA4 with GTM, the configuration lives under Admin, then Data Streams, then the relevant web stream, then Configure Tag Settings, then List Unwanted Referrals and Configure Domains. Both domains need to be listed.
The Australian context
Australian businesses are more exposed to this issue than they often realise because the local market has a high concentration of businesses using third-party hosted infrastructure: Shopify checkouts, Ezidebit payment pages, HubSpot landing pages, Simplybook or Calendly booking tools, and external quote or application portals.
Each of those is a potential domain break. The Privacy Act and Australian Privacy Principles also add a layer of complexity, because the session parameter passed in the URL technically contains a user identifier. Consent frameworks need to account for this. Businesses that implement cross-domain tracking without reviewing their consent configuration may be passing identifiers before consent is established.
Where people get this wrong
Related terms
Common questions
Do I need cross-domain tracking if I use a Shopify checkout?
Yes, if your main site is on a different domain from your Shopify store. When a visitor moves from yourbrand.com to yourstore.myshopify.com, GA4 treats that as a referral unless cross-domain tracking is configured. Your paid channel attribution for completed purchases will be wrong without it.
How do I know if cross-domain tracking is broken?
Open Traffic Acquisition in GA4. If your own domain or a checkout domain appears as a referral source, sessions are being broken at the handoff. A secondary check is comparing your paid channel click data against attributed conversions. An unexplained gap often traces back to this.
Does cross-domain tracking work with consent mode?
Yes, but the order matters. The linker parameter should only fire after consent is granted for analytics cookies. If you use a consent management platform, verify the GA4 tag and the linker fire in the correct sequence. Passing a user identifier before consent is a compliance risk under the Privacy Act.
Is cross-domain tracking the same as subdomain tracking?
No. Subdomains on the same root domain share cookies automatically in GA4 and do not need cross-domain configuration. Cross-domain tracking is specifically for separate registered domains. Confusing the two is common but the fix for each is different.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →