← Guides

How to check if your Meta Pixel is working

Updated 2026-11-22. Sources are listed at the end.

A Meta Pixel can disappear with a site rebuild, a template change or a paused tag in Google Tag Manager. Here is how to check that it is on the page and sending events.

1. Meta's browser extension

Meta Ads Data Advisor (formerly Meta Pixel Helper) is a free extension for Google Chrome and Microsoft Edge. Open your page with it and its side panel shows which pixels it found, whether they loaded, and the events each pixel sent, with errors and warnings.

2. The Test events tab in Events Manager

In Meta Events Manager, open your pixel's dataset, go to Test events, enter your page address and browse the site. Events appear in the tab as they arrive, which also confirms that Meta receives them.

3. The page source and the Network tab

Search the page source for fbq('init' followed by your pixel ID. In the developer tools Network tab, requests to facebook.com/tr are the pixel sending events.

curl -s https://www.example.com/ | grep -o "fbq('init', *'[0-9]*'" | sort -u

If the pixel is installed through Google Tag Manager, it is not in the page source; check the container in Tag Manager instead (see how to tell if your GTM container is installed).

Why a pixel stops working

  • The snippet was dropped from a template during a redesign or migration.
  • The pixel's tag was paused or removed in Google Tag Manager.
  • A consent banner holds it back until visitors agree.
  • The pixel ID changed when an ad account or business portfolio was rebuilt.
  • Your own ad blocker hides it during testing; test in a clean browser profile.

Events sent from a server through the Conversions API do not appear in browser checks; check those in Events Manager.

Checking many client sites?

Lindenkit Tag Watch reads the HTML of up to 5 key pages per site about once a day and emails you when a GTM, GA4, Google Ads, Meta, LinkedIn or TikTok ID disappears or changes, or a GA4 ID looks configured twice, once the change is seen on two consecutive checks. It reads the HTML your server returns, so it cannot see tags that other scripts add later. US$25/month for 5 sites, 14-day trial without a card.

How Tag Watch works What it can and cannot detect

Sources