Deduplication is counting one receipt once when the same number arrives by fax and by post. If the numbers do not match, the two copies are harder to merge.
When the Pixel and the Conversions API are used together (a redundant setup), the same event arrives twice. The method the developer docs recommend is event ID plus event name: the browser eventID must equal the server event_id, and the browser event must equal the server event_name. In the pixel you pass it as the fourth argument of fbq, like fbq('track', 'Purchase', {value: 12, currency: 'USD'}, {eventID: 'EVENT_ID'}); with an image pixel you use the eid parameter. If the same key combination reaches the same Pixel ID within 48 hours, the later event is discarded, and when the two do not differ meaningfully the one received first is preferred.
Even without an event_id, sending event_name plus fbp or external_id consistently from both sides can let Meta remove duplicates automatically, with limits. It generally works only when the browser event arrives first and the server event follows, a server event is not discarded if no browser event was seen in the past 48 hours, and nothing is deduplicated when only one source is used.
So events sent by one path need no deduplication, while every event sent through both paths needs the same event_id on both sides. An order number is a good candidate because it is unique per order.
When to use
Use it right after enabling the Pixel and the Conversions API together, to confirm purchases are not counted twice.