Google Ads

Double Counting

Also called Duplicate conversions, conversion inflation

The same enquiry or sale recorded more than once, by two tags, two conversion actions or two platforms.

Quick facts: Double Counting

Category
Google Ads
Also called
Duplicate conversions, conversion inflation
Level
Intermediate
Affects
Conversion counts, bidding signals, return on ad spend, trust in reporting
Where to see it
Google Tag Assistant, GA4 DebugView, Meta Events Manager, your own order records
In this article4
  1. How double counting happens
  2. Why double counting matters
  3. Common mistakes that cause double counting
  4. How to fix it

How double counting happens

Every duplicate has the same shape: one real event, more than one thing listening. The Google tag ends up installed both through Tag Manager and hardcoded in the theme, so both copies fire. A conversion action is set to count every conversion rather than one per interaction, so a customer who refreshes the thank-you page is recorded again. Two separate actions cover the same moment — a form submission event and a view of the confirmation page — and each dutifully reports it.

Server-side setups add their own version. When a browser pixel and a server event both describe the same purchase without a shared event identifier, the platform has no way to know they are one event, so it keeps both.

Then there is the reporting kind, where nothing is broken at all: Google, Meta and your analytics each claim the same sale, and someone adds the three totals together in a slide.

Why double counting matters

Inflated conversions do not just embarrass a report. Automated bidding learns from the conversion feed, so phantom conversions teach it that certain keywords, audiences and placements work better than they really do, and the budget follows. The account then optimises confidently towards the wrong thing.

The commercial damage arrives later. Return on ad spend looks strong, spending is scaled up, and the bank balance quietly disagrees. By the time the numbers are reconciled against invoices, months of budget have been allocated on fiction.

Common mistakes that cause double counting

Installing a tag “just to be safe” while an old one is still live is the most frequent. Migrating to Tag Manager without removing the hardcoded snippet is the same mistake wearing a different hat.

Leaving the count setting on every conversion for a lead form is another: that setting suits ecommerce, where a customer really can buy twice, and is wrong for an enquiry. Sending a purchase event on a page that customers can reload or reach from their order history compounds it, unless the order identifier is passed so repeats can be recognised.

Finally, running a browser pixel and the Conversions API together without matching event identifiers is common, and easy to miss because both halves look correct on their own.

How to fix it

Start by testing rather than guessing: submit a real enquiry, watch what fires, then reload the confirmation page and watch again. Anything that fires twice is your answer. Check the page source for stray tags left behind by a previous developer.

Set lead conversions to count one per interaction, pass a unique order identifier with every purchase, and give browser and server events a shared identifier so they can be deduplicated. Decide which conversion action owns which moment and switch the spare to secondary rather than deleting history. Above all, reconcile platform numbers against your own records regularly — that habit belongs with the rest of your analytics and tracking work, and it catches duplicates nothing else will.

Do and do not

Do

  • Test a real submission, then reload and watch again
  • Count lead conversions once per interaction, not every time
  • Pass a shared event identifier for browser and server events

Do not

  • Add conversion totals together across different platforms
  • Leave an old hardcoded tag in place after migrating
  • Delete a duplicate action before bidding has settled

Questions people ask about this

How do I know whether my conversions are being double counted?

Compare the platform's count with your own records for the same period — enquiries in your inbox or CRM, orders in your shop admin. If the platform reports meaningfully more, something is firing twice. Then submit a test enquiry and reload the confirmation page while watching the tag; a second conversion on reload confirms the cause.

Can I just add up conversions from Google, Meta and analytics?

No, and this is the most common version of the problem. Each platform claims credit for journeys it touched, so a customer who saw a Meta ad and then clicked a Google ad appears in both. Adding the totals invents customers who do not exist. Use one source as the scoreboard and treat the others as diagnostics.

Should I delete a duplicate conversion action?

Usually not straight away. Deleting removes the history you need to understand what happened, and it can disturb bidding that has been learning from it. Set the spare action to secondary so it still reports but no longer feeds bidding, let the account settle, and clean up once you are confident the right action is working.

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.