A Meta CAPI event quality score tells you how well Meta can match the events you send through the Conversions API to actual Facebook or Instagram users. When that score is low, campaigns can look healthy on the surface, budget spending, ads delivering, reports generating, while attribution quietly falls apart underneath. Agencies often notice this only after a client asks why cost per acquisition has crept up despite no changes to creative or targeting. Understanding what the score measures, and what actually moves it, is the difference between guessing at fixes and making targeted improvements that protect both performance and client trust.
What Meta's Event Quality Score Actually Measures
Meta's event quality score, as of 2026, appears in Events Manager as either a numeric rating or a label such as Good, Great, or Low, depending on which part of the interface you're viewing. At its core, it measures how well the parameters attached to an event, things like email, phone number, and external ID, allow Meta to match that event to a known user profile. A high score means Meta is confident it correctly identified the person behind the conversion. A low score means Meta is essentially guessing, which weakens everything downstream: attribution, optimization, and reporting.
You'll find this score inside Events Manager under your Data Sources, specifically in the Conversions API or Diagnostics tab tied to each dataset. Importantly, the score isn't a single account-wide number. It's calculated per event type, so your Purchase events might score well while your Lead or ViewContent events score poorly, especially if those events fire from different parts of a site or app with inconsistent data collection.
One misconception worth clearing up early: CAPI event quality score is not the same thing as Event Match Quality (EMQ), the metric associated with browser-based Pixel tracking. EMQ evaluates matching for events sent directly from a user's browser. CAPI event quality evaluates server-side submissions, which come with their own parameter requirements and weighting because the data arrives without the browser context a Pixel naturally captures. Agencies that assume improving one automatically improves the other often end up troubleshooting the wrong system. If your Pixel EMQ looks fine but a client's CAPI score is low, the fix lives in your server-side event payload, not your website tracking code.
Why a Low Score Hurts Attribution and Ad Spend
When Meta can't confidently match a conversion event to a real user, it loses signal it needs to optimize delivery. The ad algorithm relies on accurate conversion data to learn which audiences, placements, and creative variations are actually driving results. Poor matching doesn't just create a reporting gap, it degrades the learning phase itself, often pushing campaigns toward broader, less efficient audiences because the system has less precise information to narrow in on.
For agencies managing client ad accounts, this tends to surface as a slow, frustrating pattern: cost per acquisition climbs, return on ad spend softens, and clients start questioning whether the offer or creative is the problem. In many cases, neither has changed. The underlying issue is that Meta simply isn't receiving clean, matchable event data, so it's optimizing on incomplete information.
It's worth being precise about what Meta has and hasn't confirmed publicly. Meta has not published an exact formula describing how much weight event quality carries in ad delivery decisions, so treat the relationship as a strong, observable correlation rather than a guaranteed lever you can pull to fix performance overnight. The practical approach is to check event quality alongside performance metrics like CPA and ROAS for each client, and treat a dropping score as an early warning sign worth investigating, not as a metric to chase in isolation. When you see both decline together, event quality is usually a meaningful contributing factor.
The Parameters That Move Your Score the Most
According to Meta's own Conversions API documentation, certain parameters carry significantly more matching weight than others. Hashed email address and phone number sit at the top, since these are stable identifiers Meta can match with high confidence against its user graph. External ID, a unique identifier from your own system such as a customer or order ID, along with the fbp and fbc browser cookies, round out the parameters that most reliably lift your score.
Every one of these personal identifiers needs to be hashed using SHA-256 before it's sent to Meta. This isn't optional, it's a requirement for both privacy compliance and proper matching. In practice, most agencies won't be hashing this manually. A properly configured server-side setup, or a Conversions API Gateway, handles the hashing automatically as part of the event pipeline, which reduces the risk of sending malformed or incorrectly formatted data that Meta then discounts or discards.
Consider two versions of the same e-commerce client. One sends only the fbp cookie with each Purchase event, relying entirely on browser-based identifiers passed through to the server. The other adds hashed customer email and phone number captured at checkout, alongside the same fbp and fbc values. The second setup will typically show a noticeably higher event quality score, because Meta now has multiple independent signals to cross-reference rather than a single browser cookie that can be blocked, cleared, or missing entirely on certain devices. This is also why mobile-heavy campaigns, where cookie persistence is less reliable, tend to benefit the most from adding hashed contact parameters.
The practical takeaway is simple: audit what your checkout, form, or lead capture flow actually passes into your CAPI payload. If email and phone are being collected on the front end but not mapped into the server-side event, you're leaving your highest-weighted parameters unused.
How to Check and Track Your Score Across Multiple Client Accounts
Checking a single client's event quality score is straightforward. Go into Events Manager, select Data Sources, choose the relevant dataset, and open the Diagnostics or Overview tab. From there you can see the score broken down by event type, along with which parameters are present and which are missing or incomplete for each one.
The friction shows up at scale. If you're running Meta ads for ten, fifteen, or twenty client accounts, manually logging into each Business Manager weekly to check this one metric is tedious, and it's exactly the kind of task that gets skipped once things get busy. A score can quietly drop after a client's developer changes their checkout flow or a CRM migration breaks a form integration, and without a regular check, weeks can pass before anyone notices the CPA creep tied back to it.
This is where centralized visibility matters more than any single fix. Tools built for agencies, like ClientPlug, pull Meta Ads performance and CAPI health data into one dashboard, so you can scan for a client whose event quality has slipped without opening each Business Manager individually. Instead of treating event quality checks as a separate manual chore, it becomes part of the same view where you're already tracking spend, campaign performance, and client payments. For agencies managing many accounts, that consolidation is often the difference between catching a data problem in week one versus explaining a CPA spike to a client in week four.
Common Setup Mistakes That Tank Event Quality
The most frequent issue agencies run into is duplicate events, where the same conversion fires from both the Pixel and the CAPI without proper deduplication. Meta deduplicates using a matching event_id sent from both sources for the same event. When that ID is missing or inconsistent, Meta doesn't just double-count the conversion, it also has a harder time confidently matching either version to a user, which drags the quality score down rather than simply inflating your numbers.
Timing is another common culprit. Meta recommends sending CAPI events as close to real-time as possible. Events sent with significant delay, batched hours later from a backend job, for instance, reduce Meta's confidence in the match because the browsing session context has aged or expired. If your server-side integration queues events and sends them in bulk overnight, that lag is likely showing up as a lower score even if every parameter is technically present.
The third mistake is skipping validation before launch. Meta's Conversions API Gateway and Test Events tool exist specifically to catch malformed payloads, missing parameters, and formatting errors before they affect live campaigns. Agencies that push a new client's tracking setup live without testing it often don't discover a broken integration until weeks later, when a client asks why costs are rising. By then, you're troubleshooting retroactively instead of catching the issue at setup.
Each of these mistakes is fixable, but they tend to compound. A client with duplicate events, delayed sends, and an unvalidated setup isn't dealing with one problem, they're dealing with three separate drags on the same score, which makes the eventual fix feel more overwhelming than it needs to be if caught early.
A Practical Checklist to Raise Your Score This Week
Fixing a low event quality score doesn't require rebuilding a client's tracking from scratch. It usually comes down to a focused audit and a few targeted changes:
- Open Events Manager and check the current score for each event type individually, Purchase, Lead, ViewContent, rather than assuming one score applies account-wide.
- Identify which high-value parameters are missing, prioritizing hashed email and phone number if they aren't currently being passed into the CAPI payload.
- Confirm deduplication is working correctly by checking that the same event_id is sent from both Pixel and CAPI for matching events.
- Use Meta's Test Events tool to send sample events and verify the payload is formatted correctly and hashed as expected before assuming the fix worked.
- Recheck the score after a few days of live data, since Meta needs a volume of events to recalculate the rating, not just the next page refresh.
Treat this as a recurring review rather than a one-time fix. A client's website redesign, a new checkout provider, or a CRM swap can silently break parameter mapping that was working fine the month before. Building event quality checks into a regular cadence, monthly at minimum for active clients, catches these regressions before they show up as a CPA problem in a client call.
For agencies handling this across many accounts, ClientPlug's Conversion API setup flow simplifies the parameter mapping and deduplication checks that otherwise require digging through Events Manager settings client by client, making it easier to get new accounts configured correctly the first time and to spot when an existing one drifts.
Treat the Score as an Early Warning System
Event quality score isn't a vanity metric to screenshot for a client report, it's a diagnostic that tells you whether Meta can actually do its job with the data you're sending. A high score doesn't guarantee great performance, but a low one reliably signals that attribution and optimization are working with incomplete information, and that's worth fixing before it shows up as a CPA problem you can't otherwise explain.
Pick one client account today and check its current score in Events Manager. If it's low, walk through the parameters, deduplication, and timing issues covered above before assuming the offer or creative is at fault. Then set up a recurring check-in, whether that's a calendar reminder or a centralized tool like ClientPlug, so the next drop gets caught in week one instead of week four. Learn more about our services.