What Is Meta Event Match Quality (EMQ)?
·
Event Match Quality (EMQ) is a score Meta's Events Manager assigns to a pixel or dataset based on how well the customer information sent with its events — such as email, phone, and browser identifiers — can be matched to real Facebook and Instagram user profiles. It reflects the completeness and accuracy of match parameters across recent events, not the volume or business value of those events. Meta displays EMQ per event source to help advertisers judge whether their tracking setup is sending enough identifying data for its matching system to work well.
In practice
EMQ is Meta’s built-in feedback signal for how well an advertiser’s event data can support attribution and optimization. It looks at which matching parameters are present in each event — email, phone number, external ID, first and last name, and browser-supplied identifiers like fbp and fbc — and how often they’re hashed correctly and match real accounts. A pixel-only setup that only ever sends fbp/fbc tends to score lower than a setup that also sends server-side Conversions API events carrying hashed email and phone, because more independent matching signals give Meta more ways to confirm the event belongs to a real account.
Common confusion
EMQ is not a measure of conversion volume, ROAS, or campaign performance — a low-EMQ pixel can still report plenty of conversions, it just means those conversions carry less matchable identity data. It’s also not one static number for the whole ad account; Meta scores it per pixel or dataset and it can vary by event type (Purchase vs. Add to Cart, for example). Improving EMQ is a data-completeness exercise — adding parameters like email, phone, and external_id to the CAPI payload — not a bidding or budget change.
How to check
EMQ is shown in Meta Events Manager, on the Overview tab for a given pixel or dataset, next to each event alongside a breakdown of which parameters were present on matched events. The Diagnostics tab flags specific missing or malformed parameters — like an unhashed email field — that are holding the score down, which is where a review usually starts.
Related entries
EMQ depends heavily on sending a consistent event_id across Pixel and server events, and on routing that server-side event through a server container. For a hands-on parameter review, see Meta Conversions API services.
Related entries
- Knowledge BaseWhat Is event_id? (Meta Pixel + CAPI Deduplication)What event_id is, why Meta uses it to deduplicate Pixel and Conversions API events, and where to check match status in Events Manager.
- Knowledge BaseWhat Is a Server-Side GTM Container?The difference between a server container and a web container in Google Tag Manager, and what running one changes.
- ServiceMeta Conversions API
Not sure whether your tracking is actually broken?
Start with a Health Check — a fast, read-only diagnosis that tells you what is wrong before you spend anything fixing it. Prefer email? Send your store URL and one sentence about what looks off.