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.
