Deduplication And Multiple Tools

Most sites send the same conversion to several places: analytics, Google Ads, Meta and more. Without care, the same event gets counted twice, by two tags, by a page that fires it again on reload, or by a back-button revisit.

How dedup works

• Send a stable id with the conversion (a transaction_id or event_id) so the vendor can ignore repeats.
• Use fire-once or trigger limits so a tag cannot fire twice per page.
• Fire purchase tags on a server-confirmed step, not just any thank-you page load.

Deduplication becomes essential when you also send events server-side: the browser pixel and the server event share an event_id so the vendor counts one conversion, not two.