Meta Pixel Not Detected
Updated
Most often the pixel is installed on a different page than the one the campaign lands on, or consent or a GTM rule stops it from loading. Check the final URL, how the pixel is deployed, the consent state and trigger conditions, and remember that seeing PageView does not prove Lead or Purchase are set up.
Work through the route, deployment and consent layers before deciding that the pixel is missing.
A scanner or browser test may fail to observe Meta Pixel for several reasons: the final landing page differs from the page you configured, consent delays the tag, GTM rules block it, or only an action-triggered event is expected. Detection should be interpreted in the context of the actual funnel.
What to check
1. Verify the final landing page
Confirm the campaign does not redirect to a page where the pixel was never installed.
2. Check the deployment method
Determine whether Meta Pixel is hardcoded, loaded through GTM or injected by another platform.
3. Check consent
If advertising storage requires consent, test both the initial state and the state after the relevant consent action.
4. Check triggers and conditions
GTM triggers, hostname rules, environments and script blockers can prevent the pixel from loading on specific pages.
5. Separate Pixel presence from event coverage
Seeing the base pixel or PageView does not prove Lead, Purchase or other business events are configured.
6. Check for funnel-step gaps
The pixel may exist on the pre-lander but disappear on the offer, checkout or external destination.
What you see and what it usually means
No request to fbevents.js
The base code never loads on this page. Either it is not installed on the final URL, or consent, a tag-manager rule or a blocker stops it.
fbevents.js loads, but no PageView request follows
The library is present but the pixel is never initialised or the event is never sent. Look for a request to facebook.com/tr and read its id value.
The pixel shows a different ID than expected
The page belongs to another setup, often an agency account or a previous install. Events are sent, just not to the dataset your campaign optimises on.
Other people see it, your scan does not
A browser checker reports what was observable in one page load and consent state. An installed Meta or Facebook Pixel can appear not detected when consent, a delayed GTM trigger, redirects, blockers or a required interaction prevent it from loading. Verify the exact final campaign URL and expected Pixel ID before reinstalling it.
A typical case
Worked verification (illustrative): a campaign reaches quiz.example.com, while the Pixel is installed only on www.example.com. Test the exact campaign route in a clean browser profile, record the advertising-consent state and filter Network for fbevents.js and facebook.com/tr. A library request alone does not prove PageView was sent. Where a browser event request is present, check the expected Pixel ID and event name, then confirm receipt in Meta Test Events. Repeat after installing the reviewed tag on the quiz template, using the same route and permitted consent state. Test a successful conversion separately: PageView does not verify Lead. If the integration uses only server-side events, browser absence is expected and the server delivery must be checked by the integration owner.
Before you call it fixed
- Correct final URL
- Pixel deployment method known
- Consent state tested
- GTM/trigger conditions reviewed
- Base signal checked separately from conversion events
- All important funnel steps reviewed
Check the production URL
A correct configuration on paper can still fail after redirects, deployment or consent logic. Use the exact URL your campaign will send traffic to.
Check a campaign URLVerify the signal directly
Related troubleshooting guides
Common questions
Why does Meta Pixel Helper show nothing?
The extension only reports what loads in your browser on that page. If the pixel is held back by the consent banner, blocked by another extension, or installed on a different step of the funnel, it has nothing to show.
Can the pixel work if it is not in the page source?
Yes. A pixel injected by Google Tag Manager or another platform does not appear in the raw HTML. Check the network requests after the page has loaded instead of the source code.
Does the Conversions API replace the pixel?
It can send the same events from the server, and those never appear in the browser. If a site uses only the Conversions API, a browser-based check will not detect a pixel even though Meta receives events.
Scan the full campaign route.
See where the click lands, what survives the redirect chain and which supported tracking signals are visible on the final page.