AS
Analytics Scanner
Runtime analytics validation
 Explore Scanners

GA4 IDs Differ Across Pages

What this sample shows

This sample scan shows inconsistent GA4 measurement IDs across pages, which can split analytics data and make reporting less reliable.

Next step

Use the scanner landing page to run the same validation on your own site.

Run this scan on your site
Scan Report

Analytics Tracking Validation Scan

1 of 7 checks found problems

Issues detected
Pages scanned
10
Navigations scanned
10
Checks run
7
Checks with findings
1
Scan details
Target URL
https://uniqlo.com
Audited on
2026-04-15T19:41:28.993500
Scope
Currently validates GA4, Google Tag Manager, and Google Ads only.
Published
Public sample

Crawl conditions

No crawl conditions detected that would affect result accuracy.

Not detected

Duplicate page_view

No duplicate page_view behavior was found in the pages and navigations scanned.

Not detected

Missing page_view

No missing page_view behavior was found in the pages and navigations scanned.

Not detected

Extra page_view on short-lived pages

No extra page_view events were found on pages with short dwell time.

Not detected

Failed analytics requests

No failed analytics requests were detected.

Not detected

Analytics JavaScript errors

No analytics-related JavaScript errors were detected.

Not detected

GA4 GA4 ID consistency

Inconsistent GA4 IDs detected across pages. Different navigations are using different GA4 ID configurations.

Issue detected Low severity
Pages checked
10
ID configurations
3
Why this matters

Inconsistent GA4 IDs across pages can fragment your analytics data and make it harder to get a complete picture of user behavior. This may indicate partial GA4/GTM implementations or testing environments mixed with production.

How to fix
  1. 1
    Audit all pages to ensure consistent GA4 measurement IDs.
  2. 2
    Remove test/staging GA4 IDs from production pages.
  3. 3
    Ensure GTM containers are consistent across all pages.
  4. 4
    Consider using a single configuration method (either gtag.js OR GTM, not both).
Evidence
Configuration
Navigation count
G-CYY3WCHVDC, G-T7HS3TVJBM
9
G-T7HS3TVJBM
1
G-841KDX3M5F
1
FAQ
What does this sample scan test?

This sample demonstrates a complete analytics tracking validation scan including duplicate events, missing events, failed requests, JavaScript errors, and configuration consistency checks.

Does this report use real scan data?

Yes. Sample scan pages render real scan findings and evidence, with a light public wrapper for context and navigation.

Why show technical evidence on a public page?

The technical layer makes the findings defensible and useful to implementers, not just readable to marketers or PMs.

Can I run the same scan on my site?

Yes. The public sample is a published example of the same scan structure used for live user reports. Use the scanner landing page to run the same validation on your own site.

Run this scan on your site

See what issues exist on your own site. Get the same detailed report with actionable findings.

Start Your Scan