Meta Pixel Helper Is Now Meta Ads Data Advisor: How to Check Your Pixel, and a Script That Checks Many Pages at Once
Meta's free Pixel Helper extension has a new name, new permissions and new automation features. If yours was switched off, here is how to turn it back on, how to read what it shows, and a free script that checks whether the Pixel loads on every page of a site.
Meta Pixel Helper, the free Chrome extension for checking a Meta Pixel, is now called Meta Ads Data Advisor; the Chrome Web Store listing shows version 5.15.1, updated Nov. 16, 2026, and more than 3,000,000 users.
If your Meta Pixel Helper was deactivated, Meta's instructions are to turn it back on at chrome://extensions/, accept the new permissions and reload your open pages.
Data Advisor still shows the badge with the number of Pixel events on a page, and labels each Pixel and event as Active, Warning, Inactive or Error, with event details such as value and currency.
Meta's documentation says custom conversions and some button-click events may not show in Data Advisor, so the test events tool in Events Manager is the place to confirm those.
Our free script loads a list of pages in a headless browser and reports which Meta Pixel IDs load on each one, a quick way to find templates where the Pixel is missing after a site change.
Meta Pixel Helper, the free browser extension advertisers use to check that a Meta Pixel is working, is now called Meta Ads Data Advisor. Meta's developer documentation describes it as "formerly Meta Pixel Helper", and the Chrome Web Store listing, under the same extension ID as before, showed version 5.15.1, updated November 16, 2026, with more than 3,000,000 users when we checked on Nov. 17.
It still does the old job: it shows which Pixels load on a page and which events they send. It also does something new: it can set up the Pixel and Conversions API for you on Google Tag Manager, Shopify, Salesforce, HubSpot and WooCommerce, with your approval at each step. This guide covers the checking side, which is what most people search "meta pixel helper" for.
Where did Meta Pixel Helper go?
Nowhere: it was renamed. If you had it installed, Chrome updates it in place and the toolbar icon now opens a side panel called Meta Ads Data Advisor. The listing says existing users don't need to reinstall.
What changed is what it asks for. Meta's documentation lists three permissions: access to the page debugger, "Read and change all your data on all websites", and managing your tab groups. Chrome switches an extension off when an update asks for more than you approved, which is why some people now find the old Pixel Helper deactivated.
How do you turn Meta Pixel Helper back on?
Meta's steps for a deactivated install:
In Chrome, go to chrome://extensions/.
Find the extension, now listed as Meta Ads Data Advisor.
Turn on its switch.
Review and accept the updated permissions, then click Add extension.
Reload any pages you want to check.
To install it fresh, search for Meta Ads Data Advisor in the Chrome Web Store and click Add to Chrome, or use the Microsoft Edge Add-ons listing and click Get. It works only in Chrome and Edge. You don't have to log in: Meta says basic Pixel detection and troubleshooting work while logged out; the automated setup needs a Facebook profile and admin access to the ad account.
Our view on the permissions: an extension that can read and change data on every site is a lot to give any company, Meta included. If you only need to check Pixels, install it in a separate Chrome profile that you use for testing, not the profile where you're signed in to your bank, email and client accounts.
How to check if your Meta Pixel is working
Open the page with the Pixel in Chrome or Edge.
Turn off your ad blocker for that site. Meta says blockers can stop the extension from seeing Pixels and events.
Look at the icon: a badge with a number means a Pixel is on the page and that many events fired. No badge means no Pixel was found.
Click the icon to open the side panel, then click the Pixel to see its events.
Do the action you want to measure, such as adding a product to the cart, and check that the event (here AddToCart) appears and shows as successful.
Click Show all events to see every event across your browsing session, which is how you follow a checkout across several pages.
Each event shows its details: content IDs and types, the URL it fired on, Advanced Matching data, and parameters such as value and currency.
What do the statuses mean?
For each Pixel, Data Advisor shows one of three statuses, in Meta's words:
Each event gets its own status: Active, Inactive, Warning (an issue that may affect performance), Error (a critical problem such as blocked parameters, duplicate events or a compliance violation) or Auto-detected (Meta found the event from activity on the site, without code). A Pixel can be Active while one of its events has a warning, so click into each event.
What errors does Meta Pixel Helper flag?
The common setup problems in Meta's documentation:
Duplicate Pixel code on one page.
Base code outside the <head>, which Meta says can lead to missed tracking.
More than one conversion event per page, unless the extras come from actions like button clicks.
An iframe, tag manager or privacy tool blocking the Pixel.
Missing parameters such as content_ids, value or currency on shopping events.
When should you use Events Manager instead?
Meta says custom conversions and some advanced events may not appear in Data Advisor, and button-click events may not be detected unless they reload the page or call the Pixel directly. For those, use the test events tool in Events Manager. Meta's Pixel setup guide also says a page load should record a PageView in Events Manager; if it doesn't appear, wait a few minutes and refresh.
A script that checks the Pixel on many pages at once
The extension checks one page at a time. After a redesign, a theme change or a new tag manager setup, the question is usually wider: does the Pixel still load on every template? This Node.js script loads a list of URLs in a headless browser and reports, for each one, whether Meta's Pixel library loaded, which Pixel IDs it loaded, and whether fbq('init') appears more than once in the page.
check-meta-pixel.mjs
// check-meta-pixel.mjs: load pages in a headless browser and report whether// the Meta Pixel loads on each one, which Pixel IDs it loads, and whether the// base code appears more than once in the HTML.// Usage: node check-meta-pixel.mjs <url> [more URLs]// Needs Playwright: npm i playwright && npx playwright install chromiumimport { chromium } from 'playwright';const urls = process.argv.slice(2);if (!urls.length) { console.error('Usage: node check-meta-pixel.mjs <url> [url...]'); process.exit(1); }const browser = await chromium.launch();for (const url of urls) { const page = await browser.newPage(); let library = false; const pixels = new Set(); const events = []; page.on('request', req => { const u = new URL(req.url()); if (u.hostname === 'connect.facebook.net' && u.pathname.endsWith('/fbevents.js')) library = true; // Each Pixel the page starts fetches its own config file. const m = u.pathname.match(/^\/signals\/config\/(\d+)/); if (u.hostname === 'connect.facebook.net' && m) pixels.add(m[1]); if (u.hostname.endsWith('facebook.com') && u.pathname.startsWith('/tr')) { events.push(u.searchParams.get('ev') || new URLSearchParams(req.postData() || '').get('ev')); } }); let html = ''; try { await page.goto(url, { waitUntil: 'load', timeout: 45000 }); await page.waitForTimeout(5000); // give tag managers time to run html = await page.content(); } catch (e) { console.log(`\n${url}\n could not load: ${e.message.split('\n')[0]}`); await page.close(); continue; } const inits = (html.match(/fbq\(\s*['"]init['"]/g) || []).length; console.log(`\n${url}`); console.log(` Pixel library loaded: ${library ? 'yes' : 'no'}`); console.log(` Pixel IDs loaded: ${pixels.size ? [...pixels].join(', ') : 'none'}`); if (pixels.size > 1) console.log(' note: more than one Pixel; check each one is meant to be there'); if (inits > 1) console.log(` warning: fbq('init') appears ${inits} times in the page HTML (duplicate base code?)`); console.log(` events seen: ${events.length ? events.join(', ') : 'none (see note in the post)'}`); await page.close();}await browser.close();
Run it with your home page, a product or service page, a blog post and your thank-you page: node check-meta-pixel.mjs https://example.com/ https://example.com/product/ .... Any page that says "no" where you expected a Pixel is the one to open in Data Advisor.
What we found when we ran it. On Nov. 17 we ran it on the home pages of 10 well-known online stores and on this site. Five of the 10 stores loaded the Pixel library, and each of those loaded exactly one Pixel ID. The other five loaded no Pixel on the home page in our test. That doesn't mean they don't use Meta: a site can wait for cookie consent, load the Pixel only after a click, or send events from its server with the Conversions API instead. One store's HTML contained fbq('init') twice while loading a single Pixel ID, which is the kind of thing worth a look in Data Advisor rather than proof of a problem. This site loaded none, which is correct: we don't run a Meta Pixel.
What the script can't do. In our headless browser, none of the stores sent a single Pixel event, not even PageView, although the Pixel loaded. We don't know whether that comes from consent settings, how the sites treat automated browsers, or Meta's own script, so treat the script as a check that the Pixel loads, not that events reach Meta. For events, use Data Advisor in a normal browser or the test events tool.
What we don't know
When the rename happened. Meta's documentation and the store listing say "formerly Meta Pixel Helper" but give no date, and we found no announcement.
Whether Data Advisor will keep working without a login in the long run. Today, Meta says detection and troubleshooting work logged out.
How well the automated setups work. We haven't run one; we'll write it up if we do. For a setting Meta switched on by default this month, see our guide to measure conversions on customer devices.
Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.