Cross-Domain Tracking

Cross-domain tracking lets GA4 count one person as a single visitor as they move between two or more domains you own. GA4 passes its client ID from one site to the next in the URL, so a journey that crosses domains stays stitched together as one session instead of being chopped into separate visits.

Why it matters

Plenty of small businesses run more than one domain without thinking of it that way: a marketing site on one domain and a booking, store, or payment page on another. If you haven't configured cross-domain tracking, GA4 treats the move between them as someone leaving and a brand-new visitor arriving — and the second domain shows up as a self-referral in your traffic sources.

A concrete example

Say your site lives on yourbrand.com but checkout happens on a hosted cart at shop.provider.com. Without cross-domain tracking, a customer who buys appears as two people: one who browsed and "left," and one who arrived at checkout from yourbrand.com. Your conversion looks broken because the visit and the purchase are attached to different sessions and different original sources.

The common misreading

The mistake is trusting source reports when cross-domain tracking is missing. Conversions get credited to your own domain instead of the channel that really sent the visitor, inflating referral traffic and producing a data discrepancy against your payment provider's records. Before you conclude a channel isn't converting, confirm the journey isn't being split across domains.