Google Tag Manager tag firing twice? Find the cause
Short answer: When Tag Manager tags fire twice, there are usually two copies of something: two tags doing the same job, two triggers on one tag, a tag in Tag Manager plus the same tracking hard-coded in the site or added by a plugin, or two containers on the page. Open Tag Manager's preview mode, load the page and repeat the action, then look in Tag Assistant at which tags fired on which events. The duplicate shows up as the same tag, or the same destination, firing on two events. Remove the extra copy rather than adding workarounds.
Signs you're double-counting
- Page views per session roughly double overnight, or bounce and engagement figures look suspiciously perfect.
- The same click or form event appears twice with near-identical timestamps.
- An ad platform reports more conversions than you have orders or enquiries.
- Your analytics debug view shows two
page_viewevents every time a page loads.
Note the date the numbers changed. It's usually right after a site update, a new plugin, a theme switch or a Tag Manager publish.
Step 1: watch it happen in preview mode
Google's Tag Manager help describes preview and debug mode: your site is connected to Tag Assistant so you can inspect which tags fired and in which order, using the draft container before you publish.
- Open your container in Tag Manager and click Preview.
- Enter your site's address; it opens with Tag Assistant attached.
- Load a page, click the button or submit the form that's double-counting.
- In Tag Assistant, go through the events on the left. For each, check the "Tags Fired" list.
You're looking for the same tag firing on two events, or two different tags sending the same thing to the same place.
Step 2: check the common causes
Tracking added twice
The most common cause by far: the Google tag or another tracking snippet is in Tag Manager and also hard-coded in the theme, added by a website builder's built-in integration, or inserted by an SEO or analytics plugin. Tag Assistant may show hits from tags that aren't in your container at all. View the page source and search for your measurement ID or pixel ID; it should appear only where you expect.
Two Tag Manager containers
Old containers from a previous agency or a migration sometimes stay on the page. Search the source for container IDs. Both containers may send the same events.
Several page view triggers
Tag Manager's page view triggers come in types that fire at different moments: Consent Initialization, Initialization, Page View, DOM Ready and Window Loaded, in that order of precedence. A tag attached to both "Page View" and "Window Loaded", or to two different "All Pages" triggers, fires twice on every load. Each tag usually needs exactly one page-level trigger.
Single-page apps and history changes
On sites built as single-page apps, a history-change trigger is often added so virtual page views are tracked as people navigate. If the analytics tag or your site's code already sends page views on navigation, adding the trigger doubles them. Pick one mechanism.
Click and form triggers that match twice
A click trigger set to "All Elements" with a broad condition can match both a button and the link inside it. A form submission trigger plus a click trigger on the submit button counts the same action twice. Narrow the conditions, or use one trigger per action.
Enhanced measurement overlap
Analytics properties can collect some events automatically, such as scrolls, outbound clicks or form interactions. If you also send the same events from Tag Manager, you'll see doubles. Choose one source per event.
Step 3: fix it at the source
- Remove the hard-coded snippet or disable the plugin's tracking if Tag Manager should own it, or the other way around.
- Delete or pause the duplicate tag, rather than adding conditions to suppress it.
- Give each tag one clear trigger and rename tags and triggers so their purpose is obvious.
- Preview again to confirm each action produces one event, then publish with a version note describing the fix.
Tag firing options
Advanced tag settings let you limit a tag to once per page or once per event. They can be a reasonable safety net for tags that must never repeat, such as a conversion pixel on a thank-you page. Using them to hide a duplicate you haven't found means the cause is still there, and it may bite in a different way later.
Keep an inventory
A short list of every tracking tag on the site, where it's installed (Tag Manager, theme, plugin, platform integration) and who owns it prevents most repeats. Update it whenever an agency, plugin or developer adds tracking. When numbers jump, the list tells you where to look first.
Clean up the data
Fixes apply from the moment you publish. Add an annotation or note in your reporting tools with the date range affected, and avoid comparing doubled months with corrected ones without saying so. In ad platforms, check whether duplicate conversions influenced automated bidding during that period.
A worked example
An illustrative Gold Coast surf shop saw page views per session double after moving to a new theme. Preview mode showed the analytics tag firing once from Tag Manager, plus another set of page views from a measurement ID hard-coded by the new theme's settings. The shop disabled the theme's built-in analytics field, confirmed one page view per load in Tag Assistant, and noted the affected dates in its reports.
FAQ
Can I find duplicates without Tag Manager access?
Partly. Browser developer tools and analytics debug views show duplicate requests, but you need container access to see the cause inside Tag Manager.
Will deleting the duplicate tag lose data?
No. It stops future duplicates. Past data stays as it was.
Should I use "once per page" everywhere?
No. Use it where a tag must never repeat, and fix duplicates properly elsewhere.
Why did it start after a plugin update?
Plugins sometimes add or re-enable their own tracking on update. Check their settings after updates.
If your analytics or ad conversions look doubled, tell us which numbers changed and when and we'll help you trace the duplicate.