Meta Pixel not firing PageView: how to find out and fix it

A Meta Pixel that is on the page is not the same as a Meta Pixel that works. The pixel must send a PageView event to Meta on each load. If it loads and sends nothing, your ads optimise against no data. This check looks for the PageView request itself.

Why it matters

Meta uses pixel events to learn who buys and to find more people like them. When the event never arrives, campaigns run on guesses, retargeting audiences stay empty and reported conversions look lower than they are. The store owner sees a healthy-looking setup because the script is installed.

The failure is silent. No error appears on the page, and checks that only look for the script pass.

What the audit looks at

The audit checks that your Meta Pixel actually sends a PageView event, not only that its script is on the page.

What usually causes it

• A snippet pasted without the PageView line, which loads the library and reports nothing
• Two pixel installs fighting each other, one in the theme and one through a sales channel
• A consent banner that blocks the pixel permanently and not only until consent is given
• A caching or optimisation plugin that defers or removes the pixel script

How to fix it

Repair the pixel so it sends PageView on every page load. The effort is medium, a theme or template edit that takes an afternoon.

1. Install Meta Ads Data Advisor (the Chrome extension formerly called Meta Pixel Helper) and load the page -- it names the reason the event did not fire.
2. Check the pixel snippet includes the fbq("track", "PageView") line; a snippet pasted without it loads the library and reports nothing.
3. If a consent banner is blocking it, confirm the pixel is allowed to fire after consent is granted, not permanently suppressed.
4. Verify in Meta Events Manager > Test Events that a PageView arrives when you load the page.

On Shopify

1. Open Settings > Customer events and confirm the Meta pixel app is connected and its pixel ID matches the one in Events Manager.
2. Remove any second copy of the pixel pasted into theme.liquid -- a duplicate snippet often breaks the first one.
3. If you use the Facebook and Instagram by Meta sales channel, reconnect it; a lapsed token stops events without removing the script.
4. Confirm in Meta Events Manager > Test Events that PageView arrives on a normal storefront visit.

On WooCommerce

1. Check the Meta for WooCommerce plugin is active and the pixel ID under Marketing > Facebook matches Events Manager.
2. Disable other pixel plugins one at a time -- two plugins injecting the same pixel is the usual cause.
3. If a caching or optimisation plugin defers JavaScript, exclude the fbevents.js script from deferral.
4. Confirm in Meta Events Manager > Test Events that PageView arrives on a normal storefront visit.

How to check it yourself

1. Install the Meta Pixel Helper or Meta Ads Data Advisor extension in Chrome and load your home page.
2. Open Meta Events Manager, choose Test Events, enter your store URL and confirm that a PageView appears.
3. Repeat on a product page, because some setups load the pixel only on certain templates.

Frequently asked questions

Why does Pixel Helper show my pixel but Events Manager shows no events?

The helper shows that the pixel is present. Events Manager shows what Meta actually received. A blocked request, an unconfirmed domain or a consent setting can sit between the two.

Does a missing pixel fail this check?

No. A store that does not run Meta ads can leave the pixel out and still pass. The check fails only when a pixel loads and no PageView follows.

Related checks

• Google Analytics 4 not collecting data: how to check and fix it
• Duplicate Google Analytics 4 tracking: how to find double counting
• Cookie consent banners for online stores: do you need one?

Further reading

• Meta: Pixel Helper troubleshooting