How to Improve Your Event Match Quality (EMQ)

What is EMQ, and why should D2C brands care?

Meta scores every event you send through the Pixel or the Conversion API (CAPI) against its own user database. That score is your Event Match Quality, and it tells Meta how confident it is that the data point you sent, like a hashed email, a phone number, or browser identifiers like the fbp cookie or click ID. Actually belongs to a real account on its platform.

Why does this matter to a D2C brand specifically? Your entire ad account runs on Meta correctly identifying who took which action. Optimization, retargeting, lookalike audiences — all of it depends on Meta matching your data to its own. A weak match leaves Meta optimizing in the dark.

The privacy shift of the past few years made this worse before it got better. iOS 14.5 cut off a huge slice of pixel-based tracking overnight, and browsers keep tightening third-party cookie rules. CAPI was Meta's answer: send first-party data directly from your server, skip the browser entirely, and let server-side signals fill the gap. But CAPI only works as well as the data hygiene behind it - which is exactly what EMQ measures.

The numbers back this up: Meta's own data shows advertisers who added the Conversions API alongside the Pixel cut cost per acquisition by 13% on average - and brands that go further on match quality (external IDs, pre-hash validation, faster event delivery) commonly report CPA improvements in the 10–25% range within two to three months. EMQ is the most direct lens for fixing that on Meta specifically. Learn how to master Event Match Quality (EMQ) for Better Ad Performance in our previous blog.

The business case: why invest in a higher EMQ?

How does a higher EMQ change your conversion tracking?

A better match rate means fewer conversions disappear from your reporting. This shows up most often after iOS updates, when browser signals go missing and Meta needs another way to confirm a purchase occurred. Once Meta trusts your match quality, its algorithm assigns credit to the right ad, ad set, and campaign. So, your budget moves toward what's actually working instead of what merely looks like it's working.

How does EMQ power better retargeting and lookalikes?

Lookalike audiences are only as good as the seed list you feed them. A clean list — hashed emails and phone numbers that actually match real accounts- gives Meta's modeling something solid to extrapolate from, which usually shows up as stronger lead quality or purchase intent in the resulting audience.

Retargeting benefits the same way. When Meta trusts your match, you can retarget shoppers without spamming people who never actually viewed the product. Pair that with a CRM or catalog feed, and you can show someone the exact item they added to their cart instead of a generic ad.

How does EMQ lower your costs?

Brands running mature CAPI setups like server-side tracking with full parameter coverage report CPA drops of 13% on average (Meta), 10–25% reported by brands with mature setups. The mechanism is simple: a sharper match means Meta wastes fewer impressions on people who were never going to convert in the first place. You're not paying to reach fewer people; you're paying to reach the right ones.

What are the key parameters and data points for improving EMQ?

Which extra fields boost your match rate?

Most advertisers stop at name, email, and phone. That's the floor, not the ceiling. A few additional fields can meaningfully move your score: street address, city, state, and ZIP code help most in markets where phone or email coverage is inconsistent. Browser and device signals — user agent strings, IP address — give Meta something to work with even when no deterministic identifier is available, as long as you've captured this with proper consent. Date of birth and gender aren't always available, but when you have them, they add another layer of confidence to the match.

None of these fields fixes a weak EMQ score on its own. Stacked together, they close many small gaps.

What is an external ID, and why does it matter so much?

An external ID is a unique identifier you control — usually the same ID your CRM or order system already assigns to a customer. You're not building new infrastructure; you're handing Meta an anchor point it can use even when email or phone data is missing or inconsistent.

One D2C loyalty program saw match rates jump 25% after adding an external ID alongside the standard fields, purely because it closed the gap for customers who'd given a phone number on one order and an email on another. If you already have stable internal IDs, sending them is close to a free win.

How do you balance deterministic and probabilistic matching?

Deterministic matching happens when Meta can confidently tie a hashed email or phone number to a known account. There is no guesswork involved. Probabilistic matching fills in the gaps using patterns: IP address, device type, browsing behavior.

Send your strongest deterministic data first like email, phone or external ID and let probabilistic signals act as a backup, not a substitute. Include the user agent and IP address with every server-side event, especially for visitors who've declined certain cookie consents. That way, if a deterministic identifier is missing for one transaction, the probabilistic layer can still approximate a match instead of losing the event entirely.

How do you validate data before you hash It?

Hashing bad data just produces a clean-looking hash of garbage. Validate first, hash second. Check that every email contains an “@” symbol and a real domain. Confirm phone numbers carry the correct country code and follow E.164 formatting. Make sure address fields are complete, particularly for international customers, where a missing region or postal code breaks the match entirely. A validation step before SHA-256 hashing catches errors that would otherwise quietly tank your score.

Why does cutting data transfer delay matter?

The longer an event sits before you send it to Meta, the more likely the match falls apart. Sessions expire. Cookies expire. The identifiers you'd use to tie an event to a user have a shelf life, and every minute of delay shortens it.

Real-time delivery via webhooks rather than batch uploads is the simplest fix here. It's not glamorous, but for time-sensitive conversions like lead form fills, shaving minutes off your transfer time can meaningfully change your match rate.

What role does server-side tracking (CAPI) play?

Server-side tag managers — Google Tag Manager Server-Side, Tealium, Segment — capture and process events in an environment the browser can't interfere with. No ad blockers, no aggressive browser privacy settings, no JavaScript error silently killing a pixel fire.

Analytics Mania's 2023 study found server-side implementations captured 15% to 20% more events than client-side tracking alone. That gap is mostly events client-side tracking simply never saw in the first place — not events that were double-counted or inflated.

How do you deduplicate pixel and CAPI events?

Running both Pixel and CAPI is good practice, but only if you deduplicate properly. Generate a unique, randomly assigned event id for every transaction or lead, and keep the timestamps between the Pixel fire and the server event as close together as possible. The tighter the gap, the more confident Meta is that both signals describe the same action. Pairing this with external id ties your internal record to Meta's event logic with very little ambiguity.

Skip deduplication, and you risk inflating your event counts by 20% to 40%. That doesn't just distort your EMQ, it quietly corrupts every performance number built on top of it.

How do you handle data hygiene and privacy rules?

What do GDPR and CCPA require from your setup?

Under GDPR, you need a lawful basis — consent or legitimate interest — before you collect or process user data, and that requirement extends to hashing details for Meta. It's not a separate obligation; it's the same one you already have for any data collection.

CCPA works differently: California residents can opt out of data sharing outright. A consent management platform that can dynamically switch off event tracking for opted-out users is the cleanest way to stay compliant without manually auditing every visitor.

How clean does your CRM data need to be?

Stale data is a quieter problem than most people expect. A 2022 eMarketer study found organizations lose up to 30% of potential matches simply because their CRM data has gone out of date or sits duplicated across records. Ongoing cleansing isn't optional maintenance. It's the difference between a high EMQ and one that slowly decays.

Retention policy matters here too. Holding onto inactive user data indefinitely is a legal liability, not an asset. A 12-to-24-month sunset policy that purges inactive records keeps your data both compliant and, in practice, more accurate. Old data tends to be wrong data.

How do you keep optimizing EMQ over time?

How often should you audit your EMQ?

EMQ isn't something you fix once. Track it alongside CPA, CTR, and ROAS on a regular cadence, and treat any drop — say, from an 8 to a 6, as a signal to investigate, not a number to shrug off. Keeping a change log of CRM schema updates makes it far easier to trace a dip back to whatever caused it.

What should you A/B test?

Not every parameter helps equally in every market. Phone numbers might outperform addresses in one geography and underperform in another. Test removing or adding specific fields and watch how your score responds. Some advertisers go further and feed in customer lifetime value or subscription status as custom data points — useful, but only when anonymized properly and handled with real care.

Which CRM integrations make this easier?

HubSpot, Klaviyo, and Salesforce all offer direct server-side integrations that handle CAPI without custom development — external IDs included. Beyond the initial setup, make sure profile updates sync in real time, so a new email address or phone number doesn't sit stale mid-funnel while a customer is actively converting.

How do you track EMQ and measure whether It's working?

Where do you find your EMQ score?

Meta Events Manager shows your EMQ score under each individual event, broken down by parameter and the percentage of events that included it. The “Poor,” “Fair,” and “Good” labels are blunt, but they're a fast way to spot which fields need attention.

The score only matters if it connects to outcomes. One mid-sized D2C brand saw a 15% increase in repeat purchases after combining server-side tracking with EMQ optimization. It is a result that showed up months after the technical work, not the week after.

Which metrics should you watch alongside EMQ?

CPA and cost per lead are your clearest signals. When they drop after an EMQ improvement, you know the matching change actually moved the needle. If you run loyalty or retention campaigns, watch repeat purchase rate too. A better match often surfaces returning customers your targeting was previously missing entirely.

What's the one takeaway on EMQ?

EMQ rewards patience, not a single fix. Start with a real audit of your CRM and eCommerce data to find where the gaps are. Move to server-side tracking if you haven't already — it's the foundation everything else sits on. Add external IDs to unify customers across touchpoints, validate and test your setup with Meta's own tools, and keep checking the score instead of assuming it stays fixed once it's good.

Do this consistently, and EMQ stops being a vanity metric in Events Manager. It becomes one of the more reliable levers you have for lowering CPA and making your ad spend actually count.

Frequently asked questions

1. What does EMQ actually stand for?

   Event Match Quality. It's Meta's internal score, found in Events Manager, for how confidently it can tie the event data you send to a real account on Facebook or Instagram.

   
   

2. What counts as a “good” EMQ score?

   Meta doesn't publish a universal cutoff, but most advertisers treat anything in the “Good” range in Events Manager as solid. In practice, a score above 6 or 7 out of 10 tends to correlate with noticeably better optimization. Below that, you'll usually see it show up as inflated CPA before you see it in the score itself.

   
   

3. Does EMQ affect how my ads get delivered, or is it just a reporting metric?

   Both. A low EMQ doesn't just make your reporting look worse. It directly weakens Meta's ability to optimize delivery, build lookalikes, and retarget accurately. Treat it as a delivery problem, not a dashboard problem.

   
   

4. Can I improve my EMQ without setting up CAPI?

   Only marginally. Pixel-only tracking caps out fast, especially post-iOS 14.5. CAPI lets you send first-party data directly from your server, which is where most of the real EMQ gains come from. You can clean up Pixel parameters in the meantime, but don't expect a dramatic shift without server-side tracking in place.

   
   

5. How fast will I see EMQ improve after making changes?

   Some changes, like fixing email validation, can shift your score within days. Other changes like rebuilding CRM data hygiene or rolling out a sunset policy take months to fully show up, since they're cleaning up accumulated mess rather than fixing a single broken field.

   
   

6. Does sending more parameters always raise my EMQ?

   Not automatically. Sending more fields helps only if the data is accurate and properly formatted. Sending unvalidated or stale data alongside your good fields can actually drag your score down rather than up, which is why validation comes before volume.

   
   

7. Is external id required to get a high EMQ score?

   No, it's not required, but it helps more than almost any other single field, especially for brands whose customers don't consistently provide the same email or phone number across orders. If you already have stable internal customer IDs, there's little reason not to send it.

   
   

8. Does GDPR limit how much customer data I can send to Meta?

   It limits what you can send without a lawful basis — consent or legitimate interest — not what you can technically send. If your consent management setup is solid, GDPR compliance and a strong EMQ aren't in tension with each other.

   
   

9. What's the difference between EMQ and attribution match rate?

   EMQ measures how well Meta can identify the person behind an event. Attribution match rate measures how well Meta can connect that event to a specific ad or campaign. A high EMQ generally improves attribution, but they're measuring two different steps in the same pipeline.

   
   

10. Should a small D2C brand with low ad spend even worry about EMQ?

    Yes, arguably more than larger brands. Smaller advertisers have less data volume for Meta's algorithm to learn from, so every matched event carries more weight. A weak EMQ on a small budget compound fast, since there's less room for the algorithm to recover from bad signals.