Why multiple GA4 configuration tags break your data
Last updated 17 September 2026 · 3 min read
If your Google Tag Manager container has more than one GA4 configuration tag — the "Google tag" — pointing at the same Measurement ID, every hit is sent twice, inflating users, sessions, and conversions across all your reports. A healthy container has exactly one. Here's how to confirm it and fix it.
This is one of the most common findings in a GTM audit, and one of the most damaging, because it corrupts your numbers silently — nothing throws an error, the data just doubles.
What this finding means
The GA4 configuration tag (now called the Google tag) initialises GA4 and sends the base configuration, including a page_view by default. Two of them means two of everything: two page views per load, two sessions, doubled conversions. It usually creeps in one of three ways — a gtag snippet hardcoded on the site and a configuration tag in GTM, two configuration tags created in different workspaces or folders, or a tag duplicated during a migration and never cleaned up.
How to tell if it's affecting you
The tell-tale signs are user and session counts noticeably higher than your server logs or another analytics source, page views running at roughly double what you'd expect, and conversions that look too good. You can confirm it directly in GTM Preview (two Google tags fire on the same page) or in GA4's DebugView and Realtime (two page_view events per load).
How to fix it
1. Find every GA4 configuration tag
In GTM, filter your tags by type and list every Google tag / GA4 configuration tag, noting the Measurement ID each one targets.
2. Keep one, remove the rest
Choose a single source of truth — usually one Google tag in GTM — and delete or pause the duplicates. If gtag is also hardcoded on the site, remove it from either the site or GTM, never both.
3. Preserve any unique settings first
Before deleting a duplicate, move any settings only it carries — fields to set, user properties, custom configuration — onto the tag you're keeping.
4. Re-test in Preview and DebugView
Reload a page and confirm exactly one page_view fires, from one configuration tag.
Key takeaways
- Keep exactly one GA4 configuration tag per Measurement ID.
- Duplicates double users, sessions, page views, and conversions.
- The usual cause is a hardcoded
gtagplus a GTM tag, or a leftover from a migration. - Confirm with GTM Preview and GA4 DebugView, then keep one and remove the rest.