Check the extension name and the result you are reading
Meta's official Chrome listing now names the extension Meta Ads Data Advisor, formerly Meta Pixel Helper. The listing describes diagnostic tools alongside setup and change features.
Check the publisher and permissions in the linked official listing. Reading a diagnostic result and authorizing a setup change are separate actions. The checks below do not require installing an extension.
What a missing pixel result tells you
If a diagnostic reports no pixel on a page, record the exact URL, test time and consent choice. It describes that observation, not every page or visitor.
A tag can be delayed by consent, loaded through GTM, blocked by a browser, or absent from a particular template. A server-side integration is another separate path that a browser check cannot verify.
Free tracking check
See what’s visible on a real site.
Run a free browser-based scan. No login or installation needed.
Run a free checkInspect browser requests before changing the installation
Page source can omit scripts added later by GTM or another integration. Finding no fbq call in the original HTML is not enough to conclude that the pixel is absent.
Use the published campaign page in your own browser. Keep the consent choice with the result.
- Open DevTools > Network and reload the page. Inspect requests containing fbevents.js or facebook.com/tr.
- Compare any visible pixel ID and event name with the intended setup. A request is evidence of a send attempt; it does not establish receipt or attribution in Meta.
- Record blocked or failed requests. Compare another relevant page template with the same test conditions before deciding whether the problem is page-specific.
- Ask the owner which native integration, GTM tag or custom code owns the pixel. Review that connection before adding another copy.
Use the public checker as another observation
TrackCanary looks for public browser evidence such as connect.facebook.net, fbevents.js, fbq calls and facebook.com/tr requests on the pages it can read. It does not connect to Meta or inspect a server-to-server connection.
Review the report's page scope and loading limits. A missing signal from an incomplete scan needs review. Use the saved evidence to choose a manual check; it does not establish that a whole site has lost tracking.
Test the action and account receipt separately
With the site owner, choose one expected event, such as Lead after an accepted form submission. Use an authorized test environment and non-personal test data. Compare that action with the event shown in Meta Events Manager, using the intended pixel ID and test time.
A visible base pixel does not confirm that action. Record the browser observation and account result separately, including what remains unknown. Repeat after a theme, form, GTM or consent change. One failed request alone is not evidence of a permanent break.
Next step
Start with the free Meta Pixel Checker
Paste your storefront URL and see whether the Meta Pixel appears to load across your public pages — free, no login, no extension. Use the result to decide whether you need a developer handoff or ongoing monitoring.