Usecases
Usecases
Back to blogs
Tutorials
How to Master Meta Event Match Quality (EMQ) for Better Ad Performance
By
Abhimanyu Atri
Marketing Product Manager
1 min read
TLDR
Event Match Quality (EMQ) is Meta’s 1-to-10 score for how well your conversion data matches real Facebook and Instagram users.
Meta recommends a score of 6 or higher for strong ad performance.
You raise your EMQ by sending complete, correctly formatted, hashed identifiers like email and phone number through the Meta Conversion API, and by combining data from every channel you collect it on.
Normalizing your data before you hash it, eliminating duplicate pixel and server events, and keeping your event timestamps accurate are the quickest ways to improve your EMQ.
Performance marketers face a growing data problem. Third-party cookies are disappearing, and privacy regulations like GDPR and CCPA keep getting stricter. Many advertisers respond by adopting server-side tracking tools like Meta’s Conversion API (CAPI). CAPI bypasses ad blockers and third-party cookie restrictions by sending the tracking information directly from the website to the advertiser, while preserving the customer's privacy.
But CAPI alone won’t maximize your ad performance. Event Match Quality, or EMQ, is the number that determines the value of this data.
What is CAPI and event match quality (EMQ)?
When a customer clicks “Purchase” on your ecommerce site, your Meta Pixel or Conversion API sends that event data, including details like email or phone number, to Meta. Meta compares this data against its own user database and scores how closely the two match. That score is Event Match Quality, and it runs on a scale from 1 to 10. A high EMQ score means your data includes enough identifying detail, such as email and phone number, for Meta to confidently connect your events to real users.
A higher score improves your ad targeting, sharpens attribution, and helps you optimize campaigns more effectively. It boosts return on ad spend (ROAS) and lowers cost per acquisition (CPA). A low score does the opposite. It cripples your ability to retarget and limits how well you can optimize toward the right audiences.
How does the scoring system work?
Meta rates EMQ on a 1-to-10 scale and recommends aiming for at least a 6 to achieve strong ad performance. The score depends on the identifiers you send. Email, phone number, name, city, state, ZIP code, and advanced parameters like gender or date of birth all factor in.
Meta primarily relies on deterministic matching, where it compares your hashed user data against hashed data already in its system and looks for an exact match. When an exact match isn’t possible, Meta falls back on probabilistic matching, which uses partial data points to estimate a connection instead.
Why does EMQ matter for your ad performance?
Sending conversion data doesn’t guarantee good results. The quality of that data determines how much it actually helps you, and it shapes your advertising outcomes in four distinct ways:
Meta’s machine learning models depend on high-quality data to build lookalike audiences, spot high-intent users, and optimize ad delivery. When your EMQ rises, more complete and accurate signals feed those models, which lowers your CPA and boosts your ROAS.
A higher EMQ also sharpens attribution. Meta connects conversions to the right campaigns and creative assets with more confidence, and that clarity helps you make smarter decisions about budget and strategy.
Low EMQ creates unmatched events that Meta simply can’t connect to real users, and every unmatched event is a missed opportunity for optimization and remarketing. A high EMQ minimizes that data loss and gives you a fuller picture of how your campaigns actually perform.
Most advertisers have adopted CAPI or similar server-side tools by now, but few take the extra step of actively improving their EMQ. That gap creates a real competitive advantage for anyone willing to push past Meta’s recommended baseline of 6.
How does EMQ work inside Meta’s conversion API (CAPI)?
Meta’s Conversion API transfers data directly from your server to Meta’s, which bypasses the limits of client-side tracking, like cookie restrictions and ad blockers. You can read our detailed blog on CAPI to understand how it works. CAPI strengthens your EMQ score in a few specific ways:
CAPI hashes your user data with SHA-256 and transmits it securely, which reduces the risk of corruption or blocking from client-side restrictions. It also consolidates data from your web, app, and offline sources into one unified view of user behavior, so Meta can match events across multiple touchpoints instead of just one. When you use a consistent identifier, like the same email address online and offline, Meta matches events more accurately.
CAPI can also eliminates duplicate events if you send the same event_id from both the pixel and the server. If Meta receives the same purchase from both your pixel and your server, it has to recognize them as a single occurrence, or your conversion counts will inflate, and your data will lose accuracy. High-quality match data also lets you build sharper retargeting lists, like shoppers who abandoned a cart or bought something recently, and those audiences consistently outperform broader targeting.
What are the core elements affecting EMQ?
A handful of factors determine how high your EMQ score climbs.
Data consistency and formatting come first. Convert every email to lowercase, strip out spaces, and include country codes on phone numbers before you hash anything, since Meta’s recommended SHA-256 method only works reliably on clean, consistent input.
Volume and quality of identifiers matter just as much. The more data points you send, the better your match rate gets. Combining an email with a phone number, name, or ZIP code increases your odds of a successful match, and pulling in omnichannel data, like an email from a newsletter signup paired with a phone number from your loyalty program, further increases them.
Timestamp accuracy plays a quieter but critical role. If your event timestamp doesn’t align with when the action actually happened, your match rate drops, so send events promptly and stamp them correctly.
Platform-specific strategies matter too. Mobile app events match better when you include an advertising ID, and offline conversions need CRM data formatted the way Meta expects.
Privacy compliance ties everything together. GDPR and CCPA require clear opt-ins before you collect or share user data and skipping that step doesn’t just create legal risk. It also means Meta may filter that data out entirely if the user never consented.
How does Meta match events to a real customer?
Once you send event data, Meta has to connect it to an actual person in its system. Here’s how that matching actually works:
Meta relies primarily on deterministic matching, which looks for an exact connection between the hashed identifiers you send, and the hashed data already stored in its user database. Once your server hashes an identifier like email or phone number, Meta checks whether that hash matches a hashed version of the same information on file. Formatting matters enormously here. Trim spaces, lowercase every letter, and strip special characters before you hash anything, because even a small mismatch can break the match. Phone numbers need a country code and no dashes or parentheses.
When deterministic matching fails, usually because an email or phone number is missing or wrong, Meta turns to probabilistic matching instead. This method compares multiple partial data points, like first name, last name, ZIP code, city, and date of birth, to estimate a connection even without a primary identifier. It’s a less common path than deterministic matching but sending secondary identifiers consistently can still meaningfully boost your match rate. Data completeness matters here too. A partial address drags your match odds down fast.
Cross-device behavior adds another layer. Meta already knows when a single person logs into Facebook from both a desktop browser and a mobile app, so when you send an event with a mobile device ID, like an IDFA on iOS or AAID on Android, Meta can map it back to that person’s profile. If your data strategy includes a unified internal ID, like a loyalty program or CRM ID, and you also send that ID to Meta, it can link events across channels to the same user and raise your match probability even further.
Timing matters just as much as identity. Meta uses a lookback window to connect an event’s timestamp to a person’s historical activity. If someone visited your site 15 days ago and you send a purchase event with a timestamp that lines up with that visit, Meta can still make the match. Send events promptly with accurate timestamps, or you risk falling outside that window entirely.
Login status changes your odds too. Events tied to a logged-in user, especially one who signs in with the same email they use on Facebook, tend to match more reliably. Guest checkouts are riskier, since minimal or mistyped data is common, so form validation on guest checkout fields helps close that gap.
What are the most common EMQ challenges and how do you fix them?
Even a solid EMQ strategy runs into predictable problems. Here’s how to handle the most common ones:
Privacy and consent issues come up constantly as GDPR and CCPA keep evolving. Without explicit consent, you can’t legally or ethically use a user’s data for matching, and in some cases, a lack of consent gets your data blocked or removed from your feed before it even reaches Meta, which drags your EMQ down.
Incomplete data is just as common. A single identifier, like an email alone, often isn’t enough for an accurate match, especially when a customer uses multiple addresses across different accounts. Capture more than one data point wherever you can, through forms, your CRM, and any loyalty program you run.
Formatting errors quietly kill match rates. A missing country code or a typo like “gmail.con” can knock out a match entirely, so run your data through a validation tool both when you collect it and again right before you send it to Meta.
Technical misconfigurations, like duplicated events or incorrect parameters in your CAPI setup, cause similar damage. Test your events regularly with Meta’s Test Events tool so you can confirm your server sends the right parameters in real time.
Relying on a single data source, like just your website pixel or just your email list, limits what you can see. Combine multiple sources, like in-store, mobile app, and offline CRM data, to meaningfully improve your match rate, even though it takes more thoughtful setup to unify it all.
How do you start improving your EMQ score today?
Optimizing your EMQ isn’t optional if you want to get the most out of Meta advertising. Better data collection, smarter use of CAPI, and consistent privacy compliance all work together to push your score up and unlock stronger targeting, attribution, and optimization.
Start with an EMQ audit. Open Meta’s Events Manager, check your current score, and flag where it’s weakest. From there, refine your data collection by tightening up your forms, your CRM, and your checkout flow so you capture clean, detailed identifiers every time. Confirm your CAPI setup hashes data correctly and doesn’t duplicate events and build in compliance checks so your consent process stays current with GDPR and CCPA.
Set EMQ 6 as your floor, not your ceiling. Once you consistently hit a 6, keep refining your matching process and push toward 7 or higher, where ad performance tends to improve even further.
Frequently asked questions
What is a good Event Match Quality score?
Meta considers 6 or higher a good Event Match Quality score, and scores of 7 or above tend to produce noticeably stronger ad performance.
How do I check my EMQ score in Meta Events Manager?
Open Meta Events Manager, select the pixel or dataset connected to your ad account, and look at the diagnostics panel, where Meta displays your current EMQ score next to each event you’re tracking.
What’s the difference between deterministic and probabilistic matching?
Deterministic matching looks for an exact match between your hashed data and Meta’s stored data, while probabilistic matching estimates a connection using partial identifiers like name, city, and date of birth when an exact match isn’t possible.
Does the Meta Conversion API actually improve my EMQ score?
Yes. The Conversion API improves EMQ by transmitting hashed, secure data directly from your server, consolidating signals across web, app, and offline sources, and eliminating duplicate events that would otherwise distort your match rate.
Why is my EMQ score low even though I’m sending conversion data?
A low score despite active data flow usually points to incomplete identifiers, inconsistent formatting like missing country codes or unhashed fields, misaligned timestamps, or a lack of consent that’s causing Meta to filter your data before it can match.
How does data normalization affect my EMQ score?
Normalizing your data, by lowercasing emails, removing spaces, and formatting phone numbers with a country code before hashing, directly raises your match rate, because even small formatting inconsistencies prevent Meta from recognizing an otherwise exact match.
Can I improve my EMQ score without using the Conversion API?
You can raise your EMQ somewhat through pixel-only improvements like better data collection and normalization, but CAPI consistently produces stronger results because it bypasses the ad blockers and cookie restrictions that limit pixel-only tracking.
How often should I check my EMQ score?
Check your EMQ score weekly while you’re actively optimizing, and at minimum check it monthly afterward, since changes to your checkout flow, CRM, or consent process can shift your score without obvious warning.
Does GDPR or CCPA consent affect my EMQ score?
Yes. Consent affects EMQ directly, because Meta can filter out or block unconsented data before matching even occurs, which lowers your effective match rate regardless of how complete your identifiers are.
Which identifiers should I prioritize sending to Meta first?
Prioritize email and phone number first, since Meta weights these most heavily in deterministic matching, then add name, city, state, and ZIP code as secondary identifiers to support probabilistic matching when the primary identifiers don’t produce an exact match.
Performance marketers face a growing data problem. Third-party cookies are disappearing, and privacy regulations like GDPR and CCPA keep getting stricter. Many advertisers respond by adopting server-side tracking tools like Meta’s Conversion API (CAPI). CAPI bypasses ad blockers and third-party cookie restrictions by sending the tracking information directly from the website to the advertiser, while preserving the customer's privacy.
But CAPI alone won’t maximize your ad performance. Event Match Quality, or EMQ, is the number that determines the value of this data.
What is CAPI and event match quality (EMQ)?
When a customer clicks “Purchase” on your ecommerce site, your Meta Pixel or Conversion API sends that event data, including details like email or phone number, to Meta. Meta compares this data against its own user database and scores how closely the two match. That score is Event Match Quality, and it runs on a scale from 1 to 10. A high EMQ score means your data includes enough identifying detail, such as email and phone number, for Meta to confidently connect your events to real users.
A higher score improves your ad targeting, sharpens attribution, and helps you optimize campaigns more effectively. It boosts return on ad spend (ROAS) and lowers cost per acquisition (CPA). A low score does the opposite. It cripples your ability to retarget and limits how well you can optimize toward the right audiences.
How does the scoring system work?
Meta rates EMQ on a 1-to-10 scale and recommends aiming for at least a 6 to achieve strong ad performance. The score depends on the identifiers you send. Email, phone number, name, city, state, ZIP code, and advanced parameters like gender or date of birth all factor in.
Meta primarily relies on deterministic matching, where it compares your hashed user data against hashed data already in its system and looks for an exact match. When an exact match isn’t possible, Meta falls back on probabilistic matching, which uses partial data points to estimate a connection instead.
Why does EMQ matter for your ad performance?
Sending conversion data doesn’t guarantee good results. The quality of that data determines how much it actually helps you, and it shapes your advertising outcomes in four distinct ways:
Meta’s machine learning models depend on high-quality data to build lookalike audiences, spot high-intent users, and optimize ad delivery. When your EMQ rises, more complete and accurate signals feed those models, which lowers your CPA and boosts your ROAS.
A higher EMQ also sharpens attribution. Meta connects conversions to the right campaigns and creative assets with more confidence, and that clarity helps you make smarter decisions about budget and strategy.
Low EMQ creates unmatched events that Meta simply can’t connect to real users, and every unmatched event is a missed opportunity for optimization and remarketing. A high EMQ minimizes that data loss and gives you a fuller picture of how your campaigns actually perform.
Most advertisers have adopted CAPI or similar server-side tools by now, but few take the extra step of actively improving their EMQ. That gap creates a real competitive advantage for anyone willing to push past Meta’s recommended baseline of 6.
How does EMQ work inside Meta’s conversion API (CAPI)?
Meta’s Conversion API transfers data directly from your server to Meta’s, which bypasses the limits of client-side tracking, like cookie restrictions and ad blockers. You can read our detailed blog on CAPI to understand how it works. CAPI strengthens your EMQ score in a few specific ways:
CAPI hashes your user data with SHA-256 and transmits it securely, which reduces the risk of corruption or blocking from client-side restrictions. It also consolidates data from your web, app, and offline sources into one unified view of user behavior, so Meta can match events across multiple touchpoints instead of just one. When you use a consistent identifier, like the same email address online and offline, Meta matches events more accurately.
CAPI can also eliminates duplicate events if you send the same event_id from both the pixel and the server. If Meta receives the same purchase from both your pixel and your server, it has to recognize them as a single occurrence, or your conversion counts will inflate, and your data will lose accuracy. High-quality match data also lets you build sharper retargeting lists, like shoppers who abandoned a cart or bought something recently, and those audiences consistently outperform broader targeting.
What are the core elements affecting EMQ?
A handful of factors determine how high your EMQ score climbs.
Data consistency and formatting come first. Convert every email to lowercase, strip out spaces, and include country codes on phone numbers before you hash anything, since Meta’s recommended SHA-256 method only works reliably on clean, consistent input.
Volume and quality of identifiers matter just as much. The more data points you send, the better your match rate gets. Combining an email with a phone number, name, or ZIP code increases your odds of a successful match, and pulling in omnichannel data, like an email from a newsletter signup paired with a phone number from your loyalty program, further increases them.
Timestamp accuracy plays a quieter but critical role. If your event timestamp doesn’t align with when the action actually happened, your match rate drops, so send events promptly and stamp them correctly.
Platform-specific strategies matter too. Mobile app events match better when you include an advertising ID, and offline conversions need CRM data formatted the way Meta expects.
Privacy compliance ties everything together. GDPR and CCPA require clear opt-ins before you collect or share user data and skipping that step doesn’t just create legal risk. It also means Meta may filter that data out entirely if the user never consented.
How does Meta match events to a real customer?
Once you send event data, Meta has to connect it to an actual person in its system. Here’s how that matching actually works:
Meta relies primarily on deterministic matching, which looks for an exact connection between the hashed identifiers you send, and the hashed data already stored in its user database. Once your server hashes an identifier like email or phone number, Meta checks whether that hash matches a hashed version of the same information on file. Formatting matters enormously here. Trim spaces, lowercase every letter, and strip special characters before you hash anything, because even a small mismatch can break the match. Phone numbers need a country code and no dashes or parentheses.
When deterministic matching fails, usually because an email or phone number is missing or wrong, Meta turns to probabilistic matching instead. This method compares multiple partial data points, like first name, last name, ZIP code, city, and date of birth, to estimate a connection even without a primary identifier. It’s a less common path than deterministic matching but sending secondary identifiers consistently can still meaningfully boost your match rate. Data completeness matters here too. A partial address drags your match odds down fast.
Cross-device behavior adds another layer. Meta already knows when a single person logs into Facebook from both a desktop browser and a mobile app, so when you send an event with a mobile device ID, like an IDFA on iOS or AAID on Android, Meta can map it back to that person’s profile. If your data strategy includes a unified internal ID, like a loyalty program or CRM ID, and you also send that ID to Meta, it can link events across channels to the same user and raise your match probability even further.
Timing matters just as much as identity. Meta uses a lookback window to connect an event’s timestamp to a person’s historical activity. If someone visited your site 15 days ago and you send a purchase event with a timestamp that lines up with that visit, Meta can still make the match. Send events promptly with accurate timestamps, or you risk falling outside that window entirely.
Login status changes your odds too. Events tied to a logged-in user, especially one who signs in with the same email they use on Facebook, tend to match more reliably. Guest checkouts are riskier, since minimal or mistyped data is common, so form validation on guest checkout fields helps close that gap.
What are the most common EMQ challenges and how do you fix them?
Even a solid EMQ strategy runs into predictable problems. Here’s how to handle the most common ones:
Privacy and consent issues come up constantly as GDPR and CCPA keep evolving. Without explicit consent, you can’t legally or ethically use a user’s data for matching, and in some cases, a lack of consent gets your data blocked or removed from your feed before it even reaches Meta, which drags your EMQ down.
Incomplete data is just as common. A single identifier, like an email alone, often isn’t enough for an accurate match, especially when a customer uses multiple addresses across different accounts. Capture more than one data point wherever you can, through forms, your CRM, and any loyalty program you run.
Formatting errors quietly kill match rates. A missing country code or a typo like “gmail.con” can knock out a match entirely, so run your data through a validation tool both when you collect it and again right before you send it to Meta.
Technical misconfigurations, like duplicated events or incorrect parameters in your CAPI setup, cause similar damage. Test your events regularly with Meta’s Test Events tool so you can confirm your server sends the right parameters in real time.
Relying on a single data source, like just your website pixel or just your email list, limits what you can see. Combine multiple sources, like in-store, mobile app, and offline CRM data, to meaningfully improve your match rate, even though it takes more thoughtful setup to unify it all.
How do you start improving your EMQ score today?
Optimizing your EMQ isn’t optional if you want to get the most out of Meta advertising. Better data collection, smarter use of CAPI, and consistent privacy compliance all work together to push your score up and unlock stronger targeting, attribution, and optimization.
Start with an EMQ audit. Open Meta’s Events Manager, check your current score, and flag where it’s weakest. From there, refine your data collection by tightening up your forms, your CRM, and your checkout flow so you capture clean, detailed identifiers every time. Confirm your CAPI setup hashes data correctly and doesn’t duplicate events and build in compliance checks so your consent process stays current with GDPR and CCPA.
Set EMQ 6 as your floor, not your ceiling. Once you consistently hit a 6, keep refining your matching process and push toward 7 or higher, where ad performance tends to improve even further.
Frequently asked questions
What is a good Event Match Quality score?
Meta considers 6 or higher a good Event Match Quality score, and scores of 7 or above tend to produce noticeably stronger ad performance.
How do I check my EMQ score in Meta Events Manager?
Open Meta Events Manager, select the pixel or dataset connected to your ad account, and look at the diagnostics panel, where Meta displays your current EMQ score next to each event you’re tracking.
What’s the difference between deterministic and probabilistic matching?
Deterministic matching looks for an exact match between your hashed data and Meta’s stored data, while probabilistic matching estimates a connection using partial identifiers like name, city, and date of birth when an exact match isn’t possible.
Does the Meta Conversion API actually improve my EMQ score?
Yes. The Conversion API improves EMQ by transmitting hashed, secure data directly from your server, consolidating signals across web, app, and offline sources, and eliminating duplicate events that would otherwise distort your match rate.
Why is my EMQ score low even though I’m sending conversion data?
A low score despite active data flow usually points to incomplete identifiers, inconsistent formatting like missing country codes or unhashed fields, misaligned timestamps, or a lack of consent that’s causing Meta to filter your data before it can match.
How does data normalization affect my EMQ score?
Normalizing your data, by lowercasing emails, removing spaces, and formatting phone numbers with a country code before hashing, directly raises your match rate, because even small formatting inconsistencies prevent Meta from recognizing an otherwise exact match.
Can I improve my EMQ score without using the Conversion API?
You can raise your EMQ somewhat through pixel-only improvements like better data collection and normalization, but CAPI consistently produces stronger results because it bypasses the ad blockers and cookie restrictions that limit pixel-only tracking.
How often should I check my EMQ score?
Check your EMQ score weekly while you’re actively optimizing, and at minimum check it monthly afterward, since changes to your checkout flow, CRM, or consent process can shift your score without obvious warning.
Does GDPR or CCPA consent affect my EMQ score?
Yes. Consent affects EMQ directly, because Meta can filter out or block unconsented data before matching even occurs, which lowers your effective match rate regardless of how complete your identifiers are.
Which identifiers should I prioritize sending to Meta first?
Prioritize email and phone number first, since Meta weights these most heavily in deterministic matching, then add name, city, state, and ZIP code as secondary identifiers to support probabilistic matching when the primary identifiers don’t produce an exact match.
Share:
Share:
Abhimanyu Atri
Marketing Product Manager
Marketing Product Manager at Attryb, Abhimanyu is the newest addition to the team. A passionate marketer, he helps clients improve the performance of their campaigns and achieve their goals. He's also an avid gamer.
Boost Sales Now
Join the leading D2C brands leveraging Attryb to deliver personalized experiences that drive measurable growth
Boost Sales Now
Join the leading D2C brands leveraging Attryb to deliver personalized experiences that drive measurable growth
Boost Sales Now
Join the leading D2C brands leveraging Attryb to deliver personalized experiences that drive measurable growth
