Why GA4 Counts Two Page Views Per Visit

ملخص

Pixel shares a study of 792 sites that found 123 (15.5%) had multiple sources capable of sending a GA4 page_view for one visit. A live check found 7 of 15 flagged sites actually sent duplicate or triple events, highlighting why teams should audit Google tags, GTM, and integrations.

DEV Community

GA4 counts two page views per visit? Causes in 792 sites

Short answer: GA4 records two page_view events for one visit when two things send one for one measurement ID, usually a tool integration (HubSpot, WordPress Site Kit) plus GTM. On 5 Nov 2026, 123 of 792 sites that load GA4 (15.5%) had such a setup, and 7 of 15 we loaded live sent the page view twice. Check in DevTools: filter on collect? and count the en=page_view hits for one load. How many sites send page_view twice? On 5 Nov 2026 we refetched the 981 GA4 sites in our 1,727-site study (robots.txt checked, 971 answered) and read their GTM containers. 792 showed a GA4 ID on the homepage. For each ID we counted the places that send a page_view. Setup that can send page_view twice for one ID Sites (of 792) Same ID in page code and a GTM Google tag 59 (7.4%) Same ID in two GTM Google tags (55 in one container) 58 (7.3%) A GA4 event tag named page_view on top of a Google tag 12 (1.5%) Any of the three 123 (15.5%, 95% CI 13.2 to 18.2) By segment: 15.9% of 618 B2B SaaS sites, 14.4% of 132 agencies, 14.3% of 42 ecommerce sites. Not counted (they depend on settings we can't see): two triggers on one Google tag (53 sites, 6.7%) and a History Change trigger (38 sites, 4.8%). Two different IDs (138 sites, 17.4%) is another case. 100 of the 123 doubles load only one ID. Live check, same day, 25 flagged homepages in headless Chromium, no banner click: 10 sent no GA4 hit. Of the other 15, 7 sent page_view two or three times per load and 8 once (control: 4 of 5 unflagged sites sent one, 1 none). So 15.5% means "has two sources"; about half double-count. Why does GA4 record two page_view events? The Google tag "sends a pageview by default" (Google). Each cause below adds a second sender. A tool adds GA4, and GTM adds it again. Of the 59 sites with the ID in both places (58 answered a re-read), the page copy came from HubSpot on 13, a WordPress plugin on 9 (Site Kit on 7), a CDN tag on 9, and a gtag snippet or unknown on 27. A second sender in the same container: two Google tags with one ID (often an old "GA4 Configuration" tag and its migrated copy), a GA4 event tag named page_view, or one Google tag on two triggers set to "Once per event". Single page apps. Enhanced Measurement sends a page_view on history changes, "even if you set" send_page_view: false (Google). A History Change trigger on top counts each route twice. How do I check for duplicate page views in 2 minutes? Private window, DevTools, Network tab, Preserve log on, filter collect?. Accept the banner, reload. Count requests to google-analytics.com/g/collect (or your first-party collector) with en=page_view (batched: see Payload). Two with the same tid= for one load is a double. Find the second source: search the page source for gtag('config' and gtag/js?id=G-. In GTM, filter Tags on "Google tag" and "GA4 Event". DebugView and Tag Assistant show the same. What does a double page_view break? Views double; sessions and users don't. "Viewed 3 pages" audiences fire early. Key events built on page_view (a thank-you page rule) and Google Ads conversions imported from them: counted twice, so Smart Bidding sees more than happened (duplicates in GTM). Primary or secondary can't be seen from outside: check Goals in Google Ads. How do I stop GA4 sending page_view twice? Pick one install. Keep GA4 in GTM; turn off HubSpot's integration, Site Kit, the CDN tag and hand-written gtag. One Google tag per ID: pause the extra, test, delete. Two triggers on it: firing option "Once per page". Own page_view? Set send_page_view to false. If your tag handles route changes, turn off "Page changes based on browser history events". Then recount with the DevTools check. What can't we see from outside? Enhanced Measurement settings live in the property, so history changes are a risk, not a count. A banner hides a double from a no-click load (10 of our 25). We read the homepage only. Updated 7 Nov 2026: shorter, same data. First version 5 Nov 2026. Data: a static read of 971 homepages and their GTM contain...
Why GA4 Counts Two Page Views Per Visit
Powered by Readybot.io

الأحدث من Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …

Why a Java HPA Got Stuck at 20 Kubernetes Pods

Pixel shares how a Spring Boot pricing service autoscaled to 20 Kubernetes pods and stayed there because the JVM retained committed heap memory after traffic …