Direct answer: Cross-domain tracking preserves one analytics journey when a user moves between domains you control. Configure the same property/tag where appropriate, list the participating domains, verify linker behaviour and exclude only genuine self-referrals—without hiding real partner traffic.
Key takeaways
- Use cross-domain tracking only for domains in the same controlled journey.
- Confirm tag/property consistency before configuration.
- Test links, forms, redirects and consent on both domains.
- Referral exclusions are not a substitute for cross-domain setup.
Define the domain scope
List landing, booking, payment and application domains. Document ownership and whether they should represent one user journey.
Configure and verify
Follow current Google Analytics cross-domain guidance. Verify that linker parameters appear only where expected and that destination tags process them.
Test journey continuity
- Start on the source domain.
- Navigate through the real CTA.
- Complete the destination action.
- Inspect debug events and session source.
- Repeat for redirects and mobile.
Common errors
Typical problems include different properties, missing destination tags, redirects stripping parameters, forms not decorated, consent mismatch and overbroad referral exclusions.
Experience, sources and limitations
This guide reflects GrowthSparx's practical work across acquisition, analytics, CRM and conversion operations. Platform interfaces and requirements change, so verify official documentation before implementation. The framework does not promise perfect attribution; it makes evidence, controls and uncertainty visible.