Checks in order
- Open one recent purchase in Events Manager and look at how many separate events exist for the same order — one with two sources is correct, two events are not.
- Check whether the browser and server events share an event id. If the browser generates one and the server generates its own, that is the whole bug.
- Check whether the server retries on failure while generating a new id per attempt. A timeout plus a retry then becomes two purchases.
- Check whether Purchase fires both on the confirmation page reload and from the server on order creation. Two triggers, one order.
- Check whether a second pixel, container or plugin is also sending purchases — a duplicate tag is common after a theme migration.
