If your Meta event match quality score is sitting at “Poor” or “OK” in Events Manager, you are losing ad performance silently. Meta cannot match your conversion events to the right users — and your ROAS suffers.
In this guide, I will show you exactly what event match quality means, why yours is low, and five proven ways to improve it — including the most effective fix: server-side Meta CAPI.
What Is Meta Event Match Quality?
Meta event match quality (EMQ) is a score that tells you how well Meta can match your conversion events back to Facebook or Instagram users. The higher the score, the better Meta can attribute conversions to your ads.
Meta assigns an EMQ score to each event type (Purchase, Lead, AddToCart, etc.) on a scale from 0 to 10:
- 7–10 (Excellent): Meta can reliably match your events. Ad optimisation works well.
- 5–6 (OK): Some matching is happening but significant data is lost.
- 0–4 (Poor): Very few events are matched. Your ads are being optimised on incomplete data.
Low event match quality directly causes higher CPAs, worse ROAS, and unstable ad delivery — because Meta is trying to find buyers without knowing who actually bought.
Why Is Your Meta Event Match Quality Score Low?
The most common reasons for low event match quality in 2026:
- Pixel-only tracking (no CAPI): Browser-based pixels are blocked by iOS privacy settings, ad blockers, and browser restrictions. iOS 14.5 alone blocks 30–60% of pixel events.
- Missing customer data parameters: You are not sending email, phone, name, or other identifiers with your events. These signals are what Meta uses to match events to users.
- No deduplication: If you run pixel and CAPI together without proper deduplication, Meta sees duplicate events and reduces the match quality score.
- Sending hashed data incorrectly: Meta requires customer data to be hashed (SHA-256) in a specific format. Wrong hashing = no matching.
- Late or batched event sending: Events sent hours after they occur cannot be matched as accurately. Real-time or near-real-time sending is required.
How to Check Your Meta Event Match Quality Score
To find your current event match quality score:
- Go to Meta Business Manager → Events Manager
- Select your Pixel/Dataset
- Click on Overview → scroll down to the event table
- You will see an “Event Match Quality” column with scores for each event type
If your Purchase event score is below 7, you need to take action. Here is how to fix it.
5 Ways to Improve Meta Event Match Quality
1. Implement Server-Side Meta CAPI (Biggest Impact)
The single most effective way to improve Meta event match quality is switching from browser-side pixel tracking to server-side Meta Conversions API (CAPI).
Here is why server-side CAPI dramatically improves EMQ:
- Events are sent from your server, not the user’s browser — so iOS privacy blockers and ad blockers cannot stop them
- You can send complete customer data (email, phone, name, address) directly from your database — data that pixel cannot access from the browser
- Events arrive in real time, improving match accuracy
- CAPI events typically raise EMQ scores from 4–5 to 8–9 within days of proper implementation
A properly configured CAPI setup sends customer data that was collected at checkout — email address, phone number, and shipping details — directly to Meta’s servers in hashed form. This gives Meta far more data signals to match your events.
2. Send More Customer Data Parameters
Meta uses specific customer data parameters to match events. The more you send, the higher your match quality. The key parameters are:
- em – Email address (hashed) — highest matching power
- ph – Phone number (hashed)
- fn / ln – First name, last name (hashed)
- ct / st / zp / country – City, state, ZIP, country (hashed)
- external_id – Your internal customer ID
- client_ip_address – User’s IP address (not hashed)
- client_user_agent – Browser user agent (not hashed)
- fbc / fbp – Facebook click ID and browser ID cookies
Sending all of these with your Purchase event will push your EMQ score toward 9–10. Email alone can raise your score by 3–4 points.
3. Fix Deduplication Between Pixel and CAPI
If you run both Pixel and CAPI (which you should, for maximum coverage), you must implement event deduplication. Without it, Meta receives duplicate events and your match quality score is penalised.
Deduplication requires:
- The same event_id sent in both the pixel event and the CAPI event
- The event_name must match exactly (case-sensitive)
- Events must fire within the deduplication window (typically 48 hours)
In practice: when a purchase happens, your pixel fires with eventID: "order_12345" and your CAPI sends a server event with the same event_id: "order_12345". Meta deduplicates them and counts only one conversion.
4. Hash Customer Data in the Correct Format
Meta requires all customer data (except IP address and user agent) to be hashed using SHA-256 before sending. Incorrect hashing is a common cause of low event match quality that is easy to miss.
The correct format before hashing:
- Email: lowercase, no whitespace →
john@example.com - Phone: digits only with country code, no spaces or dashes →
16505551234 - Name: lowercase only →
john - ZIP: lowercase, no spaces →
94103
A single typo in the normalisation step means Meta cannot match that data to a user, even if everything else is correct.
5. Send Events in Real Time
Batch sending events (e.g. every 30 minutes or daily) significantly reduces event match quality. Meta’s matching algorithms work best with real-time or near-real-time data.
Best practice: send CAPI events within 1–2 seconds of the conversion occurring on your server. If you use a server-side GTM setup or a direct API integration, this happens automatically. Avoid batch import tools for your primary purchase tracking.
What Is a Good Meta Event Match Quality Score?
Here is what to aim for after implementing CAPI correctly:
- 7.0 or above: Good. Your ads can optimise effectively.
- 8.0–9.0: Excellent. This is achievable with CAPI + full customer data.
- 9.0+: Best possible. Rare but achievable with complete data and perfect implementation.
Most eCommerce stores I work with start at 3–5 (pixel only) and reach 8–9 after a proper CAPI implementation. The improvement typically appears within 3–7 days of the CAPI going live.
How Long Does It Take to See Improvement?
After implementing CAPI with full customer data parameters:
- Day 1–2: CAPI events start appearing in Events Manager
- Day 3–5: Event match quality score starts updating
- Day 7–14: Full impact on ad performance becomes visible (lower CPA, better ROAS)
The score update is not instant — Meta needs a sample of events before it updates the displayed score. Be patient for the first week.
Frequently Asked Questions
Does event match quality directly affect ad performance?
Yes. Higher event match quality means Meta can attribute more conversions to your ads. This improves the training data for Meta’s algorithm, which leads to lower CPAs and more stable ad delivery over time. An EMQ of 8+ versus 4 can mean a 20–40% difference in ad performance for the same budget.
Can I improve EMQ without using the Conversions API?
You can make small improvements by sending more customer data via the browser pixel (Advanced Matching). However, the browser pixel is inherently limited by iOS restrictions and ad blockers. The most reliable and significant improvement comes from server-side CAPI. Without CAPI, you will typically plateau at 5–6 EMQ.
Does Meta Advanced Matching help EMQ?
Yes, Meta Advanced Matching (sending customer data through the pixel) helps and is better than nothing. But on iOS devices, this data is often blocked before it reaches Meta. CAPI sends the same data server-side, bypassing all browser restrictions.
What is the difference between EMQ and event match rate?
Event match quality is a score (0–10) indicating how much customer data is available for matching. Event match rate is the percentage of events that were successfully matched to a Meta user. Both matter, but improving EMQ is the root cause fix — better EMQ automatically improves your match rate.
Need Help Improving Your Meta Event Match Quality?
If your EMQ score is below 7 and your Meta ads are underperforming, a proper CAPI implementation can recover the lost conversions within days. I specialise in Meta CAPI setup for eCommerce and DTC brands on Shopify, WooCommerce, and custom platforms.
Get a free tracking audit — I will check your current pixel and CAPI setup, identify what is causing low EMQ, and tell you exactly what needs to be fixed.
Related guides: What is Meta CAPI? | Meta Pixel vs Conversions API | Meta CAPI Setup for Shopify