GTM Duplicate Events: Finding the Tag That Fires Twice

GA4 and GTM · 4 min read · by Anna Viggeborn

Duplicate events in a tag manager are almost always a trigger design problem, not a platform bug. The same user action matches more than one condition.

Patterns that cause duplicates

The same tag has two triggers, for example page view and a custom data layer event.
The data layer pushes the event on load and again after hydration on a single page app.
The tag is also hardcoded in the site, so it runs alongside the container.
Two containers are installed, often one legacy and one current.
A trigger uses a loose regex that matches more URLs than intended.
No trigger group or once per page limit on an event that can repeat.

How to find it

1. GTM Preview, complete the action once

2. Look at the event stream on the left

3. Count how many times your tag appears as fired

4. Open each occurrence and read which trigger caused it

5. Remove or narrow the redundant trigger

What it means for decisions

Duplicates inflate conversion counts everywhere downstream, in GA4, in ad platforms and in the dashboards leadership reads. Fix the trigger before you rebuild the report.

Not sure whether you have a performance problem or a signal problem?

Your performance may be fine. Your signals aren't.

Run a free Milestic Signal Audit

Continue the diagnostic path

Purchase event firing twice

Conversions look great, revenue does not match. Usually a duplicate source.

GA4 purchase event not firing

Orders exist, GA4 shows nothing. Where the ecommerce event breaks.

GA4 revenue not matching Shopify

Some difference is normal. Learn which size of gap is a real problem.