Event deduplication recognizes two reports of the same action and counts one conversion. For example, a browser pixel and a server API can both report one purchase. Without a matching key, the destination may count two purchases for one order and inflate conversion and revenue reports.

How does event deduplication work?
- Create one ID when the action happens. Use an ID that stays the same across retries and both delivery paths. An order ID can work for a purchase when it uniquely identifies that transaction.
- Send the same ID and event name from browser and server. The destination uses its own matching rules to recognize the two records as one action.
- Give the next action a new ID. A second purchase needs a different ID, even when the same customer makes it. Record a refund as its own event.
For example, send browser Purchase and server Purchase with the same ID, order-123. The ad platform can pair them and count one purchase. If the server generates order-124 for the same order, the pair will not match.
Do Meta, GA4 and Google Ads use the same rule?
- Meta Pixel and Conversions API: Send the same event name and ID in both paths. The browser Pixel uses
eventID; the server payload usesevent_id. Check the pair in Meta Events Manager. See Meta's deduplication documentation. - GA4 purchases: Send a unique
transaction_idwith each purchase. GA4 uses it to ignore a repeated purchase; it is not a general rule for every GA4 event. - Google Ads offline conversions: Within one conversion action, Google Ads uses
transactionIdto deduplicate uploaded events. Check the rules for the specific conversion method you use.
How do you test for duplicate events?
Send one test purchase through both paths. Confirm that both records have the same event name and ID, then check the destination's diagnostics for one counted conversion. Compare accepted purchases with unique paid order IDs in your source system. Test page reloads and server retries, which can send another copy of an event. Finally, block the browser event and confirm the server event can still be counted.
Deduplication prevents overcounting. It does not repair missing events or establish the right to share data with a destination.
How Hardal handles it
Hardal sends the browser and server copies of an action with a shared event ID, so each destination can pair them and count one conversion. The Meta Conversions API Gateway setup guide walks through Pixel and CAPI deduplication step by step.
Related terms: Data discrepancy, Server-to-server, Analytics event, Server-side measurement