Why is the same GA4 tag loading twice?
The same GA4 ID usually loads twice because it was installed in two places: for example in Google Tag Manager and in the theme, or through an app and a plugin. That does not always mean every event is counted twice, so check the network requests before you remove anything.
Symptom
A tag checker, an agency or a browser extension tells you the same GA4 measurement ID appears twice on your store. Sometimes there is a visible effect too: page views per session jump on a particular date, or engagement rate looks oddly high or low. Often there is no visible effect at all, which is why the problem can sit unnoticed for months.
Possible causes
- Cause A: GTM plus a direct install. A GA4 tag inside GTM, and the same ID also hard-coded in the theme as a
gtag.jssnippet. - Cause B: an app or plugin plus a manual install. On Shopify, the Google and YouTube app, another analytics app, a custom pixel and a theme snippet can each send to GA4. On WooCommerce, Site Kit, an analytics plugin and a GTM plugin can each add their own tag.
- Cause C: GTM itself loads twice. The same container is in the theme and is also injected by an app.
- Cause D: one install, two page views. GA4 sends a
page_viewautomatically when its config loads. If GTM also has a separate event tag that sendspage_view, each page is counted twice even though the ID is only installed once.
How to check
- List every source. Search the theme code for
G-,gtag(andGTM-. On Shopify, check Settings, Customer events for custom and app pixels, and the installed apps list. On WooCommerce, list the plugins that mention Google, Analytics or Tag Manager. - Count the requests. Open a private window, DevTools, Network tab, filter on
collect, and load one product page. Count requests with yourtidanden=page_view. One is expected. Two for the same ID on one page load is event duplication, not just duplicate code. - Use GTM Preview and Tag Assistant. Tag Assistant shows each Google tag it finds and the events sent. GTM Preview shows which of your GTM tags fired on each event. A GA4 hit that appears in Tag Assistant but not in GTM Preview comes from outside GTM.
- Check DebugView. With debug mode on, two
page_viewevents with the same timestamp on one navigation confirm the effect in GA4 itself. - Find the date. In GA4, plot views per session by day. A step change that lines up with an app install, a theme publish or a GTM version is strong supporting evidence.
Illustrative result from step 2, with an invented ID:
1 /g/collect?v=2&tid=G-AB12CD34EF&en=page_view (from gtag.js in theme)
2 /g/collect?v=2&tid=G-AB12CD34EF&en=page_view (from GTM container)
What the result means
- Two loaders, one request per page view: duplicate code, but the events may not be doubled. Tidy it up, because a later change can turn it into real duplication.
- Two requests per page view: real duplication. Page views, sessions-based ratios and any event fired by both installs are inflated.
- Purchases: check them separately. Duplicate tag installation doesn't automatically mean duplicate purchase events: each install may only send some events. See why purchase events are counted twice.
False positive to watch for. A theme can mention a GA4 ID in a settings variable or a dataLayer push without actually loading it. A text search finds the ID, but nothing is sent. Only count an install when there is a loader or a config call, and confirm with the network requests. Our own public check works this way, and we removed false positives of exactly this kind while building it.
Our public research. On 14 November 2026 we checked public pages of 975 Shopify stores. 92 loaded the same GA4 ID twice. These are screening observations: a public-page check can't confirm whether purchase tracking works, or whether purchases are double counted.
How to fix it
- Decide on one source of truth for GA4: GTM, a platform app, or a custom pixel. Write that decision down.
- Before removing anything, list the events each source sends. The copy you plan to remove may be the only one sending purchases.
- Remove or pause the other installs. In GTM, pause rather than delete at first, so you can roll back.
- If you have a separate
page_viewevent tag in GTM, either remove it or turn off the automatic page view in the Google tag settings. Not both. - Repeat the network count on a home page, a product page and the checkout path, then watch views per session for a week.
What not to do
- Don't remove the theme snippet blindly on Shopify. It may be the only thing running on some templates, and checkout pages behave differently from the theme.
- Don't "fix" the numbers by filtering events in reports. Fix the source.
- Don't assume a second ID is a duplicate. It may be a separate property someone relies on: see multiple GA4 IDs.
When to request help
If you can't tell which install sends which event, or purchases are involved, a GA4 and GTM audit maps every source, event and destination and recommends what to keep.
Related guides:
- Why are purchase events counted twice?
- Multiple GA4 IDs on one store: what does it mean?
- Shopify GTM is in the theme. Is checkout covered?
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.
Sources and updated date
- Google Tag Manager Help: Google Tag Manager vs. gtag.js
- Google Tag Manager Help: Preview and debug containers
- Google Analytics Help: Enhanced measurement events
- Google Analytics Help: Monitor events in DebugView
- Shopify Developer docs: About web pixels
Last checked against official documentation: 18 November 2026.