Home / Blog / Meta EMQ Low After Elevar
Shopify · Tracking Troubleshooting
Meta Event Match Quality Low After Installing Elevar: What to Check
If Meta Event Match Quality stays low after installing Elevar, the issue is usually not that Elevar “doesn’t work.” EMQ depends on the quality, coverage, and consent status of the customer information sent with server events.
Keyword target
- Primary: Meta Event Match Quality low after installing Elevar
- Secondary: Meta EMQ low Elevar Shopify, Elevar Meta CAPI Event Match Quality, Meta Event Match Quality low Shopify, improve Meta EMQ Shopify Elevar, Meta CAPI user data missing Shopify
Key takeaways
- EMQ is about match data quality, not just whether CAPI fires.
- Purchase EMQ is usually stronger than upper-funnel events because checkout has more identity data.
- Consent, accelerated checkout, and missing fbp/fbc can weaken match quality.
- Make sure you are looking at the Elevar server event, not a duplicate/native source.
What Meta says EMQ means
Meta says Event Match Quality indicates how effective the customer information parameters sent with a server event may be at matching events to Meta accounts. Better match quality can help attribution and delivery. That means a server event can fire successfully and still have low EMQ if identity parameters are weak.
Common causes after Elevar install
Low EMQ after an Elevar install is usually a mapping, coverage, consent, or source inspection problem.
| Cause | Symptom | Check |
|---|---|---|
| Missing email/phone | low Purchase EMQ | server user_data fields |
| Missing fbp/fbc | weak browser/server linkage | first-party cookie/click capture |
| Consent blocks identity | EU/UK traffic low EMQ | CMP and Elevar consent settings |
| Wrong source inspected | native event low, Elevar event clean | Events Manager event origin |
| Accelerated checkout | identity/click context missing | Shop Pay/PayPal test orders |
| Duplicate Meta sources | mixed diagnostics | remove duplicate Purchase owners |
Elevar-specific audit angle
Check that Elevar’s Shopify source and Meta destination are live, the Meta Pixel/Dataset matches the intended account, consent settings are mapped correctly, and the browser and server events are paired. Also check whether the native Meta app or another CAPI tool is still sending competing events.
Diagnostic workflow
- Open Meta Events Manager and inspect Purchase EMQ, not only page_view.
- Confirm the event origin/source is Elevar’s server event.
- Check email, phone, name/address, external_id, fbp, fbc, IP, and user agent coverage.
- Run test orders with normal checkout, Shop Pay, and PayPal.
- Check consent allowed vs denied states.
- Check Elevar Meta destination settings and dataset ID.
- Check duplicate native Meta/GTM/CAPI sources.
- Review whether checkout identity is available at the time the server event is sent.
- Wait for Events Manager processing before judging EMQ.
What not to do
- Do not expect page_view EMQ to match Purchase EMQ.
- Do not judge Elevar by a duplicate event sent by another app.
- Do not send identity data without respecting consent and policy.
- Do not chase a perfect EMQ score before verifying event count and deduplication.
TrackingAudit validation checklist
- Correct Meta Dataset checked
- Elevar event origin confirmed
- Purchase EMQ reviewed
- user_data fields checked
- fbp/fbc checked
- consent mapping checked
- accelerated checkout tested
- duplicate Meta sources checked
- deduplication checked
- 24-hour processing allowed
Need the tracking checked before scaling?
TrackingAudit can compare Shopify orders against the active event stack and show which system is missing, duplicating, or misattributing purchases.
Get your free audit →Frequently asked questions
What is Meta Event Match Quality?
Meta says it indicates how effective customer information parameters on server events may be at matching events to Meta accounts.
Why is EMQ low after installing Elevar?
Usually because identity fields, click/browser identifiers, consent-approved data, or event source selection are incomplete.
Does low EMQ mean CAPI is broken?
Not necessarily. CAPI can fire while match data quality is weak.
Should I optimize EMQ before deduplication?
Both matter. Fix duplicate Purchase ownership first, then improve match data coverage.