Purchase sent again to an ad platform
Last updated Nov 19, 2026
The confirmation page asked Meta or Google Ads to record an order's purchase again. It warns and never blocks.
What was observed
For an order whose page had already asked an ad platform to record its purchase, the confirmation page asked again: a browser conversion arrived under an identifier that had already arrived from the browser, and the second visit's request went to the same tag as the first. TraceLog counts each order once by its identifier, so the repeat is not a second order.
It covers Meta's Purchase and a Google Ads conversion with its label, and
never GA4: a page loaded again requests GA4 for its own page view, and GA4
recognises a repeated purchase by its transaction ID. For Meta, every repeat
counts, whatever key it carried. For Google Ads, only a repeat that carried no
transaction ID counts, because Google counts both as one when the ID matches.
In the application each tag is listed with, for the latest day it appeared, how many orders the page sent to it and how many of them again. The finding warns once a day reaches three orders and a tenth of the orders whose page requested the tag; below that it only states its count and asks nothing. It never names an order and never states what a platform counted.
It is raised on sites that send their own conversions, with the snippet or the npm package, and on WooCommerce and PrestaShop, whose plugin and module emit the conversion each time the confirmation page is displayed. It is not raised on Shopify, whose pixel runs in a sandbox that sees no request of the page.
The confirmation page sent the purchase of an order to an ad platform again. Send the purchase once per order, from the page and from any server that sends it.
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 a server sends is not in it. The guide shows how to check each platform by hand.
What to check
- Find where the purchase is sent to the platform, from the page and from any server that sends it, and check that each order is sent once.
- Open the confirmation page again from the link in the order email and reload it: neither should send the purchase again.
- For Google Ads, send the order number as the transaction ID of each purchase.
- If the page cannot tell a first visit from a return, send the purchase from the step that places the order.
On a site that sends its own conversions, where the page also sends TraceLog the same order again, a conversion that arrived again is raised too, and the two are drawn as one finding with one correction.
Effect on verification
It warns and never blocks. An install can still show Conversion path verified with this condition present, and the condition stays visible on the home and the Path page.