Cross-Domain Tracking Architecture is Tidal Health Group's configuration standard for healthcare organizations operating across multiple web properties, subdomains, or co-branded portals that share patient traffic. It defines how GA4 cross-domain measurement is configured, how advertising click parameters are passed between domains, and how session continuity is maintained without capturing protected health information.

GA4 cross-domain measurement configuration and advertising click parameter management for healthcare organizations operating across multiple web properties, with PHI exclusion compliance.
For a podiatry group that operated its main website on one domain, its patient portal on a subdomain, and a telehealth intake form on a co-branded partner domain, Tidal Health Group configured cross-domain tracking that maintained session continuity across all three properties while excluding patient-identifying event parameters from the GA4 data stream. Marketing attribution reports became accurate for the first time because session breaks from portal transitions were eliminated.
Healthcare organizations operating across multiple digital properties without cross-domain tracking lose session continuity every time a patient moves between domains. This produces inflated session counts, broken attribution chains, and reporting that overstates direct traffic and understates the contribution of the channels that drove the original visit.
Healthcare marketing analytics teams and IT managers at organizations operating across multiple web properties, subdomains, or partner portals who are experiencing attribution breaks and session continuity problems in their GA4 data.
Default GA4 configuration treats each domain transition as a new session, breaking attribution chains and inflating session counts for healthcare organizations with multi-domain architectures. Without explicit cross-domain configuration, marketing attribution data is systematically incorrect.