You check your Meta Events Manager and the numbers look off. Purchases aren't showing up. Add to Cart events are missing. But your store is getting orders, so what's going on?

This is one of the most frustrating situations in e-commerce marketing. When your pixel stops tracking key events, your ad platform loses the signal it needs to optimize campaigns. Meta starts making decisions based on incomplete data. Your ROAS looks worse than it really is, or sometimes better. Either way, you're flying blind.

Most pixel tracking problems follow predictable patterns which is a good news. We’ll walk you through the common causes and how to fix them, step by step.

Understanding the Core Problem First

Before you start changing things, it helps to understand what type of problem you're actually dealing with. There are two very different failure modes:

The event is not firing at all. No data leaves the browser. The pixel script may be blocked, missing, or broken on that specific page or action.

The event fires but does not show up where you expect. The data leaves the browser, but it gets suppressed, deduped, or misattributed on the receiving end.

These two problems look similar on the surface (missing data) but require completely different fixes. Treating one like the other wastes time.

A quick way to tell them apart: use the Meta Pixel Helper Chrome extension and the Test Events tool in Meta Events Manager. Perform a controlled test, view a product, add it to cart, and complete a purchase, and watch what fires. If the Pixel Helper shows nothing, you have a firing issue. If it shows the event but Meta Events Manager does not count it, you likely have a deduplication or attribution issue.

Common Reasons Add to Cart Events Go Missing

Add to Cart tracking breaks more often than most people expect, and usually for one simple reason: "add to cart" is not always a single, standardized action across a Shopify store.

Consider how many ways a customer can add a product to a cart:

• The main product page button
• A quick-add button on a collection page
• A slide-out cart drawer
• A bundle or upsell widget
• A subscription app component

Each of these can be built differently. If your pixel is only listening for one type of add-to-cart trigger, the others will go untracked.

Theme conflicts and custom JavaScript are also a common culprit. After a theme update, the element your pixel was listening to may no longer exist, or it may behave differently. This is especially common with AJAX-based add-to-cart setups that update the cart without reloading the page.

Double installation is another major issue. If your pixel is installed through a Shopify app and also injected via a theme file or Google Tag Manager, you may get suppression or deduplication behavior that makes events appear to vanish. Pick one installation method and remove the others.

Why Purchase Tracking Is More Fragile

Purchase tracking sits at a different layer of your store than Add to Cart, and that makes it more vulnerable to breaking.

The confirmation step, your "thank you" page, is not always under your full control. Several factors can interfere with tracking:

Payment redirects. Some payment methods take customers off your domain briefly before returning them. If your tracking depends on a script loading on a specific URL, a redirect can break the chain. Test your tracking across multiple payment methods if you support more than one.

Post-purchase apps. Upsell or post-purchase offer apps can alter the checkout flow in ways that delay or skip the standard order confirmation behavior your tracking expects.

Shopify Checkout Extensibility. This is a significant and often overlooked issue. Shopify is phasing out checkout.liquid and the Additional Scripts section of the Order Status page. If your pixel was injected there, those scripts will stop firing after migration. The replacement is Shopify's Customer Events and Custom Pixels system, but you cannot simply copy and paste old scripts into a Custom Pixel because they run inside an iframe and may not behave as expected.

If you migrated to Checkout Extensibility and your Purchase events dropped around the same time, this is almost certainly the reason.

The Privacy Barrier (Ad Blockers and Browser Restrictions)

Even a perfectly configured client-side pixel will miss some conversions. This is not a bug; it is an unavoidable reality of browser-based tracking in 2025.

Safari's Intelligent Tracking Prevention (ITP), Firefox's Enhanced Tracking Protection, and ad blockers all interfere with third-party scripts. The result is undercounted events, especially for users on Apple devices or those with privacy-conscious browser settings.

Here is a comparison of the two primary tracking methods and how they hold up against these barriers:

If you are running serious paid acquisition and relying only on client-side pixel data, you are working with an incomplete picture. Server-side tracking via the Meta Conversions API fills the gaps that browser restrictions create.

Step-by-Step Troubleshooting Guide

Use this checklist in order. Do not start making changes until you have identified exactly where things are breaking.

1. Reproduce the problem in a controlled environment.

Open a private browser window. Disable all extensions. Clear site data. Perform the full customer journey yourself: view a product, add to cart, start checkout, complete a test purchase if possible. Document exactly which step fails.

1. Check for duplicate installs.

Look in your Shopify theme files, your app list, and Google Tag Manager (if you use it). If the same pixel is installed in more than one place, that is your first thing to fix. One source of truth only.

1. Test Add to Cart from every entry point.

Product page, quick-add button, cart drawer, any upsell widget. If it fails in one place but not others, you have a wiring issue specific to that component, not a global pixel problem.

1. Check your Checkout Extensibility status.

If you are on Shopify Plus and have migrated (or are being migrated) to Checkout Extensibility, confirm that your pixel is set up through Shopify's Customer Events, not the old Additional Scripts section.

1. Test across payment methods.

Complete a purchase using at least two different payment methods, if available. If tracking only breaks for one method, the issue is almost certainly related to that payment provider's redirect behavior.

1. Review your deduplication setup.

If you are using both the Meta Pixel and the Conversions API, both must send the same event_id and use the same event_name (case-sensitive) for deduplication to work. A mismatch here causes either double-counting or event suppression. Check your Events Manager Diagnostics tab for deduplication warnings.

1. Validate using Meta's native tools.

Use the Test Events tool in Meta Events Manager to see a live feed of events Meta receives. Use the CAPI Tester to validate server-side events separately. Cross-reference both to confirm alignment.

Solutions and Best Practices

Once you have identified the issue, here is how to think about fixing it properly.

• For theme/wiring issues with Add to Cart - work with your developer to ensure your tracking listens to all cart-add entry points, not just the main product page form. If you use a cart app or upsell tool, test tracking with that app disabled to isolate the problem.
• For Purchase tracking gaps - move toward a server-side implementation or use a platform-native tracking solution that is built specifically for Shopify's checkout flow. Custom scripts injected into checkout settings are fragile across payment redirects and platform updates.
• For browser blocking - implement the Meta Conversions API alongside your pixel. This is not optional if you are running significant ad spend. The pixel gives you real-time behavioral signals; CAPI ensures your conversion data reaches Meta even when browsers block client-side scripts.
• For deduplication issues - establish a single event_id source of truth, generated once per event and passed to both the pixel and CAPI. Standardize your event names using Meta's standard event names (Purchase, AddToCart, etc.) in both implementations. Check Events Manager weekly for deduplication rate warnings.

The realistic definition of "done" here is not perfection. It is consistency. Add to Cart fires across all primary entry points. Purchase fires for your main payment methods. You have one clean installation path with no mystery duplicates. Your test results are repeatable.

A Note on Klaviyo Data and Retention Marketing

Fixing your pixel gets your ad attribution back on track. But the customer data you collect after that first purchase is just as important for long-term revenue.

If you are running Klaviyo for email automation and have gaps in your event data, you likely have the same problem in your flows: incomplete signals leading to missed revenue.

This is exactly the kind of problem that Aimerce Agents, an AI-powered Klaviyo flow audit tool and Klaviyo Chrome extension, was built to address. The AIM Chrome extension for Klaviyo surfaces hidden analytics like LTV, AOV, and active subscriber percentages that Klaviyo does not show you by default. It also automates Klaviyo billing reviews, runs flow audits, and helps agencies manage multiple Klaviyo accounts without the usual manual overhead.

Since launch, Aimerce Agents has helped save ecommerce brands more than $30,000 per month in unnecessary Klaviyo costs, simply by catching billing overcharges and automating account management tasks. For DTC brands and Klaviyo agencies looking to speed up Klaviyo setup, audit flows faster, or bulk create Klaviyo segments across multiple clients, it is worth a look.

Fix the Signal, Then Scale

Bad tracking does not just hurt your reporting. It hurts your actual ad performance. Meta's algorithm optimizes on the conversion signals you send it. If those signals are incomplete, wrong, or delayed, the algorithm makes poor decisions and your results suffer accordingly.

The path forward is straightforward: confirm what is actually missing, remove duplicate installs, align your Shopify tracking with Checkout Extensibility, and layer in server-side tracking for the events that matter most.

Clean data is not a nice-to-have. It is the foundation that everything else, your bidding, your audiences, your ROAS, sits on top of.

Start with the checklist above. Run the tests. Fix what you find. Then check back in a week and see what your numbers look like.