Analytics and tracking

Why are my GA4 numbers too high, and how do I find duplicate tags?

A page can load the same tracking tag twice, so one action is sent to GA4 more than once. Check one page at a time in Tag Manager Preview and GA4 DebugView, look for the same event arriving twice, then remove the extra installation.

Published . Last updated . By Hevaris.

How does a page end up sending the same event twice?

A page sends an event twice when two things on it both send that event. Google describes two ways to install the tag, directly in the page code or through Tag Manager, and a page can end up with more than one of them.

How it happensHow to checkFix
The tag is in the page code and also in Tag ManagerIn Preview, see which tags fire for one page load. In the page source, search for your measurement ID and your container IDKeep one installation and remove the other
Two tags in one container send the same eventPreview lists every tag that fired for one actionDelete or pause the extra tag, or narrow its trigger
A theme or plugin adds its own tagSearch the page source for your measurement ID and see where it appearsSwitch the plugin’s analytics setting off, or stop using it for tracking
A server-side and a standalone client-side setup both run for one propertyAsk whoever built the setupGoogle says not to run both for the same property

How do I check one page for duplicates?

Pick one page, perform one action, and count what arrives. Two tools answer two questions: what fired, and what GA4 received.

  1. Open Tag Manager Preview and connect to the page. Google says it shows which tags fired and in what order.
  2. Open GA4 DebugView. It shows events in real time, once debug mode is enabled for your device.
  3. Load the page once. Count the page views that arrive.
  4. Click one link once. Count the events that arrive.
  5. Compare. One action should give one event. Two identical events mean two senders.

Google’s Tag Assistant also reviews the tags, events and data on a page, and its Chrome extension shows the hits sent. Google’s help does not say it flags duplicates, so read the hits yourself.

What can I look for in the page source?

Search the page’s source for your measurement ID and your Tag Manager container ID. Each should appear in the place you expect and nowhere else.

An ID that appears in two places, such as once in the page head and once in a script added by a plugin, is a prompt to look closer. It is not proof of double-counting, so confirm in DebugView.

How do I fix it and confirm the fix?

Remove the extra installation, publish, and repeat the one-page test. The test is the proof, so run it again rather than assuming the change worked.

  • Make one change at a time.
  • Repeat the load and click test in DebugView after each change.
  • Test a second page, because a plugin or template can add a tag on some pages and not others.

Numbers collected before the fix stay as they were, so expect a visible step down on the date you remove the duplicate.

What sources does this guide use?

The primary sources are linked below, so each statement can be checked at its origin.

Frequently asked questions

How do I know the same event is arriving twice?

Perform one action, such as loading a page or clicking a link, with GA4 DebugView open. If the same event appears twice for that single action, something is sending it twice. Tag Manager Preview then shows which tags fired for that action.

Does Google say what happens if the tag is installed twice?

Google's help describes the two ways to install the tag, directly in the page code or through Tag Manager, but the pages we read do not say what happens when both are present. Google does say not to run a server-side and a standalone client-side setup for the same property.

Which installation should I keep?

Keep the one you can manage and test. Google describes both methods. In our view, if you use Tag Manager for several events, installing through it keeps all tracking in one place. Whichever you keep, remove the other, then test again.

Can the fix change my past data?

No. Removing a duplicate stops the extra events from then on. Numbers already collected stay as they were, so expect a visible step down in your reports on the day you fix it.