Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Cross-domain tracking for the same root domain

Cross-domain tracking for the same root domain

Cross-domain tracking is required when tracking visitors across domains that share the same root domain. For example, domainname.com and subdomain.domainname.com. This often applies to rental modules, scheduling modules, or personalization tools. They may run on a separate landing page or load in an iframe. When a visitor moves between domains or interacts with the iframe, marketing data must match on both pages.

Solution 1: Conversion Linker in GTM

Add a Conversion Linker tag to the GTM web container. Add both domain names to the tag. The Conversion Linker passes click data and session parameters correctly between domains. This ensures conversions are attributed to the correct source

Solution 2: Domain settings in GA4

In GA4, define which domains are treated as a single entity. Go to Admin, select Data streams, and choose the correct web stream. Open Configure tag settings, then select Configure your domains. Add all allowed domains, including the main domain and subdomain. GA4 then treats sessions across these domains as one continuous session

Check that the subdomain is also added to the Consent Management Platform (CMP). This is often overlooked. If the subdomain is missing, consent signals cannot be retrieved correctly. Visitors without consent may then be tracked. Tracking may also fail completely. Both outcomes affect data quality and privacy compliance.

Last updated

Was this helpful?