Event Match Quality (EMQ) is Meta's score, visible in Events Manager, for how confidently it can connect a conversion event you send back to a specific person who saw or clicked an ad. It's scored on a 0-10 scale per event source and directly affects attribution accuracy and, by extension, how well Meta's optimization algorithm can find more people likely to convert. A low EMQ doesn't stop your pixel or CAPI from working, but it quietly degrades everything downstream of it.
What EMQ actually measures
EMQ is calculated from the customer information parameters included in each event's user_data block - hashed email, phone number, first and last name, city, state, zip, date of birth, gender, external ID, plus the automatically captured fbp and fbc browser identifiers and client IP/user agent. Meta scores both how many of these fields are present and how well they match against its own user records.
A score in the 6-8 range is typical for a reasonably well-instrumented e-commerce or lead gen account. Scores below 4 usually indicate missing hashed PII entirely (pixel-only setups sending just fbp/fbc), and scores above 8 usually mean CAPI is sending multiple well-formatted identifiers per event.
The fields that move the needle most
Email and phone number carry the most matching weight because they're the most stable, unique identifiers Meta can hash-compare against its own database. Sending both, correctly SHA-256 hashed after lowercasing and trimming whitespace, is the single highest-leverage change most accounts can make.
Name and location fields (first name, last name, city, state, zip) add incremental match strength, particularly useful for events where email or phone isn't available - for instance, a phone-based lead intake where you only capture a name and callback number at first contact.
- em (email) - hash after trimming and lowercasing, no exceptions
- ph (phone) - strip formatting characters, include country code, then hash
- fn/ln (first/last name) - lowercase and hash, no punctuation
- external_id - your own internal customer or user ID, hashed, useful when synced with a CRM
- fbc/fbp - never hash these, pass them exactly as captured from the click ID or cookie
Common mistakes that tank EMQ
The most frequent error is hashing fields inconsistently - for example hashing email with mixed case or including leading/trailing spaces, which produces a hash that will never match Meta's own normalized version even though the underlying email is correct. Another common issue is sending fbc only from a cookie that expires quickly (Meta's own fbc cookie is set for 90 days by default, but some sites overwrite it or fail to persist it across sessions), leaving click-based matching weaker than it should be.
For lead gen funnels specifically, a frequent gap is capturing only an email at the top of the funnel and never enriching the event with phone or name data collected later in the sales process, even though offline conversion uploads are the natural place to add that data retroactively.
A practical improvement checklist
Start by pulling the EMQ breakdown in Events Manager for your Purchase or Lead event and identifying which fields show as 'not received' versus 'received but not matched.' The former is a data collection gap; the latter usually means a hashing or formatting bug worth fixing immediately since it's silently wasting data you're already capturing.
Next, audit your checkout or lead form to confirm you're capturing phone number wherever possible, even as an optional field, since it's the second-strongest identifier after email. Finally, if you're running offline conversions from a CRM, make sure every uploaded record includes as many identity fields as the CRM has on file, not just email.
Why this compounds over time
Higher EMQ doesn't just improve reported attribution - it improves Meta's ability to build accurate lookalike and value-based audiences from your conversion data, which feeds directly back into campaign performance. Accounts that neglect EMQ often see gradually rising CPAs that get misdiagnosed as an audience or creative fatigue problem when the root cause is a tracking data quality issue.
Power Ads reviews EMQ scores as part of ongoing account management, catching hashing and field-coverage issues before they compound into rising acquisition costs.
Key takeaways
- EMQ (0-10) measures how confidently Meta can match your conversion events to real users
- Email and phone are the highest-leverage fields; always hash consistently (lowercase, trimmed, SHA-256)
- Check Events Manager's per-field breakdown to distinguish missing data from hashing bugs
- Enrich offline conversion uploads with every identity field your CRM has, not just email
- Declining EMQ often masquerades as creative or audience fatigue - check tracking data quality first
FAQ
What EMQ score should I be aiming for?
There's no universal target, but most well-instrumented direct response accounts land in the 6-9 range. Anything consistently below 4-5 signals a real data gap worth fixing.
Does a low EMQ mean my pixel is broken?
Not necessarily. The pixel can be firing correctly while still sending minimal identity data - a low EMQ is often a data enrichment problem, not a broken integration.
Can I improve EMQ without changing my checkout form?
Yes, to a degree - fixing hashing bugs, adding CAPI alongside the pixel, and enriching events with fbc/fbp all raise EMQ without any customer-facing form changes.
