Guide
Meta or Google Ads counting purchases twice: how to check
Published Nov 19, 2026
If Meta or Google Ads shows more purchases than your store took, the confirmation page may be sending some orders twice. Here is how to check by hand, and what TraceLog shows.
The likely causes
- The confirmation page opened again. A buyer returns to it from the order email, reloads it, or comes back from a payment provider's page, and its tag sends the purchase again.
- A tag that fires on every load. A plugin's tag, or a Tag Manager trigger set to the page and not to the order, sends the purchase each time the page is displayed, not once per order.
- Two installs. A plugin and a Tag Manager tag, or a tag in the code and Tag Manager, each send the same purchase.
Google Ads can recognise a repeat by the transaction ID the purchase carries: when the second matches the first, the duplicate is not counted, and without one a customer who reloads or returns to the page can be counted again (Google Ads Help). Where a platform has no such key on the purchase, each send is a purchase.
How to check it by hand
- In Meta's Events Manager, open Test events on your pixel, place a test
order and watch the
Purchaseevents it lists. Two for one order is a repeat. - For Google Ads, open Tag Assistant on the confirmation page and look at each conversion tag that fires: check that it carries a transaction ID, and that the ID is the order's number.
- Reload the confirmation page, and open it again from the order email, and count what each platform's tag sends the second time. A page that sends nothing is right.
- Compare a day's purchases in each platform with that day's paid orders in your store's admin.
What TraceLog sees and what it does not
TraceLog reads nothing from Meta or Google Ads and removes no duplicate from either. What it reads is your confirmation page's own requests: when the browser reports an order that had already been reported, and the second visit's request went to the same tag as the first, it says which tag and how many of the day's orders were sent again, and what to correct.

It is read on sites that send their own conversions and on WooCommerce and PrestaShop, not on Shopify, whose pixel runs in a sandbox that sees none of the page's requests. For Google Ads it counts a repeat only when the purchase went without a transaction ID. It never says what a platform counted, and it states no figure of what a repeat cost.
The count is what the page sent: a renewal that reuses an order number counts as a repeat, Meta requests TraceLog could not read leave it lower, and what your server sends is not in it.
A platform that records a repeated purchase may carry it into its reports and into the bidding built on them. The diagnostics page says what TraceLog shows and what to check; the same order reaching TraceLog twice has its own page, a conversion that arrived again.
Questions
Does TraceLog remove the repeated purchase from Meta or Google Ads?
No. It changes nothing in either platform, and it reads neither.
Does it say how many purchases Meta or Google Ads counted?
No. It says what your confirmation page sent: which tag, on which day, for how many orders and how many of them again.
Does it work on Shopify?
No. Shopify's sandbox hides the page's requests from the pixel, so TraceLog cannot tell a repeat there.
Keep reading
Guide
Published Oct 23, 2026
A sudden drop in conversions can be fewer sales or a step your site stopped recording. How to tell them apart by hand, and what to check first.
Guide
Published Nov 12, 2026
WooCommerce has the paid order but GA4 has no purchase? Usually the buyer paid on another site and never came back. How to check it by hand.
Guide
Published Oct 29, 2026
Awaiting conversions, Needs attention, Misconfigured: what each Google Ads conversion status means, and how to check it by hand.