GA4 Duplicate Page View Fires Twice on an SPA Route Change
This sample scan shows that GA4 page view event fires twice during an SPA route change. Multiple events are firing for a single page load, which can inflate metrics.
Use the scanner landing page to run the same validation on your own site.
Run this scan on your siteAnalytics Tracking Validation Scan
1 of 7 checks found problems
- Target URL
- https://boombetcasino.com
- Audited on
- 2026-04-15T19:41:38.053286
- 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.
Duplicate page_view
Duplicate page_view requests were found on 6 page(s) across 6 navigation(s).
Two GA4 page_view events fired during a single page navigation. This commonly happens when GA4 is installed multiple times (for example via gtag.js and Google Tag Manager) or when SPA navigation triggers duplicate page_view events.
Duplicate page_view tracking can inflate traffic and route-level engagement metrics.
- • Page views seem too high
- • Traffic metrics look inflated
- • Reports do not match expectations
- • DebugView shows repeated page_view events
- • GA4 installed via gtag.js and GTM
- • SPA navigation triggers duplicate page_view
- • Multiple GTM containers
- • Automatic page_view enabled + manual page_view
-
1Check whether GA4 is implemented through both gtag.js and GTM.
-
2Confirm only one config path is sending page_view on each navigation.
-
3If this is an SPA, verify page_view only fires once per route change.
-
4Disable automatic page_view if you intentionally send page_view manually.
Missing page_view
No missing page_view behavior was found in the pages and navigations scanned.
Extra page_view on short-lived pages
No extra page_view events were found on pages with short dwell time.
Failed analytics requests
No failed analytics requests were detected.
Analytics JavaScript errors
No analytics-related JavaScript errors were detected.
Analytics ID consistency
No inconsistent analytics IDs detected across pages.
This sample demonstrates a complete analytics tracking validation scan including duplicate events, missing events, failed requests, JavaScript errors, and configuration consistency checks.
Yes. Sample scan pages render real scan findings and evidence, with a light public wrapper for context and navigation.
The technical layer makes the findings defensible and useful to implementers, not just readable to marketers or PMs.
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.