Guide 18 · Debugging · GA4 + Tag Manager
The same event arrives twice: find the second sender and remove it
Duplicate events come from two senders, not from one tag firing twice. Count the senders — a second tag, a second snippet, or a tag plus gtag — and remove one.
After the steps below, one action sends one event, the second sender is named and removed, and the count per action is back to one.
Download the check: the debugging check (JSON) (MD5 a2fbf734ebb387ad0d237f9c029cbbd1, 408 bytes). It lists the checkpoints from this guide and the worked check, with the figures recomputed. The file was built for this guide and validated structurally — it was not exported from a live container or a live property.
What you need
- Tag Assistant Preview, connected. The debug view shows how many times the tag fired for one event.
- The network tab, filtered for collect. One request per event is normal; two requests for one action is the duplicate, seen directly.
- A list of every way GA4 is installed. Tag Manager, a direct gtag snippet, a platform integration, a plugin — write them all down before you look.
- One repeatable action. Do it the same way each time, so the counts can be compared.
The trace
The worked check: the figures below were recomputed before publication, and the note under the table shows the working.
| Check | Figure |
|---|---|
| Actions done in the test | 10 |
| Events counted in GA4 | 20 |
| Events expected | 10 |
| Extra events | 10 |
| Events per action after the fix | 1 |
Ten actions were done and GA4 counted 20 events, so 20 minus 10 is 10 extra events — exactly one extra per action. After removing the second sender, 10 actions produced 10 events, so 10 divided by 10 is 1 event per action, the correct count.
- Count the events per action. Do the action 10 times and count the events in Realtime or DebugView. In the worked check, 10 actions produced 20 events. If the count is exactly double, there are two senders. If it is sometimes double and sometimes not, the second sender fires only sometimes — note which actions double.
- Count the collect requests for one action. In the network tab, filter for collect and do the action once. Two requests for one action means two senders both fired. One request means the tag fired once and the doubling happens elsewhere — in a second tag on another trigger, or in a second install.
- List every install of GA4 on the page. Open the page source and count: a Tag Manager container, a direct gtag snippet, a platform GA4 field, a plugin. The Google tag through Tag Manager plus a direct gtag snippet with the same Measurement ID is the classic pair — both send page_view, and both send every event.
- Check for the second page_view tag. In Tag Manager, list the tags. A Google tag sends page_view on its own, so a second GA4 Event tag named page_view on top of it records the same page view twice. The setup guide for this site calls this out as the most common install mistake.
- Remove one sender, then count again. Remove the duplicate — the direct snippet, the extra tag, or the plugin field — and repeat the 10-action count. The count should fall to 10 events for 10 actions. If it falls to 0, you removed the only working sender and kept the broken one; put it back and remove the other.
Dead ends
DEAD END — FIXING THE TAG WHEN THE SNIPPET IS THE SECOND SENDER. The duplicate is often outside Tag Manager entirely: a gtag snippet pasted in the theme plus the Google tag in the container. Rebuilding the Tag Manager tag leaves the snippet in place and the count stays double.
DEAD END — A SECOND page_view TAG HIDING IN THE CONTAINER. The Google tag sends page_view by itself. A GA4 Event tag named page_view on the same trigger doubles it, and because both tags look right, the list of tags has to be read one tag at a time to spot it.
DEAD END — COUNTING A SAMPLE OF ONE. One action producing one event proves nothing when the duplicate fires only sometimes. Count 10 actions. A doubling that appears on 10 of 10 actions is a second sender; a doubling on 3 of 10 is a trigger that fires twice on some pages.
End state
One action, one event, one request: the count per action back to one, and the second sender named and removed. The reports now count each action once, and the duplicate tag or snippet is gone, not just disabled in a draft.
Sources
- Tag Manager Help — Preview and debug containers — The debug view showing how tags fired and in which order, for each event
- Analytics Help — Confirm that you are collecting data — Realtime as the place to count the events one action produces
Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened 11 November 2026. What was run: the duplicate counts, recomputed — 10 actions, 20 events counted, 10 expected, so 10 extra, and 1 event per action after the fix. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.