Meta Pixel isn't firing. What should you check?
Start by confirming whether the pixel script loads at all, then whether events leave the browser, then whether Meta receives them. Most cases come down to one of four things: no install on the page you are testing, a consent setting holding it back, a browser blocker, or an install that never reaches checkout.
Symptom
You open Events Manager and see no recent activity for your pixel, or PageView arrives but Purchase does not. Meta's browser extension shows nothing on your store, or your ads report far fewer purchases than your orders suggest.
The short answer: check three layers in order. Does the pixel code load? Does the browser send a request to Meta? Does Events Manager receive it? The layer where the trail stops tells you where the fault sits.
Possible causes
- The pixel is not installed where you are testing. It may be on the homepage but not on product pages, or in the theme but not in checkout. On Shopify, theme code does not run in the checkout, so purchase tracking has to come from the Facebook & Instagram app or a custom pixel.
- Consent is holding it back. If your cookie banner blocks marketing tags until a visitor accepts, the pixel will not fire for anyone who declines or ignores the banner. That is correct behaviour, not a fault.
- A browser blocker or tracking protection. Ad blockers and some browser privacy settings stop requests to Meta. Your own browser may be the one blocking it.
- Wrong or mixed pixel IDs. The page loads a pixel ID that belongs to a different ad account or an old business, or two different pixels split the events between them.
- A script error. An event call runs before the pixel is initialised, or another script error stops the code from running.
- The Purchase event is incomplete. Meta's pixel reference expects
valueandcurrencywith a Purchase event. A missing or malformed value can make the event unusable for reporting even when it fires.
How to check
- Use a clean browser profile. Turn off ad blockers for the test, or use a fresh profile with no extensions apart from the ones below. Accept all cookies on your banner for the first pass.
- Install Meta's browser extension. Meta's Pixel Helper has been renamed Meta Ads Data Advisor. Open your homepage and a product page and note which pixel IDs it reports and which events.
- Watch the network. Open your browser's developer tools, go to the Network tab and filter for
facebook.com/tr. Each event normally appears as a request with anev=value such asPageViewand anid=value matching your pixel ID. Also check thatfbevents.jsloads fromconnect.facebook.net. - Use Test Events in Events Manager. Go to Events Manager, open your pixel (dataset), choose Test events and enter your store URL. Browse, add to basket, and watch events arrive in real time.
- Repeat with consent declined. Clear cookies, reload, decline marketing cookies and check again. Decide whether what you see matches your consent policy.
- On Shopify, check Customer events. In Shopify admin, go to Settings, then Customer events. Note which app pixels and custom pixels exist and whether they are connected. Then place a test order and confirm a Purchase arrives in Test events.
Illustrative example of a correct browser call, with invented values:
fbq('track', 'Purchase', {
value: 42.50,
currency: 'GBP'
});
What the result means
- No
fbevents.jsand no requests: the pixel is not installed on that page, or a consent tool is blocking it. - Script loads but no
/trrequests: look for console errors, and for a pixel that is loaded but never initialised with an ID. - Requests leave the browser with the wrong
id=: the events go to a different pixel. Find where that ID is set. - Events reach Test events but not the overview: give it time, then check you are looking at the right dataset and business.
A false positive to watch for: browser extensions can miss events sent from inside Shopify's pixel sandbox. Shopify's help on testing custom pixels describes its own Shopify Pixel Helper for that case: in Settings, Customer events, open the custom pixel and click Test. An empty result in one tool is not proof the pixel is missing. Confirm with Test events and a test order before you change anything.
How to fix it
- Missing from pages: install the pixel once, through one method. On Shopify that is usually the Facebook & Instagram app. A custom pixel is the alternative when you need control the app does not give.
- Missing at checkout on Shopify: remove reliance on old checkout scripts. Shopify's help on the Thank you and Order status upgrade explains that non-Plus stores had to move to the new pages by 26 August 2026, and that tracking there runs through app pixels and custom pixels.
- Wrong ID: replace it at the source, then search the theme, tag manager and apps for any other copy.
- Consent: make sure the pixel waits for consent where your policy requires it, and fires as soon as consent is given. Test both paths.
- Server-side gaps: if browser blocking is a big share of your traffic, the Conversions API can add server events. That needs deduplication, covered in Meta duplicate purchases.
This needs a specialist when events fire in one tool and not another, when several apps each add a pixel, or when checkout events depend on a custom pixel.
What not to do
- Don't add a second copy of the pixel "to be safe". It creates duplicates and split data.
- Don't turn off your consent banner to make the pixel fire.
- Don't judge the setup from Ads Manager purchase counts alone. Attribution windows mean those numbers will never equal your orders.
When to request help
If you have checked the three layers and still can't see why events stop, our Google Ads and Meta conversions service checks the browser and server paths, IDs and consent together. Not sure where to start? Get a free check and Mikael will tell you what he can see from your public pages, and what he can't.
Related guides: Meta Conversions API not receiving events, Consent Mode v2 checks, Shopify GTM and custom pixels and the Shopify tracking checklist.
Sources and updated date
- Meta for Developers: Get started with the Meta Pixel
- Meta for Developers: Meta Pixel reference
- Shopify Help Center: Testing custom pixels
- Meta for Developers: Meta Ads Data Advisor, formerly Pixel Helper
- Shopify Help Center: Custom pixels
- Shopify Help Center: Upgrading the Thank you and Order status pages
Last checked against official documentation: 18 November 2026. Platform menus change often, so if a menu name differs from what you see, follow the current official help.
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.