# Meta Event Match Quality (EMQ) scores explained

When you run ads on Meta, the algorithm needs to match events on your store to actual Facebook users — purchases, add-to-carts, page views. The better that match, the more effectively Meta can optimize delivery, build lookalike audiences, and report accurate ROAS.

Meta uses Event Match Quality (EMQ) to score how well your tracking data matches to Facebook users. It runs from 0 to 10. Higher scores mean Meta can identify more of your customers and put your ads in front of the right people.

### Why EMQ matters

EMQ is one of the most direct signals of CAPI implementation quality. A low score means Meta is working with incomplete data.

The performance difference between a mediocre and a strong score often means:

* Lower cost per acquisition
* Higher customer match rates
* Better ROAS

Scores are calculated in real-time and update based on 24–48 hours of Conversions API data.

### Benchmarks by event type

Not all events are held to the same standard. Purchase events matter most, since they drive the optimization signal for your campaigns.

| Event                            | Target score |
| -------------------------------- | ------------ |
| Purchase                         | 8.5+         |
| Add to Cart / Checkout Initiated | 6.5+         |
| Page View                        | 5.5+         |

{% hint style="warning" %}
A purchase EMQ below 8.0 is a sign that your CAPI implementation is missing key identifiers or relying too heavily on browser-side data.
{% endhint %}

You can check your current scores in Meta Events Manager under **Overview → Event Match Quality**.

### What drives EMQ scores

Three factors determine your score.

#### 1. Data completeness

The more customer identifiers you send with each event, the higher the score. Meta weights these differently:

| Priority | Identifiers                                     |
| -------- | ----------------------------------------------- |
| High     | Email, click ID (`fbc`)                         |
| Medium   | Phone, external ID, browser ID (`fbp`), country |
| Low      | First name, last name, city, postal code        |

Email and click ID (`fbc`) have the most impact. If your setup regularly misses email at purchase events, your score won't reach 8.8+.

#### 2. Processing speed

Real-time server-side events score higher than batched data. Meta expects purchase events to arrive shortly after they occur on your store. Delayed or batched submissions reduce match quality.

#### 3. Event accuracy

Duplicate events or missing events reduce scores. If Meta receives the same purchase event from both browser pixel and server without proper deduplication, it inflates event counts and penalizes match quality.

### How Littledata improves EMQ

Browser-only tracking alone is not enough to consistently maintain a high EMQ score:

* Cookies are blocked or expire, losing the `fbp` and `fbc` identifiers
* Express checkout flows (Shop Pay, Apple Pay) don't fire the pixel reliably
* No server-side enrichment means missing device, IP, and location data

Littledata's server-side connection addresses each of these:

**Captures all purchase events** — Littledata tracks orders through Shopify's server-side data, so express checkout and cookie-blocked sessions don't create gaps.

**Enriches events with more identifiers** — Each event is sent with email, phone (where available), IP address, user agent, and location data, covering all of Meta's high and medium priority identifiers.

**Extends cookie lifetime** — Server-side tracking keeps the `fbp` cookie active for up to one year, compared to 7 days in a standard browser setup. This preserves the `fbc` click ID across longer purchase journeys.

**Deduplicates pixel and CAPI** — Littledata sends a consistent `event_id` with both browser and server events that allows Meta to deduplicate correctly.

**Sends events in real-time** — Events are dispatched as they happen on Shopify.

### Learn more

* [Meta Pixel vs Meta Conversions API](/integrations/facebook-capi/meta-pixel-vs-meta-conversions-api.md) — how the two tracking methods complement each other
* [Why Meta attribution differs from GA4](/integrations/facebook-capi/why-is-meta-attribution-different-from-ga4.md) — understanding what Meta's numbers actually measure
* [Maximize conversion value based on customer LTV](/integrations/facebook-capi/maximize-conversion-value-based-on-ltv.md) — take attribution further with new vs returning customer signals


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.littledata.io/integrations/facebook-capi/meta-event-match-quality.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.