Analytics & Tracking

Cross-Domain & Funnel Tracking
See the Full Journey, Not Broken Fragments.

Cross-domain tracking with linker, multi-property funnel visibility, measurement ID configuration and consistent user journeys across domains and subdomains. We make sure a user who starts on your marketing site and finishes on your app or checkout domain is one continuous person in your data.

Get a Free Cross-Domain Audit arrow_forward
↑ 3.1×
Accurate Cross-Domain Users
85%+
Funnel Completion Visibility
↓ 50%
Broken User Paths Fixed
60+
Multi-Domain Setups

The Invisible Revenue That Lives Between Domains

What Usually Breaks

  • Users appear as new visitors when they move from marketing site to app or checkout
  • UTM and click ID context is lost on the second domain
  • Funnel reports show huge drop-offs that are actually just domain changes
  • Attribution gives credit to the last domain instead of the true source
  • Remarketing lists and audiences are fragmented

Our Fix

We make the entire journey one continuous user. Proper cross-domain linker configuration, consistent measurement IDs or subproperties, preserved UTM and gclid/fbclid, and funnel explorations that treat domain transitions as normal steps instead of drop-offs.

Cross-Domain & Multi-Property Technical Patterns

Linker & Measurement Config

  • Cross-Domain Linker: Correct _gl parameter or gtag linker config across all domains. We test with real clicks and referrers.
  • Measurement ID Strategy: Same web stream across domains when you want one user, or carefully managed separate streams with user-ID stitching when separation is required.
  • UTM & Click ID Persistence: We ensure gclid, fbclid, msclkid, and UTM values survive the handoff via first-party cookies or server-side enrichment.

Funnel & Pathing

  • Unified Funnel Explorations: We build explorations that follow users across domains as a single path instead of broken segments.
  • Subproperty vs Single Property: We choose based on team access needs, data residency, and reporting requirements.
  • Remarketing & Audiences: Lists that span the full journey so you can reach people who started on one domain and abandoned on another.

Our Cross-Domain & Funnel Tracking Process

01

Domain & Flow Mapping

Document every domain, subdomain, app, and checkout flow the user can touch. Identify where user identity and click context are currently lost.

02

Linker & Config Audit

Check current linker implementation, measurement IDs, cookie domains, and whether UTM/click IDs survive each transition.

03

Cross-Domain Implementation

Fix linker config, add allowLinker / linker domains, ensure first-party cookie scope is correct, and test with real user journeys.

04

Funnel & Path Reconstruction

Build or repair funnel explorations and pathing reports that treat domain changes as normal steps. Add custom dimensions for current domain and previous domain when useful.

05

Validation & Attribution Fix

Run controlled tests across domains. Verify user count, session stitching, and attribution credit are correct in GA4 and ad platforms.

06

Ongoing Monitoring

Set up alerts for sudden drops in cross-domain completion and document the exact expected path for each major user journey.

Frequently Asked Questions About Cross-Domain & Funnel Tracking

Technical questions about stitching users and funnels across multiple domains.

When do we need cross-domain tracking vs separate properties? expand_more
Use cross-domain (same property or carefully linked) when the user journey is continuous and you want one user record. Use separate properties when the brands, data access, or legal requirements demand complete separation. We help you choose and implement either correctly.
How does the Google linker actually work? expand_more
It appends a _gl parameter (or uses cookies) that contains the client ID and timestamp. The receiving domain reads it and reuses the same client ID instead of creating a new one. We test with real clicks, referrers, and incognito to make sure it survives.
What about subdomains? Do they need linker too? expand_more
Subdomains on the same root domain can share cookies with the right cookie_domain setting. We still often add linker as a belt-and-suspenders approach and for cases where the cookie scope is not perfectly aligned.
How do we keep UTM and gclid when the user crosses domains? expand_more
We persist them in first-party cookies or pass them explicitly in the linker flow or server-side. We also make sure the landing page on the second domain reads and re-applies them if the platform requires it.
Can we have one GA4 property for marketing and another for the app but still see the full funnel? expand_more
You can use GA4 subproperties, BigQuery to join, or user-ID stitching. Each has trade-offs in access control and modeling. We pick the approach that fits your team structure and data needs.
What breaks most often in cross-domain setups? expand_more
Missing linker domains in the config, wrong cookie scope, redirect chains that strip parameters, and single-page app routers that do not preserve the _gl parameter. We audit and fix all of them.
How do you handle cross-domain remarketing audiences? expand_more
We build audiences in the property that sees the full journey, or we use Google Ads / Meta audiences fed from the unified events. Fragmented lists are one of the biggest hidden costs of broken cross-domain tracking.
Does cross-domain affect session counting and bounce rate? expand_more
Yes - in a good way. Properly implemented cross-domain usually reduces artificial session inflation and makes bounce rate and session duration more accurate because users are not counted as new on every domain change.
How do you test cross-domain tracking reliably? expand_more
We use a combination of GTM preview on both domains, real clicks from different referrers, incognito windows, and we look at the client ID and session ID in GA4 debugView and BigQuery to confirm continuity.
What about consent and cross-domain cookies? expand_more
Consent must be obtained (or inherited) on each domain if they are treated as separate sites. We implement Consent Mode on all domains and document the consent handoff if you have a single banner solution.
Can we track users from a marketing site to a third-party checkout? expand_more
Partially. If the third party supports passing click IDs and you can get post-purchase data back (via webhook or thank-you pixel), we can stitch the beginning and end. Full client-side continuity is usually not possible.
How do you handle international sites with different TLDs? expand_more
Same principles. We treat .com, .co.uk, .de etc. as cross-domain when the user journey spans them, and we configure linker + consistent measurement accordingly while respecting regional consent rules.
Do we need to change anything in our ad platforms for cross-domain? expand_more
Usually the auto-tagging and click ID passing still works. We make sure the final conversion domain can read and forward the gclid/fbclid so the platforms receive the conversion with the original click context.
How do you document the expected paths for the team? expand_more
We create a journey map showing every domain transition, which parameters must survive, and what the expected GA4 user and session behavior should be. This becomes part of the runbook.
How long does a solid cross-domain fix usually take? expand_more
Simple two-domain marketing + checkout: 1-2 weeks. Multiple brands, subdomains, apps, and international with consent complexity: 3-5 weeks.

Tired of seeing half your funnel disappear at the domain boundary?

Get a free cross-domain audit. We will map and fix the full continuous user journey across all your sites.

Get My Free Cross-Domain Audit arrow_forward