You added Facebook CAPI to your WooCommerce store. Your Events Manager shows purchase events firing. You saw a ROAS improvement — then it plateaued, or your CPAs climbed back up, and you couldn’t work out why. The answer is usually your Event Match Quality score — and most WooCommerce stores running CAPI plugins have never looked at it.
A score below 7.0 means Meta’s algorithm is making bidding and attribution decisions with data it doesn’t fully trust. The events fire. The confidence in those events doesn’t.
And What It’s Costing Your WooCommerce Campaigns
Stores with EMQ 8+ see 23% lower CPAs than the Facebook Ads benchmark (Madgicx, 2025). The difference between a 5.8 and an 8.2 isn’t a configuration edge case — it’s the difference between a campaign that scales and one that stalls.
What Is Facebook Event Match Quality?
Event Match Quality (EMQ) is Meta’s measure of how confidently it can match your server-side conversion event to a real Facebook user profile. It scores from 0 to 10. The higher the score, the more parameters you’re sending that Meta can use to identify who converted.
Here’s why it matters beyond attribution. Meta’s ad algorithm uses your conversion events as a training signal. When EMQ is low, the algorithm treats each event as a weak signal — it’s less sure the event belongs to a real person in its system, so it discounts it. Lookalike audiences built on low-EMQ events are built on noise. Bidding strategies optimised on low-EMQ data optimise toward the wrong targets.
A 1-point improvement in EMQ score corresponds to approximately 8–12% improvement in attribution accuracy, according to Meta’s internal study (cited in Madgicx, 2025). Let that sink in. If you’re at EMQ 6.0, moving to 7.0 recovers roughly 8–12% of the attribution your campaigns are currently missing.
The 7 Parameters Meta Uses to Score You
Meta scores EMQ based on how many of these parameters your events include — and whether they’re correctly hashed:
- Email — Hashed SHA256. The most commonly sent parameter.
- Phone number — Hashed SHA256, including country code.
- First name — Hashed SHA256.
- Last name — Hashed SHA256.
- City — Hashed SHA256.
- State/region — Hashed SHA256, lowercase abbreviation.
- Click ID (fbclid) — Not hashed. Passed as-is from the URL parameter.
Sending all 7 versus sending just 1 (email only) can improve EMQ by 30–40% (Meta for Developers, 2025). Most WooCommerce CAPI plugins send email only. That’s the entire gap.
You may be interested in: What Your Marketing Pixels Actually Send: The WooCommerce Data Flow
Why Plugin-Level CAPI Caps Out at 6
The average WooCommerce store running plugin-level CAPI achieves EMQ 5.8–6.2 (Madgicx benchmark, 2025). It’s not random. It’s structural.
Most CAPI plugins for WooCommerce were built to pass the minimum viable data: email address, event name, event time, and a value. That’s enough to fire a server event. It’s not enough for a high EMQ score.
Phone numbers, names, and address fields require reading WooCommerce order data directly — not just the browser cookie. Many plugins don’t do this consistently. Some send phone in the wrong format (missing country code). Some send name fields unhashed or skip them when the customer didn’t fill in optional fields. 70% of ecommerce stores have broken or incomplete tracking configurations (Conversios, 2025). EMQ below 7.0 is the scoreboard for that brokenness.
The fbclid click ID adds another layer. Browser-side CAPI implementations often lose the click ID when checkout happens across multiple pages, or when customers return directly after a session break. If fbclid isn’t captured and stored in a first-party cookie before checkout, it never reaches your server event — and Meta loses one of its highest-confidence matching signals.
You may be interested in: Your WooCommerce Pixel Is Counting the Same Conversion Twice
How to Find Your EMQ Score Right Now
Finding your score takes two minutes. In Meta Events Manager, select your pixel and open the Events tab. Click on your Purchase event. The EMQ score appears as a number out of 10 — and below it, you’ll see a breakdown of which matched parameters Meta is actually receiving from your events.
That parameter breakdown is where it gets useful. If you see email listed but phone, name, and address fields are absent or flagged, you know exactly what to fix. If fbclid shows low coverage, your click ID capture is broken somewhere between ad click and checkout.
The diagnostic takes less time than the fix — but at least you’ll know what you’re fixing.
The Architecture That Sends All 7
Browser-side plugins face a structural ceiling. They can only send what the browser can see at the moment of purchase — and browsers lose fbclid across navigation, can’t guarantee phone format consistency, and depend on WooCommerce data being accessible at the right moment in the checkout flow.
Server-side tracking with Transmute Engine™ reads the complete WooCommerce order object via the inPIPE WordPress plugin — which captures every field the customer submitted at checkout, including phone, name, and full address. The Transmute Engine server (running first-party on your subdomain, e.g., data.yourstore.com) hashes all PII fields with SHA256 per Meta’s exact specification before routing to Facebook CAPI. The fbclid is captured in a first-party cookie by inPIPE and persisted through checkout, so it reaches the server event even when the customer takes multiple sessions to convert.
Structurally, Transmute Engine sends all 7 matched parameters with every purchase event — not as an optional configuration, but as the default. That’s the architecture EMQ rewards.
You may be interested in: Running 5 Ad Pixels at Once? The Hidden Performance Tax
Key Takeaways
- Facebook Event Match Quality (EMQ) scores 0–10 and measures how confidently Meta can match your server event to a real user profile.
- Stores with EMQ 8+ see 23% lower CPAs. A 1-point gain improves attribution accuracy by 8–12%.
- Meta uses 7 parameters: email, phone, first name, last name, city, state, and click ID (fbclid).
- Most WooCommerce CAPI plugins send email only — structurally capping EMQ at 5.8–6.2.
- Server-side tracking reads full order data and hashes all 7 parameters by default, without plugin-level configuration.
Meta considers 8.0+ excellent. Scores of 7.0–7.9 are good. Below 7.0, your conversion signal is degraded — the algorithm has lower confidence matching your events to real user profiles, which raises CPAs and weakens lookalike audiences. Most WooCommerce CAPI plugins score 5.8–6.2 by default.
CAPI firing correctly only means events are reaching Meta’s servers. EMQ scores the quality of the matched parameters inside those events. If your plugin sends only hashed email, your EMQ will be low regardless of how correctly the event fires. You need all 7 matched parameters to score above 7.0.
Meta matches on: email, phone number, first name, last name, city, state/region, and click ID (fbclid). All PII fields must be hashed with SHA256. Sending more of these parameters — correctly formatted — directly raises your EMQ score. Sending 7 vs. 1 can improve EMQ by 30–40%.
Go to Meta Events Manager, select your pixel, click on the Events tab, and open a Purchase event. The EMQ score appears as a number out of 10. Below it you’ll see a parameter breakdown showing which matched parameters Meta is receiving — this tells you exactly what’s missing.
Yes. Stores with EMQ 8+ see 23% lower CPAs than benchmark (Madgicx, 2025). Higher EMQ means Meta’s algorithm can attribute conversions more accurately, build stronger lookalike audiences, and make better bidding decisions. Each 1-point improvement corresponds to 8–12% better attribution accuracy.
If your Facebook CAPI is firing but your campaigns won’t scale, check your EMQ score before touching your ad creative. See how Seresa routes all 7 matched parameters by default.