Cross-domain tracking lets analytics tools such as GA4 recognize that a visitor moving from one of your domains to another is the same person in the same session. Without it, the move looks like a new visit, often attributed as a referral from your own site, and the original traffic source is lost.
Typical eCommerce cases include a main website and a separate store domain, a separate checkout or booking domain, or brand sites that share a cart. In GA4, cross-domain measurement is configured in the web data stream settings by listing the domains that should be treated as one.
Why it matters for eCommerce
When journeys break across domains, purchases are credited to your own domain or to direct traffic instead of the campaign that drove them. That makes paid and email channels look weaker than they are and distorts budget decisions.
How it works in practice
- List every domain the customer journey crosses.
- Configure the domains in GA4’s cross-domain settings.
- Add your own domains and payment providers to the unwanted referrals list where needed.
- Test a full journey and confirm the session and source stay the same.
Common mistakes
- Forgetting subdomains or a third-party checkout domain.
- Treating payment gateway referrals as a cross-domain problem, when they need the unwanted referrals list instead.
- Not re-testing after a checkout or domain change.