If you went looking for the Meta Pixel Helper extension recently and found something called Meta Ads Data Advisor instead, you're in the right place. It's the same extension under a new name. Meta describes it as "formerly Meta Pixel Helper", and existing installs were updated automatically.
This guide covers what changed, how to install it, how to read what it shows, what the common warnings mean and how to fix them, and when to use Events Manager instead.
The short answer
| Question | Answer |
|---|---|
| Is Meta Pixel Helper gone? | It was renamed Meta Ads Data Advisor. If you had Pixel Helper installed, it updated itself. |
| Which browser does it work in? | Google Chrome. |
| Is it free? | Yes. |
| What does it do? | Shows whether a Meta pixel is on the page you're viewing, which events it fired, with which parameters, and flags problems. The new version can also help set things up and monitor them. |
| How do I install it? | Chrome Web Store, search "Meta Ads Data Advisor", Add to Chrome, confirm. |
| Does it check the Conversions API? | No. It sees what the browser sends. To check server events and deduplication, use Test events and Diagnostics in Events Manager. |
| What's the quickest test? | Open your site, click the extension, check the pixel ID matches yours and that the right events fire on the right pages. |
What changed from Pixel Helper
Pixel Helper was a read-only checker: it showed what fired and left the fixing to you. Meta Ads Data Advisor keeps that and adds, according to Meta:
- Automatic setup of data connections from the browser.
- Monitoring that flags problems over time, not only when you happen to look.
- Guided fixes, carried out with your approval.
- A record of what it changed.
For checking whether a pixel works on a page, it does the same job Pixel Helper always did.
How to install it
- Open the Chrome Web Store in Google Chrome.
- Search for Meta Ads Data Advisor.
- Click Add to Chrome.
- Review the permissions it asks for and click Add extension.
- Pin it to the toolbar: click the puzzle piece icon next to the address bar and pin Meta Ads Data Advisor.
If you already had Meta Pixel Helper, you don't need to do anything. Look for the new name in your extensions.
It's a Chrome extension. There's no official version for Safari or Firefox.
How to read what it shows
Open any page of your website and look at the extension's icon:
- No badge: no Meta pixel found on this page.
- A badge with a number: a pixel was found, and the number is how many events fired.
Click the icon to see the details. For each pixel on the page you'll see:
- The pixel ID. Check it matches the ID in your Events Manager. A surprising number of sites send events to an old pixel or to someone else's.
- Each event that fired: PageView, ViewContent, Lead, Purchase, or custom events.
- The parameters sent with each event, such as value, currency, content name and content IDs.
- Advanced Matching data, if the pixel is passing customer details like email automatically.
- A status for the pixel and for each event. Meta uses Active, Warning, Inactive, Error and Auto-detected.
Click an event to expand it and see what was sent.
A two-minute check of your site
- Home page: one PageView, your pixel ID, no errors.
- A product or service page: PageView, plus ViewContent if you use it.
- Your form or checkout: submit a test. You should see Lead or Purchase fire once, on the thank-you step, not on page load.
- For purchases: check that value and currency are present and that value is a number.
- Look for a second pixel ID you don't recognise. Old agencies and old plugins leave pixels behind.
If all five pass, the browser side is fine. Check the server side in Events Manager (below).
Common warnings and how to fix them
The extension's wording changes from version to version, so here are the problems it reports in plain terms.
| What it tells you | What it means | How to fix it |
|---|---|---|
| No pixel found | The pixel code isn't on this page, or is blocked | Check the base code is in the page head on every page. Turn off ad blockers while testing. Check your cookie banner isn't blocking it before consent. |
| Pixel fired more than once, or duplicate pixel | The same pixel was installed twice, often once by hand and once by a plugin or tag manager | Keep one installation. Remove the duplicate. |
| More than one pixel ID | Several pixels are on the page | Remove pixels you don't use. If you need two, make sure each event goes where you mean it to. |
| Not a standard event | An event name Meta doesn't recognise, often a typo like "lead" or "Purchased" | Use Meta's exact standard event names, which are case sensitive: Lead, Purchase, CompleteRegistration, Schedule and so on. |
| Invalid pixel ID | The ID in the code is wrong or deleted | Copy the ID again from Events Manager. |
| Missing value or currency | A Purchase was sent without the amount or currency | Add both. Currency is a three-letter code like USD or GBP. Value must be a number, not text with a currency symbol. |
| Pixel took too long to load | The code loads late, often far down the page | Move the base code into the head, as high as possible. |
| Event fires on page load | The conversion event runs when the page opens, not when the action happens | Fire it on the form submit or on the confirmation page only. |
| Pixel inside an iframe | The form or checkout is embedded from another site | The embedded tool has to fire the event itself, or send it server-side. |
What the extension can't tell you
The extension only sees the browser. These need Events Manager:
- Whether your server events (Conversions API) arrive. Server events never pass through the browser.
- Whether browser and server events are deduplicated. Meta merges them when both share the same event name and event_id. Events Manager shows deduplication and event coverage.
- Event Match Quality. How well your events match real people. See Event Match Quality explained.
- Whether events sent hours ago were received. The extension only shows what fires while you're on the page.
Use Test events for a full check
- In Events Manager, open your dataset (pixel) and go to Test events.
- Enter your website URL and open it from there, or copy the test code for server events.
- Do the action: submit the form, book, buy.
- Watch the events arrive. Each one shows whether it came from the browser or the server, and whether it was deduplicated.
Server events only show in Test events if they're sent with the test event code, so your developer or tool needs to support it.
Check the Diagnostics tab
The Diagnostics tab in Events Manager lists problems Meta has found across real traffic, for example events missing parameters, deduplication issues or a drop in events received. Check it after any website change.
For developers: the network tab
Open Chrome's developer tools, go to the Network tab, filter for facebook.com/tr, and do the action. Each request is a pixel event. You can read the event name and parameters in the request.
How this works with Inflowave
If your forms, booking pages and funnel pages are built in Inflowave, you'll see the browser pixel events in the extension as normal. Inflowave also sends a matching server-side event for form submissions, bookings and paid deposits, with the same event_id as the browser event, so Meta counts each conversion once.
You won't see those server events in the extension, because they go straight from Inflowave to Meta. Check them in Events Manager: open the event in your dataset's overview and you'll see events received from the server as well as from the browser.
Add your pixel ID and Conversions API access token in Inflowave settings. Each form can use its own pixel.
Related guides: Event Match Quality, Facebook Conversions API setup, How to connect Facebook lead ads to your CRM and Meta conversion leads explained.
Questions people ask
What is Meta Pixel Helper?
A free Chrome extension from Meta that shows whether a Meta pixel is installed on a web page and which events it sends. It's now called Meta Ads Data Advisor.
Is Meta Pixel Helper gone?
No, it was renamed. Meta Pixel Helper became Meta Ads Data Advisor, and existing installs updated automatically.
How do I install Meta Pixel Helper?
Search for Meta Ads Data Advisor in the Chrome Web Store, click Add to Chrome, and confirm. Then pin it to the toolbar.
Does Meta Pixel Helper work on Safari or Firefox?
No. Meta's extension is for Google Chrome.
Why does Meta Pixel Helper say no pixel found?
The pixel code isn't on that page, it's blocked by an ad blocker or cookie banner, or it's inside an iframe. Check the base code is in the page head, test with ad blockers off, and accept cookies on your own site while testing.
Why is my pixel firing twice?
It's usually installed twice, for example by hand and by a plugin or tag manager. Remove one. If the same event fires twice on one action, check it isn't triggered both on page load and on submit.
Can Meta Pixel Helper check the Conversions API?
No. It only sees what the browser sends. Use Test events and Diagnostics in Events Manager to check server events and deduplication.
What is the main purpose of the Meta pixel?
To tell Meta what people do on your website after seeing or clicking an ad, such as viewing a page, submitting a form or buying. Meta uses that to measure results, build audiences and optimise delivery.
Can I delete a Meta pixel?
You can stop using it by removing its code from your website and disconnecting it from your ad accounts and tools. A pixel that no longer receives events does nothing, so removing the code is what matters.
How do I check which events my pixel sends?
Open the page with the extension active and click its icon. It lists each event that fired and the parameters sent. For the full picture, including server events, use Test events in Events Manager.
