Meta EMQ Score Estimator

What Is Meta Event Match Quality (EMQ)?

Meta Event Match Quality is a score from 0–10 that measures how accurately your conversion events are being matched back to Meta user profiles. A high EMQ score means Meta can reliably attribute purchases, add-to-carts, and other events to specific ad clicks — which directly determines how accurately your ROAS is reported and how well Meta's algorithm can optimise your campaigns.

The core problem: browser-only tracking is broken. Apple's iOS App Tracking Transparency, Safari's ITP, and widespread use of ad blockers all interfere with the Meta Pixel's ability to fire accurately. When a customer uses iOS Safari, your pixel may miss 20–40% of conversions entirely. Those conversions still happen — they just become invisible to Meta.

How EMQ Score Is Calculated

Meta calculates EMQ based on which customer data signals are present in your event payload and how accurately they can be matched to a Meta user profile. The most valuable signals are:

• Email address — highest individual impact. Must be SHA256 hashed before sending.
• Phone number — second highest impact. Hashed in E.164 format.
• External ID — your Shopify customer ID or order ID. Medium impact but easy to include.
• Click ID (fbc) — captured from URL when a user clicks your Meta ad. High deduplication value.
• IP address + User Agent — lower individual impact, but contribute to overall match rate.

Sending events server-side (via the Events API) is the single biggest improvement available because it ensures events fire regardless of browser restrictions, ad blockers, or iOS settings. Server-side signals are more reliable, arrive faster, and can carry more data than browser pixel events.

Why Low EMQ Scores Directly Cost You Money

Reporting accuracy: If Meta can only match 60% of your conversions back to ad clicks, your reported ROAS is based on 60% of actual revenue. You may be cutting campaigns that are actually profitable, or scaling campaigns that look strong but have inflated numbers.

Algorithm optimisation: Meta's Advantage+ campaigns and automated bidding use conversion signals to find buyers. Low-quality signals mean the algorithm is learning from incomplete data — it optimises toward the 60% of conversions it can see, not the 100% that are happening.

Attribution windows: Meta's default attribution window is 7-day click, 1-day view. With low EMQ, conversions that happen 2–3 days after a Meta ad click may never be matched, artificially compressing your measured attribution window.

How to Fix Low Meta EMQ on Shopify — Free Method

The fastest way to improve EMQ on Shopify is to implement server-side tracking via the Meta Conversions API using Make.com. When a Shopify order is placed, a Make.com webhook fires immediately and sends a Purchase event directly to Meta's server — with hashed email, phone, external_id, and IP address all included in the payload. This bypasses every browser-level restriction and typically moves EMQ scores from 4–5 range to 6–8+ range.

The full setup takes approximately 6 minutes on Make.com's free tier (1,000 credits/month). No code, no developer, no ongoing subscription. The guide at stackarchitect.xyz/capi-shield covers every step.

Low EMQ is one visible symptom of a wider measurement gap. For how much purchase signal the typical Shopify store loses to iOS — a sourced 20–40% — see the iOS attribution gap benchmark.

EMQ score bands — what each range actually means

Meta scores every web event from 0–10 on a rolling 48-hour window. The bands below are the working interpretation used across Shopify tracking practice in 2026 — what each range tells you to do next, not just a colour.

Which signals move the score — and by how much

EMQ is cumulative: it rewards parameter depth on every event, not one perfect identifier. Hashed identifiers are matched deterministically; the browser and click IDs (fbc, fbp) carry the probabilistic load for anonymous visitors. Critical detail most setups get wrong: email, phone, external_id, names and address are SHA-256 hashed before sending — but fbc and fbp must never be hashed.

Event-specific benchmarks — why one number is misleading

A single store-wide EMQ figure hides the real picture, because different event types structurally score differently. Purchase events fire at checkout where email, phone and address all exist, so they score high. PageView and Add to Cart events fire before the visitor has typed anything — and fbc only exists if they arrived from a Meta ad — so they score lower by design. Judge each event against its own benchmark, not against Purchase.

Figures reflect Meta’s published Conversions API guidance and 2026 EMQ documentation. EMQ updates on a rolling 48-hour window, so allow two days after any change before re-reading your score in Events Manager (Data Sources → your dataset → Events).