Meta Event Match Quality Is Low: What Data Should You Check?
A low Event Match Quality score means Meta is not receiving enough recognizable customer information to match your events to users. The score reflects the data in your events, not a setting you can flip. Improving it means sending more matching data, but only data you are permitted to collect and send.
Table of Contents
- 01.What Event Match Quality measures
- 02.What to check first
- 03.Customer information parameters
- 04.Browser vs server data
- 05.Consent and what you may collect
- 06.Data formatting
- 07.How to test it
What Event Match Quality measures
Event Match Quality describes how well the customer information in your events can be matched to Meta accounts. More matching data means a higher score and better optimization. The score is a reflection of the data you send, not a separate configuration. You improve it by improving the data, where you lawfully can.
What to check first
- Identify which customer information parameters you currently send.
- Check whether email or phone is available and correctly formatted.
- Confirm whether external IDs or browser identifiers are available to you.
- Review consent and what data you are permitted to collect and send.
- Compare browser event data with server event data, since server can carry more.
Customer information parameters
The parameters that affect matching include customer email, phone, external ID and browser identifiers where available. Email and phone are the most common. The data must be formatted correctly, typically normalized and hashed where required by the implementation. Sending a parameter is not enough, it must be in the format Meta expects.
Browser vs server data
Server events can carry more customer data than browser events in many setups, because the server has access to information the browser does not. This is one reason CAPI often improves match quality. If your browser events have low match quality, check whether your server events carry more data. The guide on Meta browser and server events not matching covers how the two can differ.
Consent and what you may collect
You should only collect and send data you are permitted to collect with appropriate consent and lawful basis. Adding every possible parameter is not always appropriate, and you should not collect data the business is not entitled to. Match quality must be improved within the bounds of what the user has consented to and what you are allowed to process. Do not bypass consent to raise a score.
Data formatting
Correctly formatted data matches better than raw data. Email should be normalized, typically trimmed and lowercased, before hashing where hashing is used. Phone should include the country code in a consistent format. Badly formatted data that is technically present can still fail to match, so formatting matters as much as presence.
How to test it
- 1.Review which parameters you currently send on browser and server events.
- 2.Confirm the data is correctly formatted and hashed where required.
- 3.Add parameters you are permitted to collect, one at a time.
- 4.Run test events and check whether match quality improves.
- 5.Confirm no change sends data without appropriate consent.
Frequently Asked Questions
What is a good Event Match Quality score?
There is no single threshold that applies to every account, and scores depend on the data available and the implementation. Focus on sending correctly formatted data you are permitted to collect rather than chasing a specific number.
Should I send every possible parameter to improve match quality?
Not necessarily. Only send data you are permitted to collect with appropriate consent and lawful basis. Adding parameters you are not entitled to collect is not appropriate, even if it would raise the score.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Meta CAPI User Data Missing: How It Can Affect Event Matching
Missing user data you are permitted to collect is a fixable gap. Send the data you lawfully can, correctly formatted. Never send data without appropriate consent or fabricate unavailable data.
Meta Browser Events and Server Events Do Not Match: How to Audit the Difference
Browser and server counts will not always be identical because the paths face different restrictions. Find unexpected differences, confirm event names and deduplication, then investigate.
Meta Events Manager Shows Warnings or Diagnostics: What to Check Before Changing Your Setup
A diagnostic describes the state of your data, not a command to rebuild your setup. Match the warning to the right part of your implementation before you change anything.