What Event Match Quality measures
Every conversion event you send to Meta carries customer information alongside it — an email address, a phone number, a name, a city, a browser identifier. Meta uses those fields to work out which person the event belongs to, because an event it cannot attach to anyone is of limited use for optimisation or reporting.
Event Match Quality, usually written EMQ, is the score Meta shows for how well that matching went. It reflects two things: how many useful fields you sent, and how well formatted they were. Sending more of the right fields lifts it. Sending them in a form the platform cannot process — a phone number without a country code, an email with stray spaces, values hashed before being normalised — wastes them entirely, and the score reflects that as though they were never sent.
The score is shown per event type, not for the account as a whole, so a purchase event and a lead event can look very different from each other.
Why Event Match Quality matters
Matching is what connects an action on your website to a person Meta can recognise. When it works, the platform can credit the conversion to the ad that caused it, exclude that person from campaigns aiming to acquire them again, and use them as an example when looking for similar people. When it fails, the event still exists but floats free of anyone — counted, perhaps, but not learned from.
That makes it one of the few diagnostic scores worth watching regularly. A drop after a website change is a reliable early warning that fields have stopped being passed, usually long before the conversion numbers themselves look wrong.
Common mistakes with Event Match Quality
The first is treating a low score as proof the pixel is broken. It is a matching measure, not a health check. A working setup on a business whose customers rarely log in or leave an email address will score modestly, and that is a fact about the audience rather than a fault to fix.
The second is chasing the score by collecting more than you need. Adding fields to a form purely to raise a number in Meta’s interface runs straight into the reason those fields were left out — it lowers form completion and it works against data minimization. Send what you already lawfully hold, not what you could persuade someone to type.
The third is a formatting problem masquerading as a data problem. Fields must be normalised — lowercase, trimmed, phone numbers in international format — and then hashed exactly as specified. Get that order wrong and even complete data matches nothing.
How to act on it
Check the score per event in Events Manager and treat it as a trend, not a target. Note where it sits when the setup is known to be correct, then watch for movement; a sudden fall after a deployment is worth investigating the same day.
To improve it honestly, send the fields you already have but currently do not pass — logged-in customer details, checkout data, information the CRM holds — rather than asking for more. Confirm normalisation and hashing happen in the right order, and cover both the browser and server copies of each event, since a pixel and Conversions API setup is usually where the missing fields are recovered.
