Meta Event Match Quality on Shopify: How to Get to 8 or Higher in 2026

May 20, 2026

TL;DR

Meta's EMQ score sits in your Events Manager and tells you, per event, how well Meta can match what you send to a Meta account [1]. The score is calculated from which customer information parameters arrive in your Conversions API events and how often they successfully match a person. On Shopify, every parameter Meta accepts for web events is sourceable from a completed order, but most stock pixel setups send only a handful. This article walks through every parameter, where Shopify exposes it, and what to verify in Events Manager to know whether you have actually reached 8+ on Purchase.

What Event Match Quality Actually Measures

Meta defines Event Match Quality as a score from 0 to 10 that reflects how effective the customer information you send through Conversions API is at matching event instances to a Meta account [1]. It is calculated in real time, currently only for web events, and shown per event in Events Manager [1].

The score is not a count of how many parameters you send. It is a weighted measure of which parameters arrive, how clean they are, and the match rate Meta sees against its own user graph. Email and phone are the strongest signals because most Meta accounts have one or both verified. Adding external_id and fbc (the click ID parameter) further boosts match confidence on people who originally arrived from a Meta ad.

Third-party benchmarks vary, but a common pattern is that 6 is treated as the floor and 8+ is the working target for the Purchase event. Once Meta can match most of your conversions, additional gains shrink. The point of 8+ on Purchase is not to chase a number, but to make sure bottom-funnel signal is dense enough that automated bidding has clean data to optimize on.

What Customer Information Parameters Move EMQ

Meta accepts a defined list of customer information parameters in the Conversions API user_data object. Each one contributes to the EMQ score for the events that include it.

Meta documents the full parameter list in its Conversions API reference [1]. The parameters fall into three groups: hashed customer PII (email, phone, name, address fields), browser identifiers from Meta's own cookies (the Facebook Browser ID and Facebook Click ID), and request context (the visitor's IP and user-agent). Each one Meta receives strengthens its ability to match the event to a real account. Email and phone carry the heaviest weight because most Meta accounts have one or both verified. A stable customer-side identifier (hashed) further boosts match confidence on shoppers Meta has seen before.

Date of birth and gender are also accepted, but they require explicit collection at checkout, which is not standard on Shopify and which most merchants choose not to add.

Where the Data Lives on Shopify

Every parameter above is sourceable from data Shopify already gathers at the order level. The hashed-PII fields (email, phone, name, address, country) come from the customer's checkout submission and are deterministic on every completed order. The browser identifiers (fbp, fbc) come from cookies set when the visitor lands from a Meta ad. The request fields (client_ip_address, client_user_agent) are captured at the storefront and need to travel with the event when it ships server-side.

What a merchant cares about is not the specific field name on each side. It is whether the tracking layer they install actually wires all of them up. The next two sections cover why most stock setups do not, and what to verify if you suspect yours is missing something.

Why Browser-Only Tracking Caps Your EMQ Below 8

If you run only Shopify's stock Meta Pixel through the Facebook & Instagram channel, Purchase fires from the browser. Meta gets fbp, fbc, client_ip_address, and client_user_agent. It does not get the hashed-PII set in a structured way, because the standard Pixel hits before checkout completion data is fully available client-side and email/phone are typically not exposed without explicit advanced-matching configuration.

In practice, browser-only Shopify Pixel installs land lower EMQ scores on Purchase than the same store would with a server-side CAPI layer reading checkout data. Events without em and ph match at lower rates [1]. The server-side path attaches the full hashed-PII set from the order, which is what pushes Purchase EMQ into the 8+ range.

How to Read Your EMQ Score in Events Manager

Open Events Manager, select your pixel/dataset, and go to the Overview tab. The score appears per event under "Event match quality" with a numerical value 0 to 10 [1]. Click into a specific event (Purchase, AddToCart, etc.) to see which parameters Meta received and what share of events arrived with each parameter present.

What to check on Purchase specifically:

em should be present on close to 100 percent of events. If it is missing, the order webhook is firing without order.email, which almost always means the tracking layer is reading the wrong field or skipping guest checkouts.
ph will be lower than em because not every shopper enters a phone. Coverage tracks whether phone is required or optional at checkout. Partial coverage is normal and not a fix item.
fbp and fbc coverage depends on whether the visitor had cookies at all. Anyone who arrived from a Meta ad in a non-incognito Chrome or Firefox session will have both. Safari ITP and ad-blocked sessions will be missing them.
client_ip_address and client_user_agent should be present on essentially every event when your tracking layer captures them correctly.

If your overall EMQ on Purchase is below 6, look at the parameter coverage breakdown first. If em coverage is below 90 percent, that is almost always the single biggest lift available.

How to Verify Your Tracking Layer Is Actually Wired

Events Manager shows what Meta received, which is the ground truth. To see exactly what your tracking layer is sending, use the Test Events tab. Place a test order with the test event code applied and the Test Events stream shows the full user_data payload Meta saw [2]. Confirm each expected parameter appears, that hashed fields look hashed (not plain text), and that any address fields are normalized correctly. If a parameter is in the payload but Meta cannot use it (wrong format, wrong hash), the EMQ score does not benefit from it.

If something is off, that is a tracking-layer configuration issue, not a Meta-side problem. Either fix the tool you are using or switch to one that handles this correctly out of the box.

What WeltPixel Conversion Tracking Sends on a Shopify Purchase

WeltPixel Conversion Tracking (WCT) populates the full set of customer information parameters Meta accepts on web events when the data is present on the order, on every plan (Explorer free with 100-order cap, and Plus at $39/month unlimited). That covers the strongest matching signals on the order itself, the browser identifiers captured on the storefront, and the request context that Meta uses to verify event provenance. Hashing and normalization follow Meta's documented rules.

For guest checkouts, WCT generates a stable identifier so guest orders do not lose one of Meta's strongest matching signals just because the shopper did not log in.

Refund events forwarded to Meta CAPI are included on the Plus plan. Refund attribution credits back failed conversions, keeping reported ROAS aligned with actual fulfilled revenue.

What to Watch for on Your Own EMQ Score

After the tracking layer is in place, run a few test orders with Meta's test event code applied, then come back to Events Manager Overview 24 hours later. Purchase should sit at 8 or higher. If it does not, the parameter coverage panel in Events Manager will show you which signals are missing or weak across your real traffic.

A score below 6 on Purchase almost always traces back to missing email coverage on the server-side event. Anything in the 6-to-7 range usually means the browser identifiers or request fields are not arriving alongside the order data. A well-configured stack lands 8+ within a day.

Key Takeaways

Event Match Quality (EMQ) is Meta's per-event score from 0 to 10 that reflects how well your Conversions API events match real Meta accounts [1]. Calculated in real time, shown in Events Manager.
The score is weighted, not a count. Hashed email and phone, the browser identifiers from a recent Meta ad click, and a stable customer identifier carry the most weight on web Purchase events.
All of the customer information parameters Meta accepts on web events are sourceable from a completed Shopify order, but a browser-only Pixel install typically delivers only a few of them.
Server-side Conversions API is what unlocks the full set on every Purchase event and pushes the score into the 8+ range.
Use Events Manager's Test Events tab to confirm parameters are arriving in the right format before relying on the score. Configuration changes show up in the Overview number within roughly 24 hours.
On Shopify, refund events forwarded to Meta CAPI are gated to the Plus plan ($39/month). The browser pixel + server-side CAPI baseline is available on every plan (Explorer free with 100-order cap, and Plus).
Running the official Facebook & Instagram channel alongside a server-side integration like WeltPixel Conversion Tracking is safe. Both sides use Shopify's checkout event.id and Meta deduplicates them.

Get to 8+ EMQ With WeltPixel Conversion Tracking

If you want the full Conversions API payload populated automatically on every Shopify order, hashed and formatted to Meta's spec, with the browser identifiers from Meta ads carried through to the server-side event, Install WeltPixel Conversion Tracking and it sets up in around 15 minutes. It runs alongside Shopify's native Facebook & Instagram channel without duplicating Purchase events, because both sides include the same Shopify checkout event.id and Meta's matching deduplicates them.

For the deeper architectural comparison between server-side tracking via a Shopify app versus a manual GTM Server-Side setup, see our server-side GA4 article.

FAQ

Does Meta require every customer parameter to reach an 8+ EMQ score?

No. The score is weighted, not a sum. Sending hashed email and phone, a stable customer identifier, the browser identifiers from Meta's cookies, and the request context on every event is usually enough to land 8+ on Purchase. The other PII fields add incremental match confidence and are worth sending when available, but they are not the hinge that flips a 6 into an 8.

Why is my EMQ score lower on AddToCart than on Purchase?

AddToCart fires earlier in the funnel, often before checkout fields are filled in. em, ph, and the address components are not yet available, so the only matchable signals are fbp, fbc, client_ip_address, and client_user_agent. A 5-7 EMQ on AddToCart is normal even with a well-configured stack. Focus optimization effort on Purchase first.

Will the official Facebook & Instagram channel deduplicate against my server-side Purchase event?

Yes, if both events carry the same event.id. Shopify's native channel uses the checkout's stable event.id, and any well-built server-side integration (including WeltPixel Conversion Tracking) uses the same value. Meta merges the two events on its end. Running both is safe and is the recommended setup, because each catches edge cases the other misses.

Does Shopify's Web Pixels API expose enough data for advanced matching?

The Web Pixels API exposes cart and checkout events, including customer and cart objects, in a privacy-aware sandbox [3]. It is sufficient for capturing fbp and fbc cookies and for triggering events. The hashed-PII matching parameters are easier to source server-side from the Order webhook, because that is where Shopify guarantees the full address and contact fields.

How long does it take EMQ to update after a fix?

Events Manager updates EMQ in real time, but the smoothed-out score you see in the Overview panel reflects a rolling window. Plan for 24 hours of fresh events before the displayed score reflects a configuration change.

Sources

Meta for Developers, "Dataset Quality API, Conversions API": https://developers.facebook.com/docs/marketing-api/conversions-api/dataset-quality-api/
Meta for Developers, "Conversions API Best Practices": https://developers.facebook.com/docs/marketing-api/conversions-api/best-practices/
Shopify Developers, "Web Pixels API": https://shopify.dev/docs/api/web-pixels-api

Ready to upgrade your tracking?

Server-side tracking for Magento and Shopify — accurate data, better attribution, full privacy compliance.

Shopify App Magento Extension

Your cart is empty