What Is Event Match Quality on Meta? How to Improve It

Event match quality (EMQ) is Meta's score that measures how accurately your conversion events match Meta user profiles, with higher scores enabling better ad targeting, lower CPMs, and more efficient conversion optimisation.

Last updated: February 2026

Table of Contents

• What Event Match Quality Measures
• EMQ Score Range
• Why EMQ Matters for DTC Performance
• How EMQ Is Calculated
• Customer Information Parameters
• How to Improve EMQ
• Conversion API and EMQ
• Common EMQ Issues
• Key Takeaways
• FAQ

What Event Match Quality Measures

When a conversion event (like a purchase) fires on your Meta Pixel or via Conversion API, Meta receives customer information that it uses to match the event to a specific Meta user profile. This matching enables:

• Attribution: connecting the conversion to the ad that influenced it
• Optimisation: teaching the algorithm which user types convert
• Audience building: creating accurate Custom Audiences for retargeting

Event match quality scores how accurately your events are being matched to Meta profiles. A high EMQ score means Meta is confidently identifying which users are converting. A low score means matches are uncertain, degrading attribution accuracy and optimisation effectiveness.

EMQ Score Range

Meta displays EMQ in Events Manager on a scale:

Most DTC brands without Conversion API implementation score in the 4-6 range. With proper CAPI setup and high-quality customer data parameters, scores of 7-9 are achievable.

Why EMQ Matters for DTC Performance

Better Targeting

When Meta matches purchase events accurately to user profiles, it builds a more accurate picture of who your buyers are. The algorithm uses this picture to find similar users. Higher EMQ = better prospecting targeting.

Lower CPMs

Meta's algorithm gives lower CPMs to campaigns with confident conversion attribution. Higher EMQ tells the algorithm it can trust your data, leading to more aggressive optimisation and often better CPM efficiency.

More Accurate Retargeting

Custom audiences built from high-EMQ purchase events are more accurate. Your "30-day purchaser" audience with excellent EMQ includes the right users; a low-EMQ version may miss buyers or include false positives.

Better ROAS and CPA Reporting

Higher EMQ means Meta can attribute more conversions correctly. Paradoxically, improving EMQ sometimes shows lower immediate ROAS as Meta stops double-counting, but actual campaign performance and algorithm efficiency improve.

How EMQ Is Calculated

Meta calculates EMQ based on the customer information parameters included with each event and how well they match a Meta user profile:

Matching Parameters (by matching power)

The key insight: Email is by far the most powerful matching parameter. Ensuring your checkout process captures and passes email to Meta (via Pixel and CAPI) is the single biggest EMQ improvement for most DTC brands.

Customer Information Parameters

To pass customer parameters via Meta Pixel:

fbq('track', 'Purchase', {
  value: 79.99,
  currency: 'USD',
  content_ids: ['SKU123'],
  content_type: 'product'
}, {
  em: 'HASHED_EMAIL', // Required - SHA256 hash
  ph: 'HASHED_PHONE', // Recommended
  fn: 'HASHED_FIRST_NAME', // Recommended
  ln: 'HASHED_LAST_NAME', // Recommended
  zp: 'HASHED_ZIP', // Helpful
  ct: 'HASHED_CITY', // Helpful
  st: 'HASHED_STATE', // Helpful
  country: 'HASHED_COUNTRY', // Helpful
  db: 'HASHED_DOB', // Optional
  ge: 'HASHED_GENDER' // Optional
});

All customer parameters must be SHA256-hashed before sending to Meta. Meta hashes the same data on its side and compares. This means you can send identifiable data (email, phone) to Meta without transmitting plaintext personal data.

How to Improve EMQ

1. Implement Conversion API (CAPI)

The single most important EMQ improvement. Browser-based Pixel data is incomplete due to iOS 14 tracking restrictions, ad blockers, and browser privacy settings. CAPI sends conversion data server-side directly to Meta, bypassing client-side tracking gaps.

Shopify brands: Enable the native Meta integration in Shopify Settings > Apps > Meta. This automatically implements server-side CAPI.

Custom implementations: Use Meta's CAPI Gateway, or a customer data platform like Segment, Elevar, or Klar to send server-side events.

2. Pass Email with Every Purchase Event

Email is the highest-matching-power parameter. Ensure your checkout captures email before purchase (not just at confirmation) and that email is passed hashed to both Pixel and CAPI.

Many brands miss this: if a user checks out as a guest and does not see the email field until the confirmation page, the purchase event fires before email is captured.

3. Deduplicate Events

When you run both Pixel (browser) and CAPI (server), the same purchase event fires twice. Without deduplication, Meta sees double the conversions. Use the `event_id` parameter (a unique ID for each purchase) in both browser and server events so Meta can deduplicate correctly.

4. Pass Phone Numbers

After email, phone number is the second most powerful matching parameter. Use E.164 format (e.g., +447911123456), hash with SHA256, and pass with purchase events.

5. Include Name and Location Data

First name, last name, city, state, and zip code provide additional matching signals when email or phone is not available. Include these from your checkout/order data.

Conversion API and EMQ

Conversion API is the most effective single action for improving EMQ. Meta recommends a score above 7.0, which is typically achievable with CAPI implementation + email parameter.

Before CAPI: Most Pixel-only implementations score 4.5-6.0 EMQ due to browser tracking gaps. After CAPI: Typical improvement to 6.5-8.5 EMQ depending on data quality and parameter completeness.

In MHI Media's experience, DTC brands that implement CAPI properly see an average of 1.5-2.5 EMQ score improvement, which translates to measurable CPA improvements of 10-20% as the algorithm gains better conversion data.

Common EMQ Issues

Not passing email: The most common issue. Resolve by ensuring email is collected at checkout start, not just at confirmation, and passed hashed with all purchase events. Event deduplication failures: Running Pixel + CAPI without event_id deduplication shows double conversions, inflating reported results while degrading algorithm quality. Using unhashed parameters: Customer data must be SHA256-hashed. Sending plaintext email to Meta is both a privacy violation and a technical error. Missing server-side implementation: Pixel-only tracking in 2026 is significantly incomplete. iOS 14+ and browser privacy settings block a large percentage of events. CAPI is no longer optional for competitive DTC advertising.

Key Takeaways

• EMQ measures how accurately Meta can match your conversion events to user profiles (scored 0-10)
• Higher EMQ improves targeting accuracy, reduces CPMs, and strengthens Custom Audiences
• Email is the highest-power matching parameter; implement CAPI to ensure email passes with every purchase
• The biggest EMQ improvement comes from implementing Conversion API alongside the browser Pixel
• Target EMQ above 7.0; most brands improve from 5.0 to 7.5+ after proper CAPI implementation

FAQ

How do I check my Event Match Quality score?

In Meta Events Manager (business.facebook.com/events_manager), click on your Pixel, then go to the "Overview" or "Test Events" section. You will see an EMQ score for each event type (Purchase, Add to Cart, etc.). The score refreshes as events are processed.

Does a higher EMQ score directly improve ROAS?

Not immediately and not always. Better EMQ improves the algorithm's data quality, which leads to better targeting accuracy and eventually lower CPA. However, when you fix deduplication issues alongside improving EMQ, you may see reported ROAS decrease temporarily (as fake double-counted conversions are removed) while actual performance improves.

What is the fastest way to improve EMQ?

(1) Enable CAPI via Shopify's native Meta integration or a CAPI partner, (2) ensure email is collected and hashed with purchase events, (3) implement event deduplication with a consistent event_id. These three steps typically improve EMQ by 1.5-3 points within 7 days.

My Shopify store is already integrated with Meta. Does that mean I have CAPI?

Shopify's native Meta integration does include CAPI functionality, but you need to ensure it is enabled in your Meta app settings within Shopify. Go to Shopify Admin > Settings > Apps > Meta and verify that "Share data with Meta" is set to maximum. This enables server-side event sending alongside the browser Pixel.

---

MHI Media implements CAPI and optimises event match quality for DTC clients. Get a free pixel audit.