Paid Ads

Cross-domain Tracking

Cross-domain tracking connects user sessions across multiple domains (for example marketing site -> checkout) to preserve attribution and funnels.

Updated 2026-01-24

Definition

Cross-domain tracking connects user sessions across multiple domains (for example marketing site -> checkout) to preserve attribution and funnels.

Example

Users move from marketing.site.com to checkout.site.com without losing the original source.

How to use it

  • Ensure linker parameters pass across redirects and payment providers.
  • Test end-to-end after changes to checkout, routing, or domains.
  • Align cookie domain settings so sessions do not reset across subdomains.

Common mistakes

  • Breaking attribution by stripping query parameters on redirects.
  • Letting self-referrals inflate new sessions and distort ROAS in analytics.
  • Changing domains without updating linker configuration.

Why this matters

This term matters because it affects how you interpret performance and make budget decisions. If you use inconsistent definitions or windows, ROAS/CPA can look "better" while profit gets worse.

Practical checklist

  • Write a 1-line definition for "Cross-domain Tracking" that your team will use consistently.
  • Keep the time window consistent (weekly/monthly/quarterly) when comparing trends.
  • Segment results (channel/plan/cohort) before drawing big conclusions from blended averages.
  • Sanity-check with a related calculator from the same category on MetricKit.
  • Read the related guide (e.g., UTM + GA4 attribution: practical tracking for paid ads (without lying to yourself)) for context and common pitfalls.

Where to use this on MetricKit

Calculators

Guides