How to Tell If Your Meta Pixel Is Broken on Shopify
Open Meta Events Manager, select your dataset under Data Sources, and look at how recently each event fired. If PageView or ViewContent shows hours of silence while your store has traffic, your pixel is broken. Confirm it in two more places. First, open the Test Events tab, visit your own storefront in another window, and watch whether your visit appears in the live feed. Second, load a product page with your browser's developer tools open and filter the Network tab for requests to facebook.com. A working setup loads the fbevents.js script and then sends requests to the /tr endpoint carrying event names like PageView and ViewContent. If the script loads but no /tr requests leave the page, a consent tool or a theme change is usually blocking the calls. If browser events look fine but purchases are still missing, the server side Conversions API path needs its own check.
The five minute manual check
Start where the damage shows: Events Manager. Under Data Sources, your dataset lists every event Meta has received and when it last arrived. Recency is the tell. A healthy store with steady traffic shows PageView arriving continuously; a broken one shows a clean cutoff, often dated to the day a theme or app changed.
The Test Events tab gives you a live feed scoped to your own browsing. Visit your storefront, click into a product, and add something to cart. Each action should appear within seconds. This isolates your session from the noise of real traffic, so you can see exactly which events your setup produces and which are missing.
The Network tab is the ground truth for the browser side. With developer tools open, a working page loads fbevents.js from Meta's CDN and then issues requests to facebook.com/tr with an ev parameter naming the event. No /tr requests means nothing is being sent, no matter what any app dashboard claims.
Failures that hide from a quick look
The dangerous breakages are partial. The pixel fires on the home page but not after checkout, so campaigns keep spending while purchase signal disappears. Delivery continues, reported return on ad spend decays, and nothing raises an alarm because PageView still looks alive.
Watch for indirect symptoms: retargeting audiences that stop growing, a widening gap between orders in Shopify and Purchase events in Events Manager, and Meta reporting far fewer conversions than your store actually took. Each of these usually means one specific event broke while the rest kept firing.
Common Shopify specific causes
Theme changes are the leading cause: pixel snippets pasted into theme code do not follow you to a new or duplicated theme, and app embeds default to off when a different theme is published.
Consent management is the second: many banners block tracking scripts until a visitor accepts, and a misconfigured banner blocks them for everyone, silently.
App conflicts are the third: two apps installing the same pixel produce duplicate events, and deduplication failures make Meta discard events it should have counted. Migrations, such as moving to a new checkout, also change where tracking code is allowed to run, which can strand old code that no longer executes.
Set up standing verification
A manual check tells you the state right now; it cannot watch the 3am theme publish. Standing verification means something visits your storefront on a schedule like a shopper, confirms the pixel loads and produces tracking requests, reads Meta's own Dataset Quality metrics with your token to confirm events are received and matched, and alerts you only on confirmed breakage with the evidence attached.
That is exactly what PixelSentry does for Shopify merchants: a synthetic crawl every 6 hours, Dataset Quality polling every 2 hours, and a one button test event to prove the Conversions API receive path end to end.