Meta ads event match quality low: how to improve it
Troubleshooting guide · 2 min read · Updated 2026-10-21 · By the Cofoundr team
Event match quality is Meta's score for how well it can match your events to real people. Raise it by sending more customer information parameters with each event, such as hashed email and phone, and by sending events from the server as well as the browser, de-duplicated. Better matching usually gives the delivery system better data to learn from.
A low score does not break your ads, but it means Meta is matching fewer events to the people who saw your ads, which can weaken optimisation and reporting. The score is shown per event in Events Manager. Meta's definitions and the parameters it lists can change, so use its current documentation alongside this guide.
What it measures
Meta compares the customer information you send with an event, such as email, phone, name, location and browser identifiers, against its own data. The more good parameters that match, the higher the score for that event.
Ways to raise it
- Send hashed email and phone number wherever you collect them, such as at checkout or on a lead form.
- Send the browser identifiers Meta provides, such as the click and browser IDs, with server events.
- Send the customer's IP address and user agent from the server.
- Use an external ID, such as your own customer ID, consistently.
- Check formatting: values must be cleaned and hashed the way Meta requires.
Add server-side events
The Conversions API sends events from your server, so they are not lost to browser limits. Send them alongside the browser pixel and de-duplicate them. See duplicate conversions.
What to do on lead gen and low-data sites
If you cannot collect an email before the event, the score may stay modest. Move the event to the point where you do have the information, or send it from your CRM when the lead is created.
Check after you change it
- Wait for events to accumulate, because scores update with data.
- Compare event counts in Meta with your own records.
- Watch cost per result over the following weeks.
How Cofoundr helps
Cofoundr does not read or change your event setup. What it does is show when results look wrong: the client page warns when the gap between clicks and results suggests tracking may be incomplete, and purchases, revenue and return on ad spend are shown separately from the per-ad-set result. See conversion tracking not matching.
Frequently asked questions
What is a good event match quality score?
Higher is better, and Meta describes the scale in Events Manager. Aim to improve it step by step by adding more customer parameters, rather than chasing a particular number.
Does low event match quality hurt performance?
It can limit how well delivery learns, and it can make reporting less complete. The effect varies by account.
Do I need the Conversions API to improve it?
It is the most reliable way to send extra parameters from the server, so it usually helps. Some improvement is possible from the browser pixel alone.