Featureavailable
Order-level deduplication across browser, server and retries
A purchase can arrive from the thank-you page, your server, a webhook retry and a chat order record. Trakero keeps one, and tells every platform so their own deduplication agrees.
Illustration of the event flow
What you get
Two layers
Exact repeats are dropped at ingestion for 48 hours; copies from different sources merge into one event with several receipts.
Same id everywhere
event_id purchase_{order_id} for Meta, TikTok, Pinterest and Snap; transaction_id for GA4.
Visible
The event inspector shows each receipt, which one was a duplicate, and what each platform received.
Set up in minutes
- 1Send the order id with every purchase.
- 2Use the same order id in the browser and on the server.
- 3Check an order in the debugger to see the merged receipts.
Questions
What if two orders share an id?+
Order ids must be unique per store; a second order with the same id would be treated as the same purchase.
Platform rules from Meta: Handling duplicate Pixel and Conversions API events.