Meta
Meta Conversions API Setup: Pixel Deduplication, Hashing and Event Quality
How the Meta Pixel and Conversions API work together, how deduplication works, what must be hashed, and how to test your setup.
Meta's ad system can only optimize toward the events it receives. If your tracking misses purchases, or counts each one twice, the campaign learns from a distorted picture. The Conversions API exists to improve that signal. This guide explains how it fits with the Meta Pixel and which details matter most, based on Meta's developer documentation as of October 2026.
What the Conversions API does
The Conversions API sends marketing data from your server, website platform, app or CRM to Meta. Server events are tied to a dataset ID and processed like data from other sources, so they can be used for measurement, reporting and optimization in the same way as Pixel events.
It doesn't replace the Pixel. Meta recommends a redundant setup, where you send the same events through both channels. Examples include Purchase, Initiate Checkout and Contact. The Conversions API can capture website events the Pixel misses because of network issues or page loading errors, and it also covers offline events that a Pixel can't capture at all.
Your setup options
If you already use the Pixel, Meta offers a route to set up the Conversions API for website events from Events Manager, with no code and no setup fee. That's a reasonable start for a simple store. A direct server integration takes more work, but it gives you more control over what is sent and when. It suits businesses with custom checkouts, custom software or CRM events such as a lead becoming a customer.
How deduplication works
Sending events from two places creates an obvious risk: one purchase could count as two. Meta handles this through deduplication, and it recommends the event ID and event name method:
- The Pixel's eventID must match the Conversions API's event_id.
- The Pixel's event must match the API's event_name.
- Use a unique ID for every event.
Timing matters too. Events are deduplicated only if they arrive within 48 hours of the first event with that ID. When matching events don't differ meaningfully, Meta generally prefers the one it received first.
There is a second method, using the same event_name along with fbp or external_id values from both browser and server. It only works for browser events that are followed by server events, so the event ID method is the safer default.
In practice, generate the ID once, at the moment the event happens, and pass that same value to both the browser and the server. An order ID can often serve for purchases. Bugs tend to appear when the two sides generate IDs separately.
Which fields are required
Meta's best-practice documentation lists required fields that are easy to miss:
- For all website events: action_source, event_source_url and client_user_agent.
- Meta's best-practice page also lists external_id and event_id as required for all events.
- action_source must be accurate. Offline events should use an appropriate value other than website.
- At least one user_data parameter must be supplied in the correct format.
What to hash and what to leave alone
Customer data needs careful handling, and Meta is specific. These must be hashed with SHA-256 before sending:
- Email (em) and phone (ph).
- First name (fn) and last name (ln).
- Date of birth (db) and gender (ge).
- City (ct), state (st), zip code (zp) and country.
Other values must not be hashed, including client_ip_address, client_user_agent, fbc and fbp. Meta recommends hashing external_id, but doesn't require it. If you don't use Meta's Business SDK, you have to do the hashing yourself. Mixing these up is a common way to send events that look fine but match poorly.
Before you send anything, decide what your privacy policy allows and what consent your customers have given. Meta's technical pages explain how to send the data, not whether you may. That decision belongs with your legal adviser.
Improve event match quality
Only matched events can be used for attribution and ad delivery optimization, so matching has a direct effect on results. Meta says that additional customer information, such as email, IP address, name and phone, can raise Event Match Quality. It also warns that weak combinations, such as first name plus gender alone, are treated as invalid. If you send fbp and fbc as user parameters, refresh those values regularly.
Send only fields you have a real reason to collect and a right to share. More data isn't always better if it conflicts with your privacy commitments.
Send events promptly
Meta recommends sharing events as they happen, either in real time or in batches close to real time. A nightly batch job may be simple to build, but it isn't what Meta advises for campaign performance. If your checkout already sends order webhooks, those are often a natural trigger for server events.
Test before you trust it
Meta provides two main checks. The Payload Helper validates the structure of what you send, and the Test Events tool verifies that events arrive and deduplicate properly. A sensible test sequence looks like this:
- Place a real test order in a staging or low-risk setting.
- Confirm both the browser and server events appear in Test Events.
- Confirm they share an event ID and are recorded as one event.
- Compare event counts with your order system over several days.
That last step is the one people skip. Your own order records are the reference point. If Meta reports many more purchases than your store has, suspect duplication. If it reports far fewer, look for lost events or poor matching.
Our team can help you set up and test Pixel and Conversions API tracking for your business.