Marketing9 min read
Meta pixel not firing on Shopify? 5 causes and how to fix them
admin
Shopify shows orders all day. Events Manager says no Purchase events in the last 7 days. Meta's algorithm is now optimising your budget on half a picture, and nobody has noticed.
If your Meta pixel is not firing on Shopify, work through five likely causes in a fixed order. This guide walks through each one with the exact admin paths, then shows how to test the fix and how to catch the next break the same morning.
A pixel that is not firing shows up as one of five symptoms, and each symptom points to a different cause. Match yours first, so you fix the right thing.
| What you see | Most likely cause | Go to |
|---|---|---|
| Pixel Helper shows "no pixel found" on the storefront | App connection, data sharing or consent | Causes 1 and 2 |
| PageView fires, but AddToCart or Purchase never arrives | Checkout or Thank you page setup | Cause 4 |
| Server (CAPI) events arrive, browser events are dead | Pixel base code not loading, or consent | Causes 1 and 2 |
| Purchases counted twice, or far more in Meta than Shopify | Duplicate pixel code or broken deduplication | Causes 3 and 5 |
| Everything worked until a theme or checkout change | Old code removed or left behind | Causes 3 and 4 |
All five appear again and again in Shopify Community threads, usually from founders who add, "there definitely have been sales every day."
Check the app first, because it controls both the browser pixel and the Conversions API. A wrong pixel ID, data sharing switched off or the Standard level alone can each leave Meta with missing events.
Go to Sales channels > Facebook & Instagram > Settings > Data sharing settings in Shopify admin. Check three things:
One more detail worth knowing: the order value Shopify sends is the order total, including duties, taxes and discounts. If Meta's purchase value looks higher than your net revenue, that is expected, not a bug.
Yes, the Shopify cookie banner can block the Meta pixel. In any region where your cookie banner is active, Shopify collects non-essential data only after the visitor gives consent, and Shopify pixels follow that consent.
Open Settings > Customer privacy and check which regions the banner covers. On new stores Shopify switches it on automatically for UK and EEA visitors and leaves it off elsewhere by default. If your team (or an app) widened it to all regions, Indian visitors who ignore the banner will not fire the browser pixel.
Two things trip brands up:
Several merchants in one long thread report that fixing the cookie banner settings got their pixel firing again. That is community advice, not an official Shopify statement, but it costs two minutes to check.
Old Meta pixel code left in your theme can double-count or break events. Shopify's own Meta pixel guide says to remove any Meta pixel code you added by hand once the app pixel is set up, because multiple pixels cause "duplicate or incorrect data in your reports."
To find it, go to Online Store > Themes > Edit code, open theme.liquid and search for fbq( or your pixel ID between the <head> tags. Also check:
Theme migrations are the classic trigger. The new theme drops a snippet the old one had, or the old snippet comes along and doubles every event. Meta's own setup errors list puts duplicate pixel code at the top for a reason.
If Purchase stopped firing in 2025 or 2026, check the Thank you page upgrade first. Any pixel or script that lived in the old Additional scripts box stopped running once the store moved to the new Thank you and Order status pages.
The timeline, from Shopify's upgrade guide:
So if Purchase died around late August and your store had pixel code in Additional scripts, you have found your cause. Move tracking to the Facebook & Instagram app (or another app pixel) under Settings > Customer events.
If you use a custom pixel instead, know its limits. Shopify runs custom pixels in a "Lax sandbox", warns that not all pixel functionality works there, and does not support custom pixels itself (source). That is also why browser extensions can show "no pixel found" at checkout even when events reach Meta: the pixel runs inside a sandboxed frame. Test checkout events with the tools in the testing section below, not by eye.
Pixel and Conversions API events deduplicate only when both copies of an event share the same event ID and the same event name. When they don't, Meta treats them as two events and your purchase count inflates.
Meta's rule is precise:
eventID must match the server event's event_id.Purchase and Purchase).The native app handles this for you. The risk comes from mixed setups: the app sends CAPI events while a GTM container or a second app sends browser events with its own IDs. Pick one owner for each event, and turn the other off.
Use three tools, in this order, and run one real journey from product page to purchase.
content_ids, value or currency (Meta).| Tool | Best for | Blind spot |
|---|---|---|
| Meta Ads Data Advisor | Storefront pixel, duplicates, missing parameters | Sandboxed checkout pixels |
| Events Manager Test events | Browser vs server source, event IDs, Purchase | Needs a real or test order |
| Shopify Pixel Helper | Customer events and custom pixels, consent | One custom pixel at a time |
Use a normal browser window. The Shopify Pixel Helper does not work with stores in private mode or headless storefronts.
Compare yesterday's Shopify orders with yesterday's Meta purchases every morning, by product, not just in total. A pixel rarely breaks everywhere at once; it breaks on one template, one checkout step or one set of SKUs, and the account total hides it.
Here is why speed matters. Say a brand spends ₹5L a month on Meta (an illustrative number) and Purchase stops reporting for 4 days. That is about ₹67,000 of spend optimised against missing signals, plus ad sets that look like losers and get paused while they are actually selling.
A cookware brand we work with saw exactly this pattern. Its pixel broke on 3 hero SKUs after a theme migration, and Clevrr AI caught it the same morning. Clevrr AI is an AI performance marketer for D2C brands: it reads Shopify orders and Meta ad data side by side every day and runs root cause analysis when a number moves, instead of waiting for someone to open Events Manager. If your Meta and Shopify numbers already disagree, our guide on why Meta purchases don't match Shopify orders covers the reconciliation side.
When the Meta pixel is not firing on Shopify, work in order: app and data sharing, cookie banner, duplicate theme code, the Thank you page upgrade, then deduplication. Test with Meta Ads Data Advisor, Events Manager and Shopify Pixel Helper on one real purchase. Then check Meta against Shopify every morning, by SKU, so the next break costs you a day, not a month.
If you would rather have that morning check done for you, start free with 500 credits.
It usually means the pixel never loaded in your browser. Check that the Facebook & Instagram app has data sharing on with the right pixel, accept the cookie banner, and turn off your ad blocker. At checkout, a sandboxed app or custom pixel can also hide from the extension, so confirm with Events Manager Test events instead.
It can. Where your banner is active, Shopify collects non-essential data only after the visitor consents, and Shopify pixels follow that choice. Check Settings > Customer privacy to see which regions the banner covers, and make sure any third-party consent app syncs consent back to Shopify. Otherwise visitors who ignore the banner never fire the pixel.
Yes, in most setups. Shopify's Enhanced and Maximum data sharing levels use the Conversions API and the Meta pixel together. The server events survive ad blockers, while the browser pixel captures on-site behaviour. Meta then deduplicates the two copies when they share the same event ID and event name within 48 hours.
Join hundreds of D2C brands using Clevrr AI to automate their growth and efficiency.
Join 500+ D2C founders using Clevrr AI to automate their operations and scale faster.
Get Started Free