Quick answer

Use cross-domain measurement when related domains are part of one customer journey and should be measured as a connected experience. Configure the linked domains in the appropriate Google Analytics settings, then test the transition and confirm the intended session and attribution behaviour.

Do not add domains simply because they share a brand. Separate businesses, unrelated properties and privacy boundaries need deliberate treatment; the setup should reflect the actual measurement purpose.

What I would check first

Map every domain and subdomain used from acquisition through conversion. Identify where the user leaves the main site, whether redirects or embedded forms are involved and which tags are active on each destination.

Inspect campaign parameters, referrer behaviour and the destination URL after the handoff. Test whether the linker parameter is preserved and accepted, and whether the journey creates an unexpected new session or referral source.

Decision framework

Use cross-domain configuration when two or more related sites need to be measured as one journey. If a third-party platform does not support the required setup, document the limitation and use an alternative reconciliation method rather than pretending the data is complete.

Google's tag guidance describes cross-domain measurement as sharing first-party measurement information between configured domains. It recommends configuring GA4 cross-domain settings through the Analytics interface for most use cases.

Implementation steps

List the exact domains, configure the measurement settings, verify that the same measurement property and relevant tags are present, then test from the first landing page to the final confirmation. Repeat after redirects, consent changes and provider updates.

Document the expected referrer and session behaviour and keep evidence from the test. Check both the browser journey and the reports after processing; a tag preview alone does not prove that the final reporting is correct.

Common mistakes

Do not add every external domain to the configuration, assume a cross-domain parameter will survive every redirect or use referral exclusions as a substitute for correct linking.

Avoid testing only the destination page. The problem often occurs at the transition between domains, so the complete sequence is essential.

Measurement and business implications

Track the proportion of journeys that preserve the intended source, unexpected self-referrals, duplicate sessions and the reconciliation between online actions and CRM outcomes.

Use the CRM reconciliation, consent-mode QA and UTM governance articles to keep the full measurement path coherent.