Meta Pixel Not Detected
A scanner or browser test may fail to observe Meta Pixel because the final landing page differs from the configured page, 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 this page covers
- Verify the final landing page before investigating the pixel itself.
- Identify whether Meta Pixel is hardcoded, loaded through GTM or injected by another platform.
- Test the relevant consent state and review triggers, hostname conditions and script blockers.
- Separate the base pixel or PageView from Lead, Purchase and other conversion events.
- Check every important funnel step because tracking can disappear after a redirect to an external destination.