Meta Pixel plus Conversions API: how to stop events counting twice, and what match quality tells you
Meta recommends sending events from both the browser and your server. That only works when Meta can tell the two copies are the same event.
The short answer
With the Pixel and the Conversions API both running, the same event reaches Meta from the browser and from your server. Meta counts it once when the two copies carry the same event name and the same event ID. When they don't, it can count twice. Event Match Quality is a separate score for how well your events can be matched to people on Meta.
On this page
How deduplication works
Meta recommends running the Conversions API alongside the Pixel, which it calls a redundant setup, and says anyone sending the same event both ways must set up deduplication.
The method Meta recommends uses two keys. The browser event's name must match the server event's name, and the Pixel's event ID must match the server's event ID. When both match and the copies arrive within 48 hours of the first one, Meta keeps one and drops the rest. It generally keeps the copy that arrived first.
Meta also documents a fallback that matches on the event name plus its browser ID or your own external ID. Meta says it generally only works when the browser event arrives before the server event, so the event ID method is the one to build on.
How to check yours
Meta gives you three places to look.
- The Test Events tool in Events Manager shows server events as you send them, so you can send one test purchase and see whether both copies arrive.
- Event details in Events Manager include a deduplication view with the rate of events deduplicated and how often each key is used. Meta shows a warning when the rate is too low.
- The Dataset Quality API reports deduplication key coverage and event coverage, meaning the share of Pixel events also sent by the Conversions API with matching keys. Your developer or tag manager can read it.
I check this by sending one test action from the site and following it into Events Manager, before and after a consent choice.
What Event Match Quality tells you
Event Match Quality is a score Meta shows for each event in Events Manager. It measures how well the customer information you send with a server event, such as a hashed email or phone number, can be matched to a Meta account. Meta scores it out of 10 and says it's available only for web events.
Treat it as a diagnostic. A low score tells you which customer details are missing from your server events. It doesn't tell you whether an event was counted twice, which is what deduplication covers. Meta's own guidance is to aim for 6.0 or higher.
Events and orders
Duplicates also happen when the same purchase is sent from two places, such as a Pixel tag in Tag Manager and a store app that also sends the Pixel event, each with its own ID. Meta can't tell those apart.
The next step is my own advice, and Meta doesn't state it. Use one stable ID per business action, such as the order number or the accepted lead's ID, and send it as the event ID from both the browser and the server. Then the copies match, and you can trace any event back to a real order.
Consent and privacy
The Conversions API sends data from your server, so what it sends should follow the visitor's choice the same way the Pixel does. Meta also documents Limited Data Use, an option for US state privacy laws that covers both the Pixel and the Conversions API. Ad pixels and opt-outs, whether tracking follows the choice and Meta's health and wellness restrictions cover the details. Legal questions belong with your counsel.
Questions about the Pixel and the Conversions API
Do I need deduplication if I only use the Conversions API?
Meta says advertisers who don't send the same event twice don't need to set it up. You need it when the Pixel and the Conversions API both send the same event.
How long does Meta wait to match the two copies?
Up to 48 hours from the first copy with a given event ID, according to Meta. Copies that arrive later aren't deduplicated.
Does a higher Event Match Quality score mean better results?
It means Meta can match more of your events to people. Meta recommends a score of 6.0 or higher. The score doesn't check whether events are counted once.
