Why it matters
Meta can only optimize on events it can match to a person or device. When hashed email, phone, click IDs (fbc), browser IDs (fbp), or external IDs are missing, stale, or inconsistent, server events arrive but do not attach to ad accounts. The campaign still spends, but learning is based on a thinner, biased slice of outcomes.
EMQ is the practical dashboard for that problem. A drop from 8 to 4 often correlates with weaker reported ROAS, longer learning phases, and value optimization that never stabilizes, even when your backend conversion count is unchanged. For teams sending modeled values, low EMQ is a silent tax: the model may be sound, but the platform never receives enough matched value events to steer delivery.
EMQ applies to server-side web CAPI events. App flows and MMP postbacks have separate diagnostics, but the underlying principle is the same: match quality gates how much signal Meta can use.
Event Match Quality (EMQ)
EMQ sits on the delivery side of pLTV activation, not the modeling side:
- First-party data and revenue history live in your data warehouse.
- Churney models user-level pLTV from that history.
- Churney sends designed value events directly to Meta via CAPI with complete hashed identifiers and click/browser IDs where available.
- Meta scores EMQ per event type in Events Manager; matched events feed value optimization or Non-Purchase Value Optimization (NPVO).
- Teams track EMQ trend alongside signal volume and incrementality vs BAU conversion in a holdout.
Strong pLTV without strong match is incomplete activation. EMQ tells you whether the pipe is working before you judge the model.
Category variants
| Model | How EMQ shows up |
|---|---|
| Ecommerce / DTC | Purchase and custom value events via web CAPI; hashed email/phone from checkout plus fbc/fbp from paid traffic; EMQ often highest on Purchase, lower on upper-funnel custom events. |
| Subscription app | Web trial or subscribe flows via CAPI; app events may flow via SDK/MMP with separate match diagnostics. |
| SaaS / PLG | Lead and activation events with corporate email domains; match can lag B2C if identifiers are sparse at signup. |
Common mistakes
- Checking pixel diagnostics but ignoring CAPI EMQ. Browser and server match quality are reported separately.
- Sending events without hashed PII when you have it. Email and phone are among the strongest web match keys when hashed correctly.
- Inconsistent external_id across sessions. Breaks user stitching and weakens match on repeat events.
- Stale fbc/fbp capture. Click and browser IDs decay; capture at click and persist through conversion.
- Judging pLTV performance before EMQ is stable. Low match can look like a bad model when the issue is identifier completeness.
Advertiser lens
| Role | What they ask | What good looks like |
|---|---|---|
| Head of Performance / UA | Why did value campaigns stop learning? | EMQ by event type, trend vs last quarter, and action list for parameter gaps. |
| VP Growth / CMO | Is server-side tracking actually working? | Documented match uplift vs pixel-only baseline before scaling value goals. |
| Marketing Analytics / Data Science | Are we losing events before optimization? | Join rate: data warehouse conversions vs Meta matched events; EMQ correlated with value variance. |
| Data Engineering | Who owns identifier hashing and persistence? | Schema map for hashed fields, fbc/fbp capture, monitoring on failed CAPI deliveries. |
| Finance / Procurement | Does low match distort ROI reporting? | Clear separation of platform-attributed metrics vs blended/incremental readout. |
FAQ
What is Event Match Quality (EMQ)?
EMQ is Meta's 0–10 rating for how well customer information on server-side web events matches to Meta accounts. It reflects identifier completeness and quality on CAPI events.
Where do I see EMQ?
In Meta Events Manager, per event type, for server-side web events. Meta also surfaces parameter recommendations when match keys are missing.
What is a good EMQ score?
Higher is better. Many performance teams treat 8+ as healthy for value optimization, but context matters: event type, industry, and identifier availability all shift the baseline. Track trend, not a single snapshot.
Does EMQ affect app events?
EMQ as labeled in Events Manager targets web CAPI events. App attribution uses SDK and MMP paths with different diagnostics, though identifier completeness still drives match.
How does EMQ relate to pLTV?
pLTV is the value you send; EMQ is whether Meta can attach that value to the right account for optimization. Both must be healthy for value-based campaigns to learn reliably.
Which identifiers improve EMQ most?
Hashed email and phone, fbc (click ID), fbp (browser ID), and a stable external_id from your first-party stack. Pass as many valid keys as you can on each event.
Can Churney help improve EMQ?
Churney designs CAPI event payloads and timing as part of pLTV activation, including identifier fields your data warehouse and checkout stack can supply. See the data guide for readiness requirements.
Not the same as
| Term | Difference |
|---|---|
| Match rate (generic) | Cross-platform concept; EMQ is Meta's specific web CAPI diagnostic. |
| Attribution window | How long Meta credits a touchpoint; EMQ is whether the user is identified at all. |
| Signal volume | Event count; EMQ is quality of user match on those events. |
| Meta pixel | Client-side tracking with its own diagnostics; complementary to CAPI EMQ. |
