Duplicate Google Analytics 4 tracking: how to find double counting
Two GA4 properties collecting from one page double count sessions and revenue. Learn how to spot duplicate analytics tags and keep one.
3 min read
Area
Tracking & tech health
Severity
Medium
Fix effort
Small
Stores failing
14%
Of 118 stores we scanned where this check applies, 14% fail it and 86% pass. See all benchmarks.
Duplicate GA4 tracking means more than one Google Analytics 4 property is collecting data from the same page. Sessions, orders and revenue can then be counted twice in one property, or split across two, and the numbers never match what the payment system shows.
Why it matters
A theme that adds GA4 and an app that adds it again is a common accident. The dashboards still look plausible, so the error can last for months. The damage shows up when someone compares analytics revenue with Shopify or WooCommerce revenue and finds a gap nobody can explain.
Decisions made on inflated numbers, like how much to spend on a channel, inherit the error.
What the audit looks at
The audit checks whether more than one Google Analytics 4 property is collecting from the same page.
What usually causes it
- A theme setting and an analytics app both adding the same property
- An old property left in the theme after switching to a new one
- A tag manager GA4 tag plus a hard-coded GA4 snippet
- A plugin that adds GA4 on top of the sales channel integration
How to fix it
Remove the second GA4 tag so sessions and revenue stop being counted twice. The effort is small, usually a setting or a paste and under 30 minutes.
- List every place the tag could be injected: the theme, a tag manager container, a plugin or app, and any header-script field.
- Keep exactly one. A tag manager container is usually the one to keep, because everything else can move into it later.
- Use the Google Tag Assistant extension to confirm only one tag fires after the change.
- Expect reported sessions to drop -- that is the double count going away, not traffic falling.
On Shopify
- Check three places: Settings > Customer events, the Google & YouTube channel, and a hardcoded gtag snippet in theme.liquid.
- Remove the hardcoded snippet first -- it is the one that outlives the app that added it.
- Confirm with Google Tag Assistant that a single tag now fires.
On WooCommerce
- Deactivate all but one of your analytics plugins -- installing a second one while the first is still active is the usual cause.
- Also check your theme options for a header-scripts field holding a pasted gtag snippet.
- Confirm with Google Tag Assistant that a single tag now fires.
How to check it yourself
- Open Chrome DevTools, go to Network, reload and filter by "collect". Look at the "tid" or "id" value in each request.
- Install Tag Assistant and read the list of tags found on the page.
- Search your theme code for "G-" followed by an ID to find hard-coded snippets.
Frequently asked questions
Is it wrong to send data to two properties on purpose?
Not always. Some agencies mirror data to a second property. If that is deliberate, document it. If nobody can say why there are two, one is probably left over.
Will removing one lose my history?
You keep the history in the property you leave in place. Choose the one with the longest, cleanest record and remove the other.
Related checks
Check your own store
See whether your store passes this check
Paste your store URL. The audit loads your pages in a real browser and shows the result for this check with the evidence behind it.