Fix GA4 counting every page view twice

1. 1Go to tagassistant.google.com, click Add domain, enter your website address and click Connect. This turns on debug mode for your browser.
2. 2In GA4, click Admin and, under Data display, click DebugView. Choose your browser in the Debug Device list if more than one shows.
3. 3Load one page of your site once, and watch the Seconds stream. One load should add one page_view; two together confirm the double count. Then click a link to another page of the site. That should add exactly one more page_view; two means the double count happens on page changes.
4. 4In Tag Assistant, read the list of Google tags found. The same G- ID listed twice, or found both in a GTM- container and as a separate tag, points at the second sender.

1. 1Open the website builder's or CMS's settings and look for a Google Analytics or Google tag field holding your G- ID. Google keeps a separate setup route for builders and CMSs, and a tag added there sits on top of anything in Tag Manager. Google says not to add more than one Google tag to each page.
2. 2Look in the site's code or theme header for a snippet that loads googletagmanager.com/gtag/js with your G- ID while Tag Manager also has a Google tag for the same ID. Google says to use either the Google tag snippet or Tag Manager, not both, since both can overcount.
3. 3If neither is there, the site may run its own copy of the Google tag code that sends page_view into the same data layer your Google tag uses. Nothing in Tag Manager shows it. The sign is Tag Assistant finding your G- ID only once while DebugView still shows two page_view events for one load.
4. 4On a site that changes pages without reloading, the site may send page_view itself on each change while GA4's enhanced measurement sends one too for the same browser history change.

1. 1If two installs send to the same ID, remove one. Keep the one in Tag Manager when you manage other tags there, and clear the G- ID from the builder's field or delete the extra snippet.
2. 2If a second install of the same ID cannot be removed, Google's tag settings offer Ignore duplicate instances of on-page configuration under Manage Google tag on the Google tag's Admin tab. It skips a repeated configuration of the same tag, not page_view events a builder sends separately.
3. 3If the builder sends page views itself and cannot be switched off, stop your Google tag's automatic page view instead. In Tag Manager, open the Google tag, add a configuration parameter named send_page_view with the value false, save, then Submit and Publish. On a hard-coded snippet, Google says the setting has to be on every page.
4. 4For pages that change without reloading, open Admin, Data streams and your web stream. Under Enhanced measurement, click to edit the individual options, open Page views, and in its advanced settings turn off Page changes based on browser history events. Google says send_page_view false does not stop these on its own.

Turn off only one sender. With send_page_view false and nothing else sending, pages stop being counted. Google's caution runs the other way: page views sent by the site without send_page_view false may be counted twice.