FICILCOM Inc. LogoFICILCOM Inc.
  • Company
  • Company Overview
  • Mission · Vision · Values
  • Guidelines
  • Services
  • NeX-Ray
  • Xtrategy
  • Trial Job Change
  • Tsurugi
  • Recruit
  • Culture
  • Benefits
  • Process
  • FAQ
  • Open Positions
Contact
  1. Home
  2. Blog
  3. Web Analytics
  4. GA4 Cross-Domain Measurement: Setup, Validation, and Referral Rules

GA4 Cross-Domain Measurement: Setup, Validation, and Referral Rules

GA4のクロスドメイン設定手順|複数サイトを横断計測する方法

Published: 07/09/2026

Last Updated: 10/12/2026

Category: Web Analytics

Authors: Shusaku Yosa

Ready to put this into practice?

Start NeX-Ray for free→

1-minute signup, free, cancel anytime

GA4 cross-domain measurement helps connect a journey that moves between measured domains, such as a website and an application form. Registering domains is only part of the work. Validate the shared web stream, identifier handoff, redirects, and consent conditions. Treat unwanted-referral handling as a separate decision, and test the complete journey before describing it as connected.

Decide whether a journey needs cross-domain measurement

Consider cross-domain measurement when you need to connect activity across different root domains. A link to another website does not automatically make it necessary. First establish which journey matters and whether appropriate measurement tags can run on both sides.

Journey

First check

Purpose and limitation

Different measured root domains

Cross-domain measurement

Pass measurement identifiers; requires tag and transition validation

Subdomains of one root domain

Tags and cookie-domain settings

Confirm cookie-sharing conditions rather than assuming

Return from an untaggable payment service

Whether unwanted-referral handling is appropriate

Avoid treating the return as new acquisition; does not measure activity inside the service

An illustrative move from example.com to example.org differs from a move to shop.example.com. Follow the official prerequisites when deciding which case you have.

Check the Google tag, shared web stream, and permissions

Google’s documented setup requires the same G- measurement ID from the same web data stream on each measured domain. Matching property names is not enough. Whether the implementation uses direct tagging or GTM, inspect the actual Google tag and collection destination on production pages.

  1. Confirm the property, web stream, and permission to edit the setting.
  2. Check tag loading and the measurement ID on both domains.
  3. Look for duplicate installations and sends to a test stream.
  4. List the domains and transitions used by links, forms, authentication, payment, and redirects.

An Admin setting can complete the configuration only when the necessary tagging and navigation behavior already exist. It does not make a third-party service measurable when you cannot install the required tag there.

Configure matching domain conditions

From Admin, open the relevant web data stream and the Google-tag settings, then Configure your domains. Add domain conditions, review the match type, and save conditions covering the intended domains. Exact presentation can vary by permissions and configuration.

Broad matching rules need review for unintended matches. List the real www and non-www hosts and any application-specific hostname. Do not describe both directions as tested because somebody edited the setting from one site’s administration workflow. Confirm that the shared stream settings reach the tags actually running on both sides, then test A to B and B to A.

Understand linker IDs versus the User-ID feature

A qualifying link can add the _gl linker parameter to its destination URL. It passes cookie-based measurement information; it is not the dedicated User-ID feature that uses an account identifier. The User-ID requirements are separate.

Seeing _gl is useful intermediate evidence. It does not by itself prove that the destination accepts the information, sends to the same stream, or satisfies consent and browser conditions. Session timeout and identification boundaries still matter. Avoid promising that every transition will always remain one user and one session; validate the actual circumstances instead.

Know when unwanted referrals are a separate task

Unwanted referrals changes how a referrer is treated for acquisition. It does not connect measurement identifiers and cannot replace cross-domain setup. Google describes automatic self-referral detection for properly configured cross-domain transitions with the linker parameter. Adding every measured domain again to the unwanted-referral list is not a universal required step.

A payment-service return may be a valid reason to review unwanted-referral handling. A genuine external publisher that introduced a visitor is different. Before hiding a referral, decide whether the underlying issue is acquisition treatment, tag coverage, or identifier continuity. Otherwise a tidier report can conceal the original implementation problem.

Validate links, forms, payment, and authentication paths

Use a test matrix for the real environment. Preparing it does not mean the journey has passed. Record the device, time, consent state, start and destination pages, and evidence for each case.

Case

Inspect

Evidence

A to B and B to A

Shared G-ID, destination _gl, successful display

URLs and collection destinations in both directions

Form submission

Actual destination and linker handling

Submitted journey and received events

Redirected transition

Query handling at each step

Redirect chain and final landing URL

Authentication or payment return

Consent, identity, success condition, duplicates

Events around the return and independently verified success

Use DebugView for event order and parameters, supplemented by browser cookies or collection-request evidence where appropriate. Do not assume its standard interface always exposes a client ID for comparison. Identifier continuity and a correctly measured registration are separate acceptance criteria.

Troubleshoot redirects, JavaScript, and subdomains

Consider an illustrative A to B/checkout to B/login to B/checkout journey. The first B URL may contain _gl while a login redirect drops information needed by the destination. Inspecting only the final page misses the step that changed the URL. Follow each redirect and its query handling in the browser’s network evidence.

Test JavaScript-driven navigation, forms, and embedded iframes as implemented; do not assume that every mechanism is automatically covered. Avoid “fixes” that strip legitimate UTMs or click IDs along with linker information. For subdomains, review cookie-domain coverage and matching tags. Sharing a root domain is a reason to check those settings, not proof that all identification is correct.

Report by hostname and retain a change record

If both domains have /thanks, Page path alone combines them. Use Hostname or Page location with event_name and consistent consent conditions. Keep test traffic, reporting dates, and filters explicit when comparing the later data.

  1. Save existing measurement IDs, domain conditions, and unwanted-referral settings.
  2. Record each test’s owner, time, result, and untested paths.
  3. Inspect production sending and duplicates by hostname, then review processed reports.
  4. Retest affected journeys after authentication, payment, or site changes.

The purpose is to connect the intended measurement boundary. Event totals are not registration headcounts. If success conditions remain unverified, record the business outcome as unmeasured even when the domain transition itself works.

Related reading

  • GA4 Source / Medium Explained: Scope, Referrers, and Direct Traffic
  • GA4 Direct / None Traffic: Causes and a Practical Diagnostic Checklist
  • Exclude Internal Traffic in GA4: IP Rules, Testing, and Permanent Filters

Sources and specification date

Specifications checked against these primary sources on October 12, 2026. Navigation can differ by permissions and report collection.

  • Set up cross-domain measurement
  • Identify unwanted referrals
  • [GA4] Best practices for User-ID
  • Monitor events in DebugView
  • API dimensions and metrics

 

 

 

 

Table of Contents

  1. Decide whether a journey needs cross-domain measurement
  2. Check the Google tag, shared web stream, and permissions
  3. Configure matching domain conditions
  4. Understand linker IDs versus the User-ID feature
  5. Know when unwanted referrals are a separate task
  6. Validate links, forms, payment, and authentication paths
  7. Troubleshoot redirects, JavaScript, and subdomains
  8. Report by hostname and retain a change record
  9. Related reading
  10. Sources and specification date

 

Company

  • Company
  • Company overview
  • Mission · Vision · Values
  • Guidelines

Services

  • Services

Blog

  • Blog
  • Categories
  • Authors

Estimate

  • Estimate simulator

Careers

  • Careers
  • Culture & Work Style
  • Benefits & Systems
  • Hiring Process
  • FAQ
  • Open Positions

Policies

  • Privacy Policy
  • Anti-Social Policy
  • Information Security Policy

Contact

  • Contact

Social

  • X
  • LinkedIn
  • Facebook
  • Pinterest
© 2026 Ficilcom Inc.

Related Articles

GA4の「探索」の使い方|レポート作成と見方の基本を解説
Web Analytics09/01/2026

GA4 Explorations: Build and Interpret Free-Form, Funnel and Path Analyses

Build GA4 free-form, funnel and path explorations with clear questions, segment scopes and denominators. Check retention...

Shusaku YosaRead more
GA4の権限設定とは?許可レベルの違いと安全な転送・付与手順
Web Analytics08/21/2026

GA4 Permissions: Roles, Sharing and Access Troubleshooting

Compare GA4 roles, add or remove users, understand inherited access, and troubleshoot permission issues when sharing a p...

Shusaku YosaRead more
Googleアナリティクスレポートの見方|主要指標とチェックすべき項目
Web Analytics08/19/2026

How to Read GA4 Reports: Acquisition, Pages and Key Events

Read GA4 acquisition, landing-page, page and key-event reports with the right dimensions and denominators. Separate miss...

Shusaku YosaRead more