--- title: Fixing Low Meta CAPI Event Match Quality on Shopify (2026 Guide) description: Improve your Meta CAPI Event Match Quality on Shopify with our 2026 guide. Learn to diagnose low scores, fix common data parameter issues, and enhance your ad canonical: https://tacey.app/blog/fixing-low-meta-capi-event-match-quality-on-shopify-2026-guide published: 2026-10-30T13:01:45.501Z updated: 2026-10-30T13:01:45.501Z category: Marketing & Growth --- # Fixing Low Meta CAPI Event Match Quality on Shopify (2026 Guide) A low Meta CAPI Event Match Quality score can limit your ad attribution and performance. This guide provides a diagnostic checklist and step-by-step instructions for Shopify merchants to diagnose and fix common event matching issues. Your Meta ad campaigns are running, but the numbers in Events Manager feel disconnected from your Shopify sales. Your cost per acquisition is climbing, and you suspect your tracking is leaking. You check your Meta pixel diagnostics and see an Event Match Quality score that is lower than you would like, but you are not sure what it means or how to fix it. This is a common issue for Shopify merchants. A low Event Match Quality score is a direct signal that Meta is struggling to connect your store's conversion events to the people who saw your ads. This guide walks through how to diagnose the problem and provides concrete steps to improve your score. ## What is Meta CAPI Event Match Quality (EMQ)? Event Match Quality (EMQ) is a score from 0 to 10 that Meta assigns to your server-side events. It estimates how effectively the customer information sent via the Conversions API (CAPI) allows Meta to match a conversion event, like a purchase, to a specific user account on Facebook or Instagram. Think of it as a data quality report card. A high score means you are sending clean, comprehensive data that Meta can confidently use for attribution and audience building. A low score means the data is sparse or poorly formatted, leaving Meta to guess who your customers are. This score is calculated for each type of event, so your "Purchase" event will have a different score than your "ViewContent" event. The score only applies to events sent through the CAPI, not events that only arrive from the browser-based Meta Pixel. ## Why is a high EMQ score critical for Shopify ad tracking in 2026? A high EMQ score is crucial because it directly impacts your ad campaign's performance and reporting accuracy. When Meta can confidently match a purchase to a user, it can better attribute that sale to the correct ad, optimize ad delivery to find similar buyers, and build more effective retargeting audiences. With increasing browser privacy restrictions and the decline of third-party cookies, server-side tracking via CAPI has become essential. However, simply having CAPI enabled is not enough. If the events you send have a low match quality, you are sending signals that Meta cannot effectively use, which can lead to higher ad costs and lower return on ad spend (ROAS). ### A worked example: The cost of a low EMQ score Imagine you spend $1,000 on ads and get 20 sales, for a true ROAS of 5.0 (assuming a $250 AOV). With a high EMQ of 8.5, Meta successfully attributes 18 of those 20 sales. The reported ROAS is 4.5, which is close enough to reality. Your campaigns are correctly seen as successful. Now consider the same campaign but with a low EMQ of 4.0. Meta only matches 8 of the 20 sales. The reported ROAS plummets to 2.0. Meta's algorithm now thinks your ads are failing. It may stop showing them to the right people, leading to a real drop in performance and a spiral of wasted ad spend. A purchase that Meta receives but cannot match to a person is a purchase that never trains its delivery algorithm or contributes to your reported ROAS. Improving your EMQ is one of the most direct ways to improve the efficiency of your ad spend. > The signal you send to an ad platform is only as good as the data it contains. A high match rate is the foundation of effective ad optimization, ensuring your budget is spent reaching actual potential customers, not just anonymous clicks. Odera Joseph Echendu, Founder, Tacey ## What are the most common reasons for a low EMQ score on Shopify? A low EMQ score usually means your server-side events are missing key customer data parameters, or the data is formatted incorrectly. A common issue is that customer identifiers like email and phone number are not being passed, or they are being passed in a format Meta cannot use. One of the most frequent errors is incorrect data hashing. Meta requires customer information to be hashed using SHA-256, but it must be formatted correctly _before_ hashing. For example, an email must be lowercased and have extra spaces removed before the hash is calculated. A simple difference like "jane.doe@email.com" versus "Jane.Doe@email.com" creates two entirely different hashes. If a customer signs up with a capital letter but your system normalizes it before sending it to CAPI, the browser pixel and server event might not match. This is a frequent source of failed deduplication and low scores. Another silent killer of EMQ is event delay. Meta prefers to receive events in near real-time. Some setups might use batch processing or have server queues that cause delays of hours. While Meta accepts events up to seven days late, any significant delay hurts real-time campaign optimization and can degrade your score. Other common issues include missing the Facebook Click ID (fbc), which is vital for attribution, or sending events more than seven days after they occurred, which causes Meta to reject them. Many server-side setups also fail to include the user agent and event source URL, which are required for website events. ## How can you check your store's current Event Match Quality score? You can check your EMQ score directly within Meta Events Manager. This process takes only a few minutes and gives you a clear picture of your current tracking health. It is the first step in any diagnostic process. Navigate to Events Manager, select your dataset (pixel), and go to the "Overview" tab. Here, you will see a list of your events, like "Purchase" and "AddToCart". Each event that is being sent via CAPI will have its own EMQ score displayed. Click on an event and choose "View details" to get more information. This screen shows your score out of 10 and a breakdown of the customer information parameters Meta is receiving for that event, including how often each one arrives. This view will tell you exactly which data points are missing or being sent infrequently. In the details view, pay close attention to the percentages next to each parameter. If "Email" is present in 95% of events but has a "Match Rate" of only 60%, it is a red flag. This suggests the email data you are sending is often in a format Meta cannot use, or it does not match a user in their system. ## What are the 5 steps to improve your CAPI event matching? Improving your EMQ score involves a systematic process of checking and refining the data you send to Meta. While some setups can be complex, many improvements come from fixing basic formatting and ensuring all available data is passed correctly. A score above 8 for your Purchase event is a good target. - **Ensure All Key Parameters Are Sent:** The most impactful parameters are hashed email, phone number, and the Facebook Click ID (fbc). Work with your developer or app provider to ensure your CAPI integration is capturing and sending these for every relevant event, especially purchases. - **Verify Correct Data Formatting Before Hashing:** As detailed in a Medium post by Charles T, data must be normalized before it is hashed. This means lowercasing emails and names, removing symbols from phone numbers (while keeping the country code), and using two-letter state codes for US addresses. - **Enable Automatic Advanced Matching:** In your Events Manager settings, turn on Automatic Advanced Matching. This allows Meta to use information from the pixel to help match events when your CAPI data is incomplete. It's a simple, effective way to boost your match rate. - **Implement Proper Event Deduplication:** You should be running the Meta Pixel alongside CAPI. To avoid counting conversions twice, you must use event deduplication. This requires sending a unique `event_id` (like the Shopify order ID) with both the pixel event and the CAPI event for the same conversion. - **Use the Test Events Tool:** Before deploying changes, use the Test Events tool in Events Manager. This allows you to make a test purchase and see exactly what data is received by Meta from both your browser (pixel) and your server (CAPI). You can verify that parameters are present and correctly formatted. ### Diving deeper into the five steps For a "Purchase" event, you should aim to send every possible parameter, as the customer has provided their full details. For an "AddToCart" event, you may only have an email address if the user is logged into their store account. Do not send blank or placeholder data; only send what you have actually collected. The same applies to phone numbers. A number formatted as `(555) 123-4567` must be normalized to `15551234567` before hashing. This includes the country code and removes all symbols or spaces. Consistency is the most important factor, as the pixel and CAPI must perform the exact same normalization to match. Think of Automatic Advanced Matching as a safety net, not the primary solution. It is a sign that your server-side data is incomplete. While it helps, relying on it means you are not fully leveraging the power and reliability of CAPI. The goal should be to make your server events so good that this setting has little work to do. Getting deduplication wrong is costly. If you fail to send a matching `event_id`, you will double-count every purchase that fires from both the pixel and CAPI. Your ROAS will look amazing, but it will be a lie. For example, a $10,000 ad spend might report a 10x ROAS when the reality is a barely profitable 5x. Conversely, if your logic is flawed, you might accidentally deduplicate unique events, hiding real sales from Meta. When you see a discrepancy in the Test Events tool, it provides a clear clue. If the browser event shows a parameter like `fbc` but the server event does not, it means your server-side logic is failing to capture or pass that value. This is the moment to check your app's settings or your developer's code. ## Does Shopify's native Meta integration handle all customer data parameters? Shopify's native integration for Meta makes it easy to get started with CAPI, but its default settings may not be enough to achieve a high EMQ score. The level of data shared depends on the "Customer data sharing" setting you choose in your Shopify admin under the Meta sales channel. The "Standard" setting is very limited. To enable CAPI and send richer customer data, you need to select "Enhanced" or "Maximum". These settings pass customer details like name, location, email, and phone number, which are essential for a good match rate. The "Maximum" setting also presents a trade-off between data richness and control. It sends a broad set of customer data automatically. For merchants who need granular control over which specific parameters are sent, perhaps for regional privacy compliance, a dedicated tracking app often provides more flexibility than Shopify's all-or-nothing approach. However, even with the "Maximum" setting, some stores find their EMQ scores hover in the 6 to 7 range. Achieving a score of 8 or higher often requires a more advanced setup, either through a dedicated tracking app from the [Shopify App Store](https://apps.shopify.com?utm_source=tacey&utm_medium=blog&utm_campaign=fixing-low-meta-capi-event-match-quality-on-shopify-2026-guide) or a custom server-side implementation, to ensure every possible parameter is captured and formatted perfectly. ## How does accurate user data improve both tracking and ad delivery? Accurate user data is the currency of modern digital advertising. For tracking, complete and correct data allows Meta to attribute more of your sales to the ads that drove them. This moves conversions out of the "unattributed" bucket and gives you a clearer understanding of your return on ad spend. For delivery, this same data is what fuels Meta's optimization algorithms. When Meta knows the precise characteristics of the people who buy from you, it can more effectively find and show your ads to new audiences who look just like your best customers. A higher EMQ score leads to a more efficient ad delivery system. This creates a positive feedback loop, or a data flywheel. Better data leads to better ad targeting. Better targeting results in more efficient sales. More sales generate more high-quality conversion data. This virtuous cycle continually refines your audience and improves your ROAS, making each ad dollar work harder than the last. This principle of data accuracy extends beyond ad tracking. The customer data you work so hard to capture for your marketing efforts is the same data your fulfillment operations depend on. An accurately tracked customer is a valuable asset, but only if their order reaches them without issue. Fixing your ad tracking is a critical first step for customer acquisition. The next step is ensuring the customers you win have a flawless delivery experience, which starts with a correct shipping address. Tacey's [address validation](/address-validation) runs on every order after it is placed, checking for errors that can cause delivery failures. By catching and correcting address issues before they reach your warehouse, you reduce support tickets and protect the relationship with the customer you just paid to acquire. Learn more about how Tacey protects your post-purchase experience and [install it from the Shopify App Store](https://apps.shopify.com/tacey?utm_source=tacey&utm_medium=blog&utm_campaign=fixing-low-meta-capi-event-match-quality-on-shopify-2026-guide). ## Frequently asked questions ### What is a good Event Match Quality score on Shopify? For Purchase events, a score of 8.0 or higher is considered good to excellent. Scores for upper-funnel events like PageView or AddToCart will naturally be lower, often in the 5 to 7 range, because less customer data is available at that stage. ### Why is my Purchase EMQ score higher than my AddToCart score? This is normal and expected. A Purchase event has access to the full customer record, including email, phone, and address, which the customer enters at checkout. An AddToCart event happens earlier, when the user is often still anonymous, so it can only send browser-level data like cookies and IP addresses. ### Will a low EMQ score stop my ads from running? No, a low EMQ score will not stop your ads from being delivered. However, it will reduce the effectiveness of Meta's optimization and attribution systems, which can lead to worse performance and a higher cost per acquisition over time. ### Can I improve my EMQ score without a developer? You can make some improvements without a developer. Start by checking your Shopify data-sharing settings and ensuring they are set to "Enhanced" or "Maximum". Also, enable Automatic Advanced Matching in Meta Events Manager. For more advanced fixes, you may need help from a developer or a specialized tracking app. ### How long does it take to see an improved EMQ score? After you have made corrections to your tracking setup, you should see changes in your EMQ score relatively quickly. A properly configured server-side setup can show strong match rates within 24 hours. It is not a process that should take weeks to show results. ### Does a 10/10 EMQ score guarantee better ad performance? No, a perfect score is not a guarantee of success. While a higher score provides Meta's algorithm with better data to work with, it cannot fix a poor product offer, unconvincing ad creative, or a confusing website. EMQ is a measure of your data plumbing; it is not a measure of your overall marketing strategy. ### Is it possible for my EMQ score to be too high? Some experts argue that a very high score (e.g., 9.3+) might simply indicate an over-reliance on Meta ads for traffic. If a large portion of your purchases comes from users who clicked a Meta ad, they will have a click ID, boosting your score. A healthy business with diverse traffic sources might have a slightly lower score, and that is not necessarily a bad thing.