What is Event Match Quality? Why It Decides Your Ad Performance

The metric most advertisers don't know exists

Every time you send a conversion event to Meta — a purchase, an add-to-cart, a lead form submission — Meta tries to figure out who performed that action. Was it a specific Facebook user? Which ad did they click? Can this conversion be attributed to a campaign?

The answer depends on a metric called Event Match Quality, or EMQ.

EMQ is a score from 0 to 10 that measures how well Meta can match your conversion events to real people on their platform. You can find it in Meta Events Manager, buried under each event type in your pixel or CAPI connection. Most advertisers never look at it. Most advertisers should.

Here's why: EMQ doesn't just affect your reporting — it affects your ad delivery.

When Meta's algorithm receives a conversion event with high match quality, it can confidently attribute that conversion to the ad that drove it. This feedback loop helps the algorithm find more users like the one who converted, improving targeting precision and lowering costs.

When Meta receives an event with low match quality, it can't match the conversion to a user. The algorithm loses a data point. Over time, this means worse targeting, higher CPAs, and campaigns that appear to underperform — even when actual conversions are happening.

---

How EMQ scoring works

Meta calculates EMQ based on the customer data parameters you send with each server-side event. Each parameter has a different matching weight:

High-impact parameters (move the needle most)

Medium-impact parameters

Lower-impact parameters

The key insight: you don't need every parameter to reach a high EMQ. Sending email + _fbp + _fbc consistently is worth far more than sending 15 low-impact parameters inconsistently.

---

Why EMQ directly affects ad performance

EMQ isn't just a data quality metric — it has a real, measurable impact on your ad costs and results.

1. Attribution accuracy

When Meta matches a conversion to a user, that conversion gets attributed to the ad, ad set, and campaign that drove it. Without a match, the conversion still happened, but Meta doesn't know which ad to credit.

This creates a reporting gap. Your actual ROAS might be 4.0x, but if Meta can only match 60% of your conversions, your reported ROAS shows 2.4x. You might scale back a profitable campaign because the numbers look weak — when the real problem is EMQ.

2. Algorithm optimization

Meta's ad delivery algorithm uses conversion data to find more users likely to take the same action. Each matched conversion teaches the algorithm: "this type of user, on this type of placement, at this time of day, converts for this advertiser."

With high EMQ, the algorithm receives dense, accurate feedback. With low EMQ, it's flying partially blind. The result is broader targeting, less efficient spend, and higher CPAs.

3. Audience building

Matched conversions feed into your custom audiences. Low EMQ means your "purchaser" lookalike audience is missing a significant portion of actual purchasers, making the lookalike less precise.

4. Auction competitiveness

During high-competition periods like Black Friday and Cyber Monday, Meta's auction system processes billions of bid requests per day. Advertisers with high EMQ scores provide more optimization signals per dollar spent, which means the algorithm can bid more confidently. The result: better delivery at lower CPMs relative to competitors with lower EMQ.

---

What a low EMQ score actually looks like

Here's a real-world example of how EMQ affects a brand's results:

Brand A: EMQ of 4.2 (pixel-only tracking)

• Sends Purchase events via Meta pixel only
• No hashed email, no _fbp, no _fbc
• Meta matches ~42% of events
• Reported ROAS: 1.8x
• Actual ROAS: 3.1x (but they don't know this)
• Algorithm optimizes on incomplete data
• CPA is 25% higher than necessary

Brand B: EMQ of 8.5 (CAPI with proper parameters)

• Sends Purchase events via both pixel and CAPI
• Includes hashed email, _fbp, _fbc, phone, IP, user agent
• Meta matches ~85% of events
• Reported ROAS: 3.8x
• Actual ROAS: 4.1x (close to reality)
• Algorithm optimizes on rich data
• CPA is optimized to near-theoretical minimum

The difference between these two scenarios isn't creative, targeting, or budget — it's data quality.

---

How to check your EMQ score

1. Go to Meta Events Manager (business.facebook.com/events_manager)
2. Select your pixel or CAPI data source
3. Click on a specific event (Purchase, AddToCart, etc.)
4. Look for the Event Match Quality score under the event details
5. Click into the score to see which parameters are being sent and which are missing

What the scores mean:

The minimum you should aim for: 6.0 for all events, 8.0+ for your Purchase event. If your Purchase EMQ is below 6.0, fixing it should be your highest-priority marketing task.

---

Why browser pixels can't achieve high EMQ

A common misconception: "I have the Meta pixel installed, so my EMQ should be fine."

Browser pixels have fundamental limitations that prevent high EMQ scores:

1. No hashed customer data — The pixel fires on page events but doesn't have access to hashed PII (email, phone) that server-side events can include. Without email, you lose the highest-impact matching parameter.

2. Ad blockers strip the pixel — 30-40% of users use ad blockers that prevent the Meta pixel from loading at all. For those users, EMQ is effectively 0 because no event is sent.

3. iOS restrictions limit cookies — Apple's Intelligent Tracking Prevention limits third-party cookie lifetimes and restricts tracking identifiers. This reduces the reliability of _fbp and _fbc parameters for Safari users.

4. Browser privacy features — Firefox Enhanced Tracking Protection, Chrome's cookie changes, and Brave's aggressive blocking all degrade pixel-based tracking data.

This is why server-side tracking via Conversions API is essential for high EMQ. Server-side events are sent from your server directly to Meta's API, unaffected by browser restrictions. And because they originate from your backend (after a purchase or form submission), you have access to the customer's email, phone, and other matching parameters.

---

The three steps to high EMQ

Step 1: Implement server-side tracking

You cannot reach EMQ 8.0+ with browser pixels alone. Set up Conversions API — either through a managed platform like SignalBridge, through server-side GTM, or through a custom API integration.

The fastest path: SignalBridge connects your store to Meta CAPI in 5 minutes, automatically includes hashed customer data parameters, and handles event deduplication between pixel and server events.

Step 2: Send the right parameters

Focus on the three highest-impact parameters first:

1. Hashed email — SHA-256 hash of the customer's email address. This is available for any event that occurs after a customer provides their email (Add to Cart on Shopify, Begin Checkout, Purchase, etc.).

2. _fbp (Facebook browser ID) — This is a first-party cookie set by the Meta pixel. To include it in your server-side events, you need to read the _fbp cookie value from the customer's browser and pass it to your server when the event fires.

3. _fbc (Facebook click ID) — This is extracted from the fbclid URL parameter that Meta appends when a user clicks an ad. Store this value when the user lands on your site and include it in subsequent server events.

Step 3: Ensure consistency

EMQ is calculated across all events of a given type. If 70% of your Purchase events include hashed email but 30% don't (because some customers check out as guests without providing email), your overall EMQ will be dragged down by the missing 30%.

Strategies to maximize consistency:

• Require email at checkout (most e-commerce platforms do this by default)
• Pass _fbp and _fbc via first-party cookies that persist across sessions
• Use event deduplication to ensure each conversion is only counted once, with the best possible parameter set
• Send additional parameters (phone, name, address) when available — each one adds incremental matching lift

---

EMQ vs other tracking metrics

EMQ vs pixel event count

Your pixel event count tells you how many events fired. EMQ tells you how many of those events Meta can actually use. You could have 10,000 Purchase events but an EMQ of 3.0, meaning Meta can only match 3,000 of them to real users.

EMQ vs conversion attribution window

Your attribution window (7-day click, 1-day view, etc.) determines which ad interactions can receive credit for a conversion. EMQ determines whether the conversion can be matched to a user at all. A 28-day attribution window doesn't help if EMQ is too low to match the event.

EMQ vs ROAS

Your reported ROAS depends directly on how many conversions Meta can attribute to ads. Low EMQ means lower reported ROAS — not because your ads aren't working, but because Meta can't prove they're working. This is why brands often see ROAS jump 15-30% after improving EMQ, without changing anything about their campaigns.

---

How SignalBridge maximizes EMQ automatically

SignalBridge is built specifically to solve the EMQ problem. When you connect your store, SignalBridge automatically:

• Sends hashed email with every conversion event where email is available
• Captures and forwards _fbp and _fbc parameters from the browser to server-side events
• Includes IP address and user agent for additional matching signals
• Hashes phone number when provided by the customer
• Deduplicates events between pixel and CAPI so each conversion is counted once with the best possible parameter set
• Filters bot traffic so non-human events don't dilute your EMQ calculations

Most SignalBridge users see their Purchase EMQ jump from 4-5 (pixel-only) to 8.0+ within 48 hours of connecting.

Start your free trial and watch your EMQ scores improve in real time.

---

FAQ

What is a good Event Match Quality score?

For your Purchase event, aim for 8.0 or higher. For secondary events like AddToCart and ViewContent, 6.0+ is acceptable. Any event below 4.0 needs immediate attention — Meta can barely match those events to real users.

Does EMQ affect Google Ads too?

The term "Event Match Quality" is specific to Meta. However, Google Enhanced Conversions uses a similar concept — hashed customer data sent with conversion events improves Google's ability to attribute conversions and optimize Smart Bidding. The principle is the same: more matching data equals better ad performance.

Can I improve EMQ without server-side tracking?

In theory, you can add some customer data parameters to enhanced pixel events. In practice, browser restrictions, ad blockers, and iOS ITP make it nearly impossible to consistently include the parameters that matter most. Server-side tracking via CAPI is the reliable path to EMQ 8.0+.

How quickly does EMQ improve after implementing CAPI?

EMQ scores typically update within 24-48 hours of sending server-side events with proper parameters. The full impact on ad performance (lower CPAs, better ROAS) takes 2-4 weeks as Meta's algorithm adjusts to the improved data quality.

Does EMQ affect all campaign types equally?

EMQ has the greatest impact on campaigns using conversion-optimized objectives (Purchase, Lead, Add to Cart). Awareness and reach campaigns are less affected because they're optimized for impressions rather than conversion signals. That said, even awareness campaigns benefit from better attribution reporting when EMQ is high.

Is EMQ the same as data quality?

EMQ is one measure of data quality specific to Meta's platform. Broader data quality includes event deduplication, bot filtering, conversion value accuracy, and event parameter completeness. A comprehensive tracking setup like SignalBridge addresses all of these, not just the parameters that affect EMQ scoring.

Why did my EMQ score drop suddenly?

Common causes: a tracking code was removed or broken (check your pixel and CAPI connections), a website update changed how customer data is collected (e.g., a new checkout flow that doesn't pass email), or an increase in anonymous traffic (more guest checkouts without email). Check Meta Events Manager's parameter breakdown to identify which specific parameters stopped being sent.