How to Improve Your Meta Event Match Quality (EMQ) Score

Event Match Quality (EMQ) measures how well Meta can match your conversion events to real Meta accounts. You improve it mainly by sending more and better customer information parameters with every event through the Conversions API: hashed email, phone, name, location, external_id, and the fbc and fbp cookies. Higher EMQ means better optimization and more accurate attribution.

What is Event Match Quality and why does it matter?

EMQ is a score, from 0 to 10, that Meta assigns to each standard event based on how much usable customer information you send. When Meta can confidently tie an event to a person, it can optimize delivery toward people who convert and credit the right campaigns. When it cannot, your events are effectively wasted signal: the same purchase happened, but Meta learned less from it. A low EMQ score therefore shows up as weaker optimization, thinner audiences, and under-reported conversions. For target ranges and how the score is graded, see what's a good CAPI EMQ score.

The number one lever: send more customer information parameters

EMQ is driven almost entirely by how many match keys you attach to each event. Every additional, correctly formatted parameter gives Meta another way to find the person. The parameters that move the score are:

• Email (em). Hashed with SHA-256, lowercased and trimmed. The single strongest key.
• Phone (ph). Hashed, digits only, with country code and no symbols.
• First and last name (fn, ln). Hashed, lowercased.
• Location (ct, st, zp, country). City, state, zip, and country, hashed.
• External ID (external_id). Your own stable customer or user identifier, hashed.
• Click and browser IDs (fbc, fbp). The Meta click ID cookie and browser ID cookie, sent in plain text.
• Client IP and user agent. Passed from the server on every event.

What are the practical ways to improve your EMQ?

• Turn on the Conversions API. The browser pixel alone drops data to ad blockers, consent gates, and iOS. A server feed lets you attach keys the browser never sees. Start with the pixel vs the Conversions API.
• Send hashed email and phone on every event. These two keys alone lift most accounts into a healthy range. Capture them as early as you can in the funnel, not just at purchase.
• Capture and send fbc and fbp. Read the _fbc and _fbp cookies server-side and include them. If a click ID is present in the URL, build fbc yourself so it is never lost.
• Add a stable external_id. A logged-in customer or user ID gives Meta a consistent anchor across sessions and devices.
• Collect more fields at checkout. If you already ask for name, city, and zip, pass them. Data you hold but never send does nothing for your score.
• Fix consent so you keep what you are allowed to use. A blunt banner can strip match keys from consented users. Tune it so permitted data actually flows through.
• Use first-party data well. The whole approach leans on data customers give you directly. See first-party data and the future of tracking.

Google Ads has the same idea under a different name. Its equivalent is enhanced conversions, which sends hashed first-party data to improve matching there too.

What does a good EMQ look like, and how often should you check it?

As a working benchmark, aim for a score of 6 or higher on your key events, with 8 or above being strong. Check it per event, not just per account: a healthy Purchase score can hide a weak Lead or AddToCart. Review it at least weekly, and always after any site, checkout, or tag change, because those are exactly the moments a match key quietly disappears.

How do you keep your EMQ from slipping?

EMQ is not a one-time fix. A theme update, a new checkout flow, a consent tweak, or a developer refactor can drop a parameter without any error showing up. Purchases keep firing, so nothing looks broken, but Meta is matching fewer of them and your delivery slowly degrades. The only reliable defense is monitoring the score over time rather than assuming last quarter's setup still holds.

That is the gap Taglert is built to close. It watches your pixel activity, EMQ, and conversion tracking continuously and alerts you the moment match keys start dropping, so a silent change never costs you weeks of weaker performance before anyone notices.