Meta Pixel Not Firing: What to Check First
When the Meta Pixel is not firing, no browser event reaches Meta and your ads lose the conversion signal they rely on. The break is almost always in one of a few places: the base code is missing or blocked, the Pixel ID is wrong, a trigger never fires or consent stopped the tag. Work through the flow in order and you will find it quickly.
Table of Contents
- 01.The event flow you are debugging
- 02.What to check first
- 03.Is the base code present
- 04.Is the Pixel ID correct
- 05.Is the trigger firing
- 06.Consent and browser restrictions
- 07.How to test it
The event flow you are debugging
A browser event follows a fixed path. The page loads, the Pixel base code loads, the Pixel initializes with the correct ID, an event fires and Meta receives the event. If any step in that chain fails, nothing reaches Events Manager. Knowing which step broke tells you what to fix.
| Step | What happens | What breaks it |
|---|---|---|
| 1. Page loads | HTML and scripts begin loading | Page errors, blocked scripts |
| 2. Base code loads | fbq script is present and runs | Missing code, wrong placement |
| 3. Pixel initializes | fbq('init', PIXEL_ID) | Wrong Pixel ID, duplicate init |
| 4. Event fires | fbq('track', 'EventName') | Trigger never fires, consent blocks |
| 5. Meta receives | Network request reaches Meta | Network blocked, ad blocker |
What to check first
- Confirm the Pixel base code is actually on the page, not just in your tag manager.
- Confirm the Pixel ID in the code matches the dataset in Events Manager.
- Check whether the event has a trigger that should fire it.
- Check whether a consent banner is blocking the tag before consent is given.
- Open browser devtools and look for the fbq network request.
Is the base code present
The Pixel needs its base code to run before any event can fire. If you load the Pixel through Google Tag Manager, the base code lives in a tag that must fire on all pages. If it is hardcoded into the site theme, confirm it is in the head or body of every page template, not just the home page. A common failure is the base code being present on the home page but missing from a subdomain or a separately templated checkout page.
Look at the page source or use the browser console to check whether fbq is defined. If fbq is undefined, the base code never loaded. That single check separates a code problem from a trigger problem.
Is the Pixel ID correct
The Pixel ID tells Meta which dataset to send the event to. A wrong ID means the event fires locally but lands in someone else's dataset or nowhere useful. Copy the ID directly from Events Manager and compare it character for character with what is in your code or tag. A transposed digit is enough to break everything while looking correct at a glance.
Is the trigger firing
If the base code loads and the ID is right, the next question is whether the event trigger fires at all. A PageView trigger should fire on every page. Custom events like Lead or AddToCart need a specific trigger, usually a page view of a thank-you URL or a click on a button. If the trigger condition is too narrow or points at the wrong URL, the event never fires even though the Pixel is healthy.
Use the Meta Pixel Helper browser extension or the Test Events tool in Events Manager to see whether the event fires when you perform the action. If nothing appears, the trigger is the likely culprit. This is covered from the angle of events that fire locally but never appear in Events Manager in the guide on Meta Pixel firing but events not showing.
Consent and browser restrictions
A consent banner can hold the Pixel back until a visitor accepts. If your tag is set to wait for consent and the banner is misconfigured, the Pixel never initializes for users who do not click accept. Browser tracking restrictions and ad blockers can also stop the network request from reaching Meta even when the code runs. These are not bugs in your implementation, but they explain why a Pixel that works in your test still misses real customer events.
How to test it
- 1.Open the page in a normal browser window with no ad blocker.
- 2.Open devtools and go to the Network tab, then filter for the Pixel endpoint.
- 3.Load the page and confirm a request is sent to Meta.
- 4.Use Test Events in Events Manager with the same browser session to confirm the event appears.
- 5.If the event is missing, check fbq in the console, then the trigger, then consent.
Frequently Asked Questions
Why does my Meta Pixel work in Test Events but not for real visitors?
Test Events uses your own controlled browser session, which usually has no ad blocker and has accepted consent. Real visitors may have ad blockers, stricter browser settings or may not have accepted your consent banner. The guide on Meta Pixel working in testing but missing real events covers this gap in detail.
Can a wrong Pixel ID still fire events locally?
Yes. The event fires in the browser regardless of the ID, but it is sent to the wrong dataset. Always compare the ID in your code with the one in Events Manager character for character.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Meta Pixel Firing but Events Not Showing in Events Manager: How to Diagnose It
A local fire only proves the code ran. Use Test Events against the correct dataset to confirm Meta actually received the event before you start changing tags.
Meta Pixel Works in Testing but Real Customer Events Are Missing: What Can Cause It?
A working test only proves the tag fires in ideal conditions. Real visitors have ad blockers, stricter browsers and different consent choices. Reproduce those to find missing events.
Meta Pixel Firing Twice: How to Find and Fix Duplicate Events
Double firing is usually two installations, not one broken tag. Find both sources using the network initiator column and remove one before changing trigger logic.