Event Match Quality
In short
Event Match Quality (EMQ) is a Meta score from 0 to 10 that rates how well your server events can be matched to a Meta account using customer data.
Also known as: EMQ, event match quality score
Event Match Quality (EMQ) is a score in Meta Events Manager that rates, on a scale from 0 to 10, how well Meta can match the events from your Conversion API to a specific Facebook or Instagram account. The higher the score, the more conversions Meta can attribute to its ads – and the better the algorithm learns.
How the score works
For each event, Meta evaluates which customer information parameters you send and how often they match an account. Typical parameters are:
- Email address and phone number (protected by hashing)
- First and last name
fbc(derived from the ad's fbclid) andfbp(the Meta Pixel browser ID)- IP address, user agent, external ID
An event that only contains IP and user agent usually scores low. Add email, phone number and fbc, and the score goes up significantly.
Example
A coaching business sends its Lead event through the browser pixel only. Meta receives fbp, IP and user agent, and the score sits at 4.2. After the business also sends the Lead event server-side with hashed email, phone number, name and fbc, Event Match Quality rises to 7.8. Meta can now match far more leads to the right ads.
Event Match Quality in lead generation
A high score is especially valuable in lead generation: forms collect exactly the data Meta needs for matching. It gets even better when you send back not only the lead but also later deals from your CRM – those events are matched via email and phone number as well.
The LeadMetrics Conversion API sends events to Meta with SHA-256 hashed email, phone number and name, plus the click IDs fbc and fbp. These are exactly the parameters Event Match Quality rates. You can see the score itself in Meta Events Manager.
Common mistakes
- Data not normalized: ‘Max@Company.com ’ with capitals and a trailing space produces a different hash than ‘max@company.com’ – the match fails.
- Phone number without country code: ‘(555) 123…’ instead of ‘1555123…’ often isn't recognized.
- Only watching the score: A high score on an unimportant event like PageView doesn't help if your Lead event matches poorly.
Ready for better tracking?
Frequently asked questions
Guides on this topic
Articles on this topic
- Conversion APIs for Lead Generation: Meta, Google, TikTok and LinkedIn ComparedAll major ad platforms now accept leads and deals server-side, but each one differently. Match keys, click IDs, lead events, time limits and deduplication for Meta, Google Ads, TikTok and LinkedIn at a glance, as of October 2026.
- Meta Conversion Leads: Why Cheap Leads Are ExpensiveYour Meta lead campaigns deliver cheap leads, but sales can hardly reach anyone? With the Conversion Leads performance goal, Meta optimizes for leads that progress in your CRM. Requirements, setup and common mistakes.
- Meta Attribution in 2026: What Engage-Through Means and Why Conversions Are MissingSince March 2026, Meta only counts link clicks as clicks, while likes and saves count as engage-through. Two view windows are gone, too. What changed and how to read your numbers correctly.
- Google Data Manager API and Enhanced Conversions for Leads: What Changed in 2026Since June 15, 2026, the Google Ads API no longer accepts new offline conversion import integrations. What the Data Manager API is, how enhanced conversions for leads work and what to do now.
Related terms
All termsConversion API · CAPI
A Conversion API (CAPI) is an interface that sends conversions directly from server to server to ad platforms like Meta or Google, without the browser.
Hashing
Hashing turns data like email addresses into a fixed string using a one-way function (e.g. SHA-256), so the original can't be calculated back from it.
fbclid · Facebook Click Identifier
The fbclid is the Facebook Click ID Meta adds to links from Facebook and Instagram, e.g. ?fbclid=IwAR2... What it means, whether you can remove it and how it is used.
Event Deduplication
Event deduplication makes sure a conversion sent through both the pixel and the Conversion API is only counted once by the ad platform.
Server-Side Tracking
Server-side tracking sends tracking data to ad and analytics platforms from a server instead of the browser – more robust and under your control.
Client-Side Tracking
Client-side tracking captures user actions with JavaScript directly in the browser and sends them from there to analytics and ad platforms.