Analytics and Tracking

Duplicate Events

Also called Double counting, duplicate conversions

One real action recorded more than once, inflating conversions and teaching automated bidding to chase results that never happened.

Quick facts: Duplicate Events

Category
Analytics and Tracking
Also called
Double counting, duplicate conversions
Level
Intermediate
Affects
Conversion totals, cost per lead, automated bidding
Where to see it
GA4 DebugView, Tag Manager preview, Meta Events Manager, Google Ads conversion diagnostics
In this article4
  1. How duplicate events happen
  2. Why duplicate events matter
  3. Common mistakes with duplicate events
  4. How to act on it

How duplicate events happen

A duplicate is one action reaching the platform as several. The usual source is two things sending the same event without knowing about each other: a tag placed directly in the theme alongside the same tag in a container, an ecommerce plugin with built-in tracking plus a manual setup, or two containers left behind after a redesign.

Triggers cause the rest. A conversion tied to a thank-you page view fires again every time the visitor refreshes, returns with the back button or bookmarks the page. A form event set to fire on both submission and the following page view counts twice by design. Single-page sites can fire on every internal route change. And when a browser pixel and a server-side sending method both report the same purchase, they are counted separately unless each carries a shared identifier the platform can match them on.

Why duplicate events matter

The reporting damage is obvious: conversions look higher than they are, cost per lead looks lower, and revenue in analytics disagrees with the accounts. Decisions made on inflated numbers tend to be expansive ones, so budget grows on the basis of results that never existed.

The costlier damage is invisible. Automated bidding learns from conversion signals, so if certain paths duplicate and others do not — a checkout that refreshes, a landing page with a legacy tag — the platform concludes those journeys are more valuable and buys more of that traffic. The account then drifts towards whatever is easiest to double-count, which is not the same as whatever is most profitable.

Common mistakes with duplicate events

The first is trusting deduplication to happen on its own. Matching only works when both sends carry the same identifier for the same action, in a field the platform is actually reading; without it, two reports of one purchase are two purchases. The second is leaving the counting setting wrong: an enquiry form should generally count once per click, since the same person filling in two forms is still one lead, while sales usually count every occurrence.

The third is checking totals rather than journeys. Duplication is easy to see when you complete one conversion and watch the event count, and almost impossible to see in a monthly total that merely looks encouraging. The fourth is removing the wrong copy — deleting the container tag while a hardcoded snippet survives leaves you with a tag nobody can maintain.

How to act on it

Test the way a real visitor behaves. Complete a conversion, refresh the confirmation page, press back, and submit a second form; then check what was recorded. Anything more than the number of genuine actions is a duplicate to chase.

Fix the cause rather than the symptom: remove the redundant tag, trigger on the submission event rather than a page that can be reloaded, and make sure every purchase carries an order identifier so repeated sends collapse into one. Where the same event is deliberately sent from both the browser and a server, follow the platform’s matching requirements exactly, as described under event deduplication. Then confirm the repair with the same walk-through you would use for any tag validation, on a phone as well as a desktop.

Do and do not

Do

  • Complete a test conversion and count the events recorded
  • Trigger on form submission rather than a reloadable page
  • Send a unique order or enquiry identifier with every conversion

Do not

  • Assume browser and server sends deduplicate themselves
  • Leave a hardcoded tag beside the same container tag
  • Count every occurrence for enquiry forms

Questions people ask about this

How do I know if my conversions are duplicated?

Complete one conversion yourself and watch what gets recorded. Submit the form, then refresh the confirmation page and press the back button, checking the event count after each step in debug view and in the destination platform. If a single genuine action produces more than one event, something is firing twice and the monthly totals are overstated.

Why does my thank-you page conversion fire more than once?

Because a page view can be repeated and a form submission cannot. Refreshing the confirmation page, returning to it with the back button or bookmarking it all count as fresh views, so any tag triggered by that view fires again. Trigger the conversion on the submission event instead, or dedupe using an identifier unique to each enquiry or order.

Does sending events from both the browser and a server cause duplicates?

It does unless both sends carry the same identifier for the same action in the field the platform matches on. Given that identifier, the platform recognises the pair and keeps one. Without it, each send is treated as a separate conversion. Test the setup with a real purchase or enquiry before trusting the reported totals.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.