--------------------------- Title: How to Improve Your Meta Event Match Quality Score URL: https://usercentrics.com/knowledge-hub/improve-meta-event-match-quality-score/ --------------------------- # How to Improve Your Meta Event Match Quality Score ### Key Takeaways - EMQ is Meta's zero-to-ten score for how well your event data matches real visitors on its platform. - Meta scores EMQ per event type. Purchase events typically score highest. PageView events score lowest. - Browser pixel tracking alone usually produces scores between three and five. Server-side tracking unlocks the higher bands. - The most common EMQ problems are missing parameters, broken hashing, and inconsistent parameter coverage. - Usercentrics Meta Signals Gateway offers a managed server-side path that sends consented first-party data to Meta. Your Meta ads may not have a creative problem. They may have a data quality problem. EMQ is Meta's scoring system for conversion data and a low score means weaker targeting, higher cost per acquisition (CPA), and unreliable attribution. The good news: most low EMQ scores trace back to technical gaps that you can fix easily. ## What Is Meta Event Match Quality? [Event Match Quality (EMQ)](https://www.facebook.com/business/help/765081237991954?id=818859032317965) is a score from zero to ten that Meta assigns to your conversion events. It measures how well the customer information you send can identify a real Meta visitor. Here's what happens. A visitor takes an action on your site, like completing a purchase. You send that event to Meta with customer data attached. Meta compares those data points against its visitor database. If it finds a match, it connects that conversion to a specific person. The more data points you send, and the more accurate they are, the higher your score. Meta uses four scoring bands: - **Great (8.0 and above):** Meta matches events to visitors with high confidence. - **Good (6.0 to 7.9):** Solid signal quality. Room for improvement. - **OK (4.0 to 5.9):** Weak matching. Limited optimization capability. - **Poor (below 4.0):** Critical gaps. The setup needs immediate attention. EMQ isn't one number for your whole account. Meta calculates it per event type. Purchase events usually score highest because checkout forms collect detailed data. PageView events score lowest because anonymous visitors provide almost nothing to match. ## Why Does Your EMQ Score Matter for Ad Performance? EMQ directly affects three areas of your Meta campaigns. Understanding each one helps you prioritize where to focus your improvement efforts. Attribution accuracy comes first. When Meta can't match a conversion to a visitor, that sale disappears from your reporting. Ads Manager can't credit the right campaign, which makes performance evaluation unreliable. Ad delivery optimization is the second impact. Meta's algorithm studies who converts and finds more people like them. Low EMQ feeds the algorithm noisy data. It struggles to distinguish high-value visitors from low-value ones and the result is wasted budget on the wrong audiences. Audience quality suffers, too. Strong EMQ produces sharper Custom Audiences and Lookalike Audiences. The math is simple: more matched events give Meta more training data, which drives faster optimization and lower CPA. ## **How to Check Your Event Match Quality Score in Meta Events Manager** Checking your EMQ takes about two minutes. Open Meta Events Manager from Business Suite and select the dataset (pixel) you want to review. You'll see each tracked event listed: Purchase, AddToCart, Lead, PageView, and others. Meta displays the EMQ score and rating band next to each one. Click into an individual event for the full breakdown. Events Manager shows which customer parameters you're sending and which ones you're not. It also shows what percentage of event instances include each parameter. Focus on per-event scores, not just the dataset summary. A strong Purchase score can hide weak scores on higher-volume events. Those weaker events still drag down your overall signal quality. ## **What Causes a Low EMQ Score?** Low EMQ almost always comes from one of four technical issues. Each one is fixable. ### Missing Customer Information Parameters This is the simplest cause. If you only send email with your events, Meta has one data point to match against. Adding phone number, name, city, state, zip code, and country gives Meta more chances to identify a visitor. The strongest identifiers are email (em), phone (ph), and external_id. Location fields are supplementary but still valuable. ### Incorrect Hashing or Formatting Meta requires specific formatting before you apply SHA-256 hashing. Email addresses must be lowercase and trimmed of whitespace. Phone numbers must use the E.164 international format. Names must be lowercase with special characters removed. If you hash "John@Example.com" instead of "john@example.com," the hashes won't match and Meta can't identify the visitor. Small formatting errors are one of the fastest ways to land in the "Poor" band. Note that some parameters — client_ip_address, client_user_agent, fbp, and fbc — must stay in plain text. Hashing them breaks matching entirely. ### Low Parameter Coverage Across Events Coverage measures how consistently you send a parameter across all instances of an event type. Sending email on 95 percent of events scores far higher than sending it on 40 percent. Coverage is also volume-weighted. High-volume events with thin data, like PageView, drag down your dataset-level score. A strong Purchase EMQ doesn't compensate for thousands of thin PageView events. ### Pixel-Only Tracking Without Server-Side Support The browser pixel runs entirely within the visitor's browser. It's subject to ad blockers, Safari's Intelligent Tracking Prevention (ITP), and tab closures. A visitor who completes a purchase and immediately closes the tab may never trigger the pixel. Pixel-only setups typically produce EMQ scores between three and five. Server-side tracking is the change that breaks through that ceiling. ## How to Improve Your Event Match Quality Score These seven steps move roughly in order of impact. Server-side tracking creates the foundation. The remaining steps build on it. ### Step 1: Implement Server-Side Tracking With the Conversions API This is the single highest-impact change you can make. The Conversions API (CAPI) sends events from your server to Meta. It works around browser limitations entirely. Your server reliably forwards client IP, user agent, and first-party cookies (fbp and fbc) with every event. The pixel can't do this consistently, especially on Safari and iOS. CAPI also captures events the pixel misses, like a purchase completed just before a visitor closes the tab. This moves most advertisers from "OK" into "Good" or "Great." Learn more in our server-side tracking overview (usercentrics.com/server-side-tracking/). ### Step 2: Send More Customer Information Parameters Don't stop at email. Meta accepts a wide range of customer information parameters, and each one you add improves match probability. The highest-priority fields are: - **em (email):** The single strongest identifier. - **ph (phone):** A strong secondary match key. E.164 format required. - **external_id:** Your own customer or visitor ID. - **fn and ln (first and last name):** Help when email isn't available. - **ct, st, zp, country (location):** Supplementary identifiers that add confidence. Collect this data at checkout, account registration, lead forms, and newsletter signups. The more touchpoints you capture, the stronger your coverage. ### Step 3: Fix Your Hashing and Formatting Follow these rules before applying SHA-256: - **Email:** Lowercase, trim whitespace. "Jane.Doe@Example.com " becomes "jane.doe@example.com" before hashing. - **Phone:** Digits only, E.164 with country code. "(415) 555-1234" becomes "14155551234" before hashing. - **Names:** Lowercase, trimmed, no special characters. "O'Brien" becomes "obrien" before hashing. - **City:** Lowercase, no spaces. "New York" becomes "newyork." - **State:** Two-letter lowercase. "CA" becomes "ca." Do not hash client_ip_address, client_user_agent, fbp, or fbc. Send these in plain text. Hashing them prevents Meta from reading them. ### Step 4: Improve Parameter Coverage Across All Events High coverage on Purchase events alone isn't enough. Meta evaluates consistency across all event types. Review each event in Events Manager and identify which parameters have low send rates. Then work backward to your data collection points. If logged-in visitors trigger AddToCart events, you already have their email and name. Pass that data with the event. ### **Step 5: Forward fbp, fbc, Client IP, and User Agent** These four parameters are easy to overlook. They aren't personally identifiable in the traditional sense, but they're critical for Meta's matching: - **fbp (Facebook browser ID):** A first-party cookie identifying the browser session. - **fbc (Facebook click ID):** Captures the fbclid from ad click URLs. - **client_ip_address:** Used for location-based matching. - **client_user_agent:** Helps match device-level patterns. In a pixel-only setup, Meta captures some of these automatically. In a CAPI setup, you must forward them from the browser to your server. Leaving these out is one of the most common CAPI mistakes. ### **Step 6: Set Up Event Deduplication** If you run the Meta Pixel and CAPI together, you need event deduplication. Meta recommends this dual setup, but without deduplication it counts every conversion twice. Generate a unique event_id on the client side. Send that same ID with both the pixel event and the CAPI event. Meta uses it to recognize duplicates and count the event once. ### **Step 7: Use a Managed Solution to Reduce Configuration Risk** Most EMQ problems are configuration errors. A phone number formatted wrong. A parameter hashed when it shouldn't be. Or the fbp cookie not forwarded from browser to server. ## How Much Revenue Are You Leaving on the Table? If you’re not sure whether signal loss is costing you real money, use our free ROAS calculator to model the gap between what your ads report and what they actually deliver. ## **How Server-Side Tracking Improves EMQ, and Where Signals Gateway Fits** The connection between server-side tracking and EMQ is architectural. With pixel-only tracking, the browser handles everything, it fires tags, sets cookies, and sends data to Meta directly. Every event passes through an environment you don't control. Ad blockers, ITP, and network interruptions all reduce what reaches Meta. Server-side tracking reroutes the data flow. The browser sends events to your server first. Your server then forwards them to Meta. This gives you control over what data leaves your infrastructure. You can enrich events with CRM data before they reach Meta, and events land reliably regardless of what happens in the browser. For EMQ specifically, this matters because server-side tracking delivers the four parameters the pixel can't reliably capture: client IP, user agent, fbp, and fbc. You can also attach customer data from your backend. [Usercentrics Meta Signals Gateway ](https://usercentrics.com/knowledge-hub/meta-signals-gateway/)is a managed, hosted implementation of Meta's Signals Gateway technology, sending conversion data to Meta's Conversions APIIt sends your first-party data to Meta from both the browser and the gateway, giving Meta more matchable signals to work with, which can help improve your EMQ score. To get the full benefit, make sure the data itself is correctly formatted, hashed, and deduplicated before it's sent. Pair it with [Usercentrics Consent Management Platform (CMP)](https://usercentrics.com/website-consent-management/) and you can configure Signals Gateway to only fire for visitors who have given consent, keeping the data you send to Meta aligned with visitor choices under regulations like General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA). Your first 20,000 events are free. --- ## Footer ### Products - [Usercentrics Web CMP](https://usercentrics.com/website-consent-management/) - [Usercentrics App CMP](https://usercentrics.com/in-app-sdk/) - [Usercentrics CTV CMP](https://usercentrics.com/usercentrics-ctv-cmp/) - [Usercentrics Privacy Policy Generator](https://usercentrics.com/privacy-policy-generator/) - [Server-side Tagging Solution](https://usercentrics.com/server-side-tracking-solution/) - [Usercentrics Preference Manager](https://usercentrics.com/preference-management/) - [Audience Unlocker](https://usercentrics.com/audience-unlocker/) - [Integrations](https://usercentrics.com/integrations/) - [Web compliance scan](https://usercentrics.com/privacy-compliance-scanner/) - [App compliance scan](https://usercentrics.com/app-data-privacy-audit/) - [ROAS Calculator](https://usercentrics.com/roas-calculator/) ### Solutions - [Data Privacy Regulatory Compliance](https://usercentrics.com/data-privacy-regulatory-compliance/) - [Marketing Performance Optimization](https://usercentrics.com/marketing-performance-optimization/) - [Migration](https://usercentrics.com/migration/) - [Media & Publishing](https://usercentrics.com/media-publishing/) - [Retail & Ecommerce](https://usercentrics.com/retail-ecommerce/) - [Banking, Finance & Insurance](https://usercentrics.com/banking-finance-insurance/) - [Healthcare & Pharmaceuticals](https://usercentrics.com/healthcare-pharmaceuticals/) - [Gaming](https://usercentrics.com/gaming/) - [Education](https://usercentrics.com/education/) - [Automotive](https://usercentrics.com/automotive/) - [Travel & Hospitality](https://usercentrics.com/travel/) ### Regulations - [GDPR (EU)](https://usercentrics.com/gdpr/) - [GDPR (UK)](https://usercentrics.com/uk-gdpr/) - [CCPA (California)](https://usercentrics.com/ccpa/) - [TCF v2.3 (IAB)](https://usercentrics.com/cmp-for-publishers/) - [DMA (EU)](https://usercentrics.com/digital-markets-act-dma/) - [Amazon Consent Signal](https://usercentrics.com/usercentrics-cmp-and-amazon-consent-signal/) - [Google Consent Mode (EU)](https://usercentrics.com/usercentrics-cmp-and-google-consent-mode-v2/) - [Microsoft UET Consent Mode (EU)](https://usercentrics.com/usercentrics-cmp-and-microsoft-consent-mode/) - [Microsoft Clarity Consent Mode](https://usercentrics.com/usercentrics-cmp-and-microsoft-clarity-consent-mode/) - [View all regulations](https://usercentrics.com/regulations-and-frameworks/) ### Resources - [Blog](https://usercentrics.com/knowledge-hub/) - [Whitepapers](https://usercentrics.com/whitepapers/) - [Checklists](https://usercentrics.com/checklists/) - [Courses](https://courses.usercentrics.com) - [Customer stories](https://usercentrics.com/customer-stories/) - [Privacy-Led Marketing](https://usercentrics.com/privacy-led-marketing/) - [Events](https://usercentrics.com/webinar/) - [CONSENTED podcast](https://usercentrics.com/consented/) - [Guides](https://usercentrics.com/guides/) - [Release notes](https://releases.usercentrics.com/en) - [Developer documentation](https://usercentrics.com/docs/) - [RFI template](https://usercentrics.com/resources/usercentrics-rfi-template/) - [Customer directory](https://usercentrics.com/usercentrics-customer-directory/) ### Company - [About us](https://usercentrics.com/about-us/) - [Press](https://usercentrics.com/press/) - [Our offices](https://usercentrics.com/contact/) - [Trust center](https://trust.usercentrics.com/) - [Careers](https://usercentrics.com/career/) - [Open positions](https://apply.workable.com/usercentrics/) - [Diversity and inclusion](https://usercentrics.com/dei/) ### Support - [General support](https://support.usercentrics.com/hc/en-us) - [Contact sales](https://usercentrics.com/book-a-consultation/) - [Technical support](https://support.usercentrics.com/hc/en-us/requests/new) - [Billing and account](https://support.usercentrics.com/hc/en-us/categories/12253804608156-Account-and-billing) - [Suggest a feature](https://support.usercentrics.com/hc/en-us/requests/new?ticket_form_id=10610312381340) - [Partner login](https://partnerportal.usercentrics.com/) - [Partner program](https://usercentrics.com/partner-program-overview/) - [Affiliate program](https://usercentrics.com/affiliates/)