What is the step-by-step procedure for configuring GA4 and GTM cross-domain conversion tracking across subdomains and third-party checkout flows?
Short answer
Configuring GA4 and GTM cross-domain tracking requires installing the same measurement ID across all properties and adding external checkout domains to GA4 domain configuration settings. This setup allows the platform to pass tracking parameters automatically across domains. Properly linking these domains prevents broken customer journeys, which otherwise falsely attribute 40% to 70% of checkout conversion revenue to direct traffic or self-referrals.
Configuring cross-domain tracking across Google Tag Manager and Google Analytics 4 requires deploying identical measurement IDs across all properties, configuring target domains in data stream settings, and validating linker parameter appending to preserve multi-touch attribution.
Broken cross-domain journeys split user paths into disconnected sessions, falsely attributing 40% to 70% of checkout conversion revenue to direct traffic or self-referrals. For growth-stage brands scaling paid media acquisition, this data gap distorts return on ad spend calculations and misallocates campaign budgets.
If you only do one thing: Add all primary and third-party checkout root domains to the Google Analytics 4 "Configure Your Domains" list so the platform automatically appends the `_gl` tracking parameter across domain boundaries.
- Unify container measurement IDs: Install the same Google Analytics 4 (GA4) Measurement ID across both the primary website and the third-party checkout flow within Google Tag Manager (GTM) to ensure both environments write to the same reporting container.
- Preserve default subdomain handling: Subdomains sharing the same apex domain (such as `store.brand.com` and `brand.com`) track across journeys automatically through first-party cookies; do not enter subdomains into cross-domain configuration rules.
- Configure domain linker rules in GA4: Open GA4 Admin, select Data Streams, click your web stream, open Configure Tag Settings, select Configure Your Domains, and enter every external checkout domain using the "Contains" or "Exactly matches" rule.
- Add unwanted referral exclusions: In Tag Settings under List Unwanted Referrals, add your root domain and the third-party payment gateway domain so returning buyers completing transactions do not overwrite initial acquisition source data.
- Deploy unified ecommerce triggers in GTM: Build data layer triggers for `begin_checkout` and `purchase` events that read standardized transaction parameters (revenue, currency, transaction ID) consistently across both domains.
- Validate parameter transmission in DebugView: Open GTM Preview mode, click a link leading to the external checkout, and confirm that the destination Uniform Resource Locator (URL) includes the `_gl=` client identifier string.
- Watch out for: Destination URL redirect stripping, where third-party platforms execute a 301 or 302 redirect on page load that purges the `_gl` linker parameter before GA4 scripts initialize.
- Watch out for: Iframe checkout barriers, which block standard link decoration and require explicit `postMessage` JavaScript listeners between the host site and the embedded checkout frame.
- Watch out for: Redundant subdomain linker rules, which add unnecessary query strings to internal links and occasionally interfere with default browser cookie inheritance.
Test an end-to-end sandbox transaction in GTM Preview mode to confirm that the final conversion event preserves the original acquisition campaign rather than registering as a direct or referral session.