Skip to the content
searchboar.

Search results and measurement

Cross-domain measurement: meaning, examples and practical use

Cross-domain measurement connects an analytics journey that spans separate domains. It can help preserve user and session continuity between a main website and a separate checkout when technical and consent conditions are satisfied.

Also known as: Domainek közötti mérés

At a glance

  • The purpose is to connect visits belonging to one journey.
  • Redirects and parameter handling can break the connection.
  • Test actual transitions and recorded events rather than configuration alone.
On this page
A continuous visitor path crossing browser windows on two different domains.
Conceptual illustration: a continuous visitor path crossing browser windows on two different domains.

When is it needed?

Content may live on one domain while booking or checkout uses another. The GA4 documentation describes passing identifiers under an appropriate configuration to connect the journey. Both destinations need to participate in the intended measurement setup.

GA4 can attach a linker parameter such as _gl during the transition. A redirect that removes it can break continuity. Seeing the parameter is a useful check but does not by itself verify the entire recorded event sequence.

Example: a separate booking website

Imagine a hotel guide on the main domain linking to booking on another domain. A test follows the actual link and checks whether continuity survives. A checkout incorrectly recorded as a new session can distort interpretation of traffic acquisition.

What does not solve it alone?

Excluding your own domain as a referral does not necessarily connect the identifiers. Measurement must also respect consent choices. Review consent handling, tags and redirects together rather than treating configuration boxes as proof. Confirm both that the customer flow works and that the resulting measurement represents it appropriately.

Sources

  1. Google Analytics: Set up cross-domain measurement