What event quality score measures and why it matters
Event quality score is the rating ad platforms assign to your conversion events based on how completely and accurately they can connect each event to a real user in their system. The higher the score, the more useful your data is to the platform's algorithm. The lower it is, the less the platform can learn from the conversions you're sending.
Meta calls it Event Match Quality (EMQ) and scores it from 0 to 10. Other platforms use different names but the same underlying logic: TikTok measures it through event quality diagnostics in Events Manager, Snap surfaces it through match rate and signal diagnostics, and Google evaluates it through enhanced conversion coverage and diagnostic reporting. The term varies. The concept does not.
Most brands check this metric infrequently, if at all. That's a problem because a low event quality score doesn't fail loudly. Your campaigns keep running. Conversions keep reporting. But the platform is making targeting and budget decisions based on an incomplete picture of who your buyers actually are.
It's a problem that compounds quietly. Journify monitors event quality scores continuously across Meta, TikTok, Snap, Google, and Amazon for every brand it works with, flagging drops before they affect campaign performance.
Event quality score vs match rate: what's the difference
These two metrics are related but they measure different things. Getting them confused leads to fixing the wrong problem.
Match rate is the percentage of conversion events an ad platform can successfully connect to a real user in its system. It's expressed as a percentage: 60% match rate means 4 in 10 purchase events arrived but could not be matched to anyone. Match rate is a volume metric: it tells you how many events were usable.
Event quality score measures the confidence of each individual match. It's a quality metric: it tells you how well the events that did get matched were matched. A high match rate with a low event quality score means many events arrived but the platform is not very confident about who they belong to. The matches are weak.
You need both to be healthy. A high match rate with a low event quality score still limits what the algorithm can learn. A high event quality score on a low match rate means the events that arrive are well matched, but too few are arriving to give the algorithm enough signal. The right diagnostic is to check both together, not one in isolation.
On Meta, both are visible in Events Manager under the same event type view. On TikTok and Snap, they are surfaced separately: match rate appears in platform diagnostics and event quality is flagged per event type. Treating them as the same metric is the most common signal quality mistake performance teams make.
How ad platforms calculate event quality
When a conversion event arrives at an ad platform, the platform tries to match it to a known user in its system. It does this using identifiers included with the event: hashed email, hashed phone number, name, IP address, browser ID, click ID, and others.
The more complete and accurate those identifiers are, the more confidently the platform can make the match. Confidence in the match translates directly to a higher event quality score.
On Meta, a score of 0 to 5 means weak matching. The platform received the event but couldn't reliably connect it to a user. A score of 6 to 7 is acceptable. A score of 8 or above means the platform can use that event for targeting, optimization, and attribution with high confidence. Default pixel-only setups typically land between 3 and 6. Implementations with enriched server-side tracking consistently reach 7 to 9.
On TikTok, the equivalent signal is event match quality rated across a similar spectrum. The platform evaluates whether events include the identifiers it needs to connect a conversion to a TikTok user. On Snap, match rate is the primary diagnostic: events that arrive without hashed email or phone match poorly, and Snap's algorithm optimizes less effectively as a result.
The platform doesn't tell you when quality is low. It just optimizes on whatever it can see.
Why event quality score drops
Three things drive low event quality scores across every platform.
Missing identifiers. The most common cause. Your event fires, but the customer parameters sent with it are sparse. A purchase event with only an IP address and browser ID scores significantly lower than one that includes hashed email, hashed phone, name, and a click ID. The data exists somewhere in your system. It's not reaching the platform.
Browser-side tracking gaps. Pixels fire from the browser. Ad blockers, iOS restrictions, and Safari's cookie limits mean a meaningful share of those events either don't fire at all or fire with reduced data. An event that doesn't arrive can't have a quality score. An event that arrives with stripped identifiers scores poorly.
Deduplication failures. When you run both a pixel and a server-side Conversions API simultaneously, the same event can reach the platform twice. Platforms handle this through deduplication logic, but it requires a consistent event ID sent through both channels. When deduplication breaks, the platform receives duplicate signals, which distorts optimization and can suppress quality scores on specific event types.
What happens when event quality is low
Low event quality score has two direct consequences.
The first is weaker targeting. Ad platforms use conversion data to find buyers who look like existing customers. When events match poorly, the platform builds lookalike audiences from an incomplete picture. It finds people who resemble the subset of buyers it could identify, not your actual customer base.
The second is slower and less stable optimization. Platforms like Meta need roughly 50 conversion events per week in the learning phase to exit it efficiently. But the count that matters is matched events, not total events. If your event quality is low, a portion of the conversions you send don't count toward that threshold because the platform can't verify who they belong to. Learning phases extend. ROAS becomes harder to stabilize.
The campaigns look fine. The problem is invisible unless you check.
How to check your event quality score
On Meta: Open Events Manager, select your pixel, and click on an individual event type such as Purchase. You'll see the Event Match Quality score and a breakdown of which customer parameters are present and which are missing. This is the fastest diagnostic available.
On TikTok: Open TikTok Events Manager and navigate to your event overview. TikTok surfaces signal quality metrics per event type and flags which parameters are missing or formatted incorrectly.
On Snap: In Snap Ads Manager, navigate to Events Manager and review match rate diagnostics. Snap shows the percentage of events it could match to a Snap user and the parameters contributing to or limiting that match rate.
On Google: In Google Ads, check enhanced conversion coverage under your conversion actions. Google also surfaces diagnostics in the tag diagnostics section that flag whether events are arriving with the data they need.
How to improve event quality score
Three changes move event quality scores consistently.
Switch to server-side event delivery. Pixels depend on the browser. Server-side delivery via Conversions API sends events from your server directly to the platform, bypassing browser restrictions entirely. Events that were previously blocked or degraded by ad blockers and iOS privacy settings now arrive complete. This is the structural fix that affects every other metric downstream.
Send more customer parameters with each event. The goal is to include as many verified identifiers as your system has available: hashed email, hashed phone, external user ID, first name, last name, city, and country. Not all of these carry equal weight. Email and phone have the most impact on Meta and Snap. But each additional parameter improves the platform's ability to make a confident match. Parameters must be hashed correctly before sending.
Fix your deduplication setup. If you run both a pixel and a Conversions API, every event needs a consistent event ID passed through both channels. Meta, TikTok, and Snap all use this ID to identify and suppress duplicate events. Without it, the same purchase can reach the platform twice, which skews reported conversions and can trigger quality issues on specific event types. Check Events Manager for any events flagged as potentially duplicated. Learn more about event deduplication and why it matters.
Event quality score is a leading indicator, not a lagging one
ROAS, CPA, and conversion volume are outcomes. Event quality score is an input. Improving it doesn't require changing your campaigns, your creative, or your audiences. It requires that your conversion data arrives at the platform complete enough to be usable.
Journify monitors event quality scores across Meta, TikTok, Snap, Google, and Amazon for every brand it works with. When scores drop, the platform flags the specific event types and missing parameters behind the decline. The 80+ brands on Journify's signal infrastructure see event quality scores validated before delivery, not discovered after ROAS has already moved. If your scores aren't something you check regularly, start there before touching anything else in your account. Learn more about match rate and how to improve your Meta match rate.
