What is Event Match Quality in Meta Ads?
Event Match Quality is Meta's 0-to-10 score. See what it measures, how it's calculated, and why a high score does not prove the report matches the store.

Event Match Quality is a score from 0 to 10 that Meta calculates from the quality of the customer information sent with a server event and from the percentage of instances of that event it can match to Meta accounts. The score measures that match. It does not prove that the Ads Manager number equals the store's orders.
TL;DR
- Meta calculates the 0-to-10 score for server events, using data from the last 48 hours.
- The score shows how well customer information helps Meta match the event to a Meta account, not whether the store sold that total.
- A high score can sit next to an ads report that still differs from the store, because attribution, date and window remain separate rules.
- Clakta does not send events to Meta and does not change this score.
What is Meta scoring?
In the Help Center, About Event Match Quality describes Event Match Quality as a way to follow the quality of the customer information sent with server events. The score is available for standard and custom web events, such as page view, add to cart and purchase.
The stated goal is to help Meta associate the event with a Meta account. That is a different question from how many orders the store recorded, or how many purchases Ads Manager credited to an ad set. What Is Server-Side Tracking? explains sending events from the server; this page covers only the score Meta calculates on those events.
How is the score calculated?
Meta calculates a score from 0 to 10 based on two points: the quality of the customer information you send for that server event, and the percentage of event instances matched to Meta accounts. Data from the last 48 hours feeds the score, which is why the help page asks you to send events regularly if you want the score to stay up to date.
The same page lists customer information parameters that can travel with the event, through the Pixel or the Conversions API, with a priority order. Email and Click ID appear as high priority. Facebook Login ID, birthdate, country, phone number, External ID and Browser ID appear as medium priority. First name, last name, city and zip or postal code appear as low priority. Meta asks that this data be formatted and hashed, and that you have a lawful basis to collect and share it, under the Meta Business Tools Terms.
View Server Event Details in Meta Events Manager describes where to inspect events sent from the server, including event match quality, in Events Manager.
Does a high score mean sales match the store?
No. The score says how well Meta can match the event to one of its accounts. Ads Manager still applies the attribution window, click-through or view-through credit and the impression date. The store still records the order on the day it was created or paid, with a status.
That is why a high score can sit next to different totals. The event may have arrived with good identifiers and still be credited to an ad the store would not use as the source, or land on another day in the report. The reverse is also true: a lower score does not, by itself, prove that the store sold less.
Meta says better event match quality may result in an increase in additional conversions reported. That is about Meta's reporting, not the list of paid orders. Why Meta Ads sales don't match your store and the overview in Why GA4, Meta, Google Ads and the store don't match cover those other rules.
What helps matching, according to Meta?
The help page itself recommends sending several customer information parameters when they are available, especially the high-priority ones. Specific recommendations appear in Events Manager.
That does not replace a check against the store. Sending more fields improves the chance that Meta can associate the event with an account; it does not redefine what the store counts as a paid, cancelled or refunded order.
When should I look at the score, and when at the store?
Look at the score when the question is "are server events arriving with information Meta can match to an account?". Look at the store when the question is "how many paid orders came in during this period, and what did Meta report alongside them?".
Both questions are useful. They do not have the same answer. Independent attribution tools help with the second. Clakta is one of them: it brings together the numbers Meta reports and the orders the store confirmed, side by side. Revenue comes from those same store orders, with status; each order enters that total once; a pending delayed payment is not revenue yet; refunds and cancellations update the same order.
Clakta does not send events to Meta, does not feed the Conversions API and does not change Event Match Quality. The pixel and the Conversions API, if you use them, stay in place. Clakta runs alongside them, does not change the platform report and does not replace GA4 (What is Clakta?, How attribution works). For stores, see the ecommerce page.
Meta's score and the store's total remain different measures. In Clakta, what the platform reports and what the store recorded appear on the same screen.
Frequently asked questions
Is Event Match Quality the same thing as attribution?
No. The score measures how the event matches a Meta account. Attribution decides which ad Meta credits the conversion to, according to the ad set's window.
How many days of data does the score use?
Meta's help says the last 48 hours of data are used to calculate the scores.
If the score is high, should Ads Manager match the store?
Not necessarily. The window, view-through credit, impression date and order status can still pull the two numbers apart.
Does Clakta improve Event Match Quality?
No. Clakta does not send events to Meta and does not change this score. It shows, side by side, what Meta reports and the store's orders.
Do I need to turn off the Pixel to use Clakta?
No. The pixel and the Conversions API, if they are already on the site, stay in place. Clakta runs alongside them and does not replace those sends.