Meta Pixel Helper Is Now Meta Ads Data Advisor: How to Use It

Meta Pixel Helper, also known as Facebook Pixel Helper, is the free browser extension marketers use to check whether the Meta Pixel fires. It has a new name. Meta's developer documentation now describes Meta Ads Data Advisor (formerly Meta Pixel Helper), and the old Chrome Web Store link for Pixel Helper now redirects to a listing titled Meta Ads Data Advisor, offered by Meta. When we checked on November 2, 2026, it showed version 5.12.2, updated October 28, 2026.

The checks people installed it for still work. Meta says all existing diagnostic features continue to work, and an installed copy updates itself. What changed is what surrounds them: a side panel, automated setup for tools such as Google Tag Manager and Shopify, monitoring, new status labels and a wider list of browser permissions.

This guide covers how to use it to check your pixel, how to read its statuses and messages, what it cannot tell you (above all, whether your server events arrive and are deduplicated), how to check a pixel with only your browser, and which helper to use for TikTok, Pinterest, Google, Microsoft and Snap. We checked the details against Meta's documentation on November 2, 2026, and ran our own request test, described below.

What is Meta Ads Data Advisor (formerly Meta Pixel Helper)?

Meta describes Data Advisor as a free browser extension for Google Chrome and Microsoft Edge that helps you connect your website and other data to Meta, monitor your setup for issues, and fix them with your approval.

When it is installed, its icon sits next to the address bar. On a page with a Meta Pixel, the icon shows a badge with a dot or a number, which is the number of pixel events fired on the current page. Meta says that if the icon has no badge, no Meta Pixel is installed on the page. Clicking the icon opens a side panel with details you can use to verify, troubleshoot and improve the pixel, and to start the automated setup flows.

The diagnostics that stayed:

• Verify the pixel installation and that events fire.
• Flag errors, such as broken events or missing parameters like price or currency.

What is new:

• Automated setup of the Meta Pixel and Conversions API through Google Tag Manager or Shopify, CRM connections through Salesforce, and product catalogs through WordPress and WooCommerce. Meta says more platforms will be added.
• Recommended fixes that it can apply from your browser, with your approval.
• Monitoring that notifies you when it detects issues.

What you need to use it:

• To check a pixel: nothing. Meta says basic pixel detection and troubleshooting work while you are logged out.
• For setup and automation: a Facebook profile with access to the ad data in your business portfolio, full access to your Meta ad account, and admin access to the platform you want to connect, such as Google Tag Manager, Shopify, Salesforce or HubSpot.
• For every check: your ad blocker switched off. Meta says you must disable your browser's ad blockers so the extension can detect your pixel and website events.

Check the permissions before you add it

During installation, Meta lists three permissions you approve:

Those descriptions explain the automation features. Chrome shows the full permission list on the extension's details page at chrome://extensions, and independent permission scanners count more than the three Meta lists, including cookies, web requests and the debugger. The store listing's privacy section says the extension handles web history, user activity and website content. The extension's terms, which the listing links to, also state that Meta will receive information about your browsing activity and use it solely to provide and improve the extension.

None of that makes it unsafe to use. It does mean it deserves more care than a simple page checker:

• Install it in a browser profile you use only for audits, with no logged-in sessions for sensitive tools.
• Skip the Facebook login unless you want the setup and automation features. Detection works without it.
• If you handle sensitive personal data, such as health or financial information, ask whoever owns compliance before you run any extension on live pages.
• Or use the no-extension method further down. It needs no permissions at all.

How to check your pixel with Meta Ads Data Advisor

This is the check we would run on any store. It follows Meta's own steps for testing pixel events.

Step 1: Install it and pin it

In Chrome, open the Chrome Web Store, search for Meta Ads Data Advisor, click Add to Chrome, review the permissions and click Add extension. In Edge, find it in Microsoft Edge Add-ons. Pin the icon so you can see the badge on every page.

If you already had Meta Pixel Helper, you do not need to reinstall, because the extension updates itself. If it shows as switched off after the update, Chrome may be waiting for you to accept the new permissions. Open chrome://extensions, switch it on and approve them.

Step 2: Turn your ad blocker off for the site

Disable ad blockers and privacy extensions for the site you are testing, or use a browser profile that has none. With a blocker active, the extension may not see the pixel, and you will chase a problem that only exists in your own browser.

Step 3: Open the page and read the badge

Open the page where the pixel should be. The badge shows how many pixel events fired. Click the icon to open the side panel, which lists each pixel it found, with its ID. If the panel looks empty, reload the page with the panel open so it can read the events.

Check the ID. If you see one you do not recognize, a second pixel is on your site, often from an old agency setup, a plugin or a theme.

Step 4: Do what a customer does

Meta's guidance is that if you add standard events to your pixel code on certain pages, you need to complete a test conversion for each. For example, add an item to your cart to test an AddToCart event. Walk the whole journey:

Step 5: Open each event and read the details

Open every event in the side panel and check its status, its parameters (value, currency, content_ids and so on) and any advanced matching data. Compare them with your product catalog and order data, because wrong values are more common than missing events.

Turn on Show all events to keep events from every page of your browser session in one list. Meta notes this is useful for debugging multi-page funnels, for example when a Purchase fires on a thank-you page after a redirect.

Step 6: Confirm that Meta received the events

The extension shows what your browser sent. It does not prove Meta received it. In Events Manager, click Data sources, select your pixel and open Test events, then browse your site from there. Meta's own quick setup checklist includes this step: events should be visible in the Test events tool.

How to read the statuses

Data Advisor puts a status on each pixel and on each event. These are Meta's definitions.

Pixel status

Event status

Meta adds a note that matters: a pixel's status may be active even if individual events have warnings, and a pixel may show a warning status even if events are being sent. A green pixel does not prove every event is clean, and a warning does not prove tracking has stopped. Open the pixel, open each event, and read what the issue is before you change anything.

Messages you may see, and what to do about them

Meta's earlier Pixel Helper documentation named a set of errors and warnings. Meta's current Data Advisor page lists a shorter set of common setup mistakes instead, shown below the table. We could not confirm that the extension still shows each of these exact names, so treat the table as a guide to the underlying problem.

Meta's current page boils the common mistakes down to five:

• Duplicate pixel code: make sure the pixel code is not duplicated on a single page.
• Strategic placement: only place pixel code on pages where tracking is necessary.
• iframes and tag managers: if you use either, confirm that browser settings or privacy tools are not blocking the pixel.
• Base code placement: place the base code in the head section of your site. Incorrect placement can lead to missed tracking.
• One conversion event per page, typically: unless additional events are triggered by user actions such as button clicks.

What Meta Ads Data Advisor cannot tell you

Meta's own page has a section on when to use Events Manager instead of the extension. It says custom conversions and some advanced event types may not appear in Data Advisor but can still be sent, that button-click events may not be detected depending on your website setup, and that user-triggered events may not be reliably detected unless the page reloads or makes a direct pixel call. For anything deeper, Meta points you to the Test events tool.

Beyond that, there are limits that follow from what an extension is. It reads the requests your browser makes. It does not see your server, and it does not see Meta's side. So:

There is a second limit that no tool removes: your test describes your browser. It has your consent choice, your blocker settings and your cookies. About 29.5% of internet users aged 16 and over use an ad blocker at least sometimes (GWI, Q2 2025), and Safari and Firefox limit tracking by default, so real visitors lose events that your clean test shows arriving. Our ad blocker statistics guide has the numbers, and the ad blocker loss calculator estimates what that means for your store.

How to check a pixel without the extension

Your browser can show you everything the extension reads. It takes one minute and needs no permissions:

1. Open the page, press F12 and go to the Network tab.
2. Type facebook.com/tr in the filter box and reload the page.
3. Do the action you want to test, such as adding a product to the cart.
4. Click a request and read its query string parameters.

If fbevents.js loads but no request to /tr/ follows, look at your fbq calls and at any consent setting that withholds events. If fbevents.js never loads, look at how the script is loaded: a consent tool, a tag manager or a blocked domain.

What a real request looks like

We loaded Meta's standard base code on a plain test page with a placeholder pixel ID in Chrome 156 on November 2, 2026, fired a PageView, and then fired an AddToCart with an event ID. The pixel library reported version 2.9.433. This is the AddToCart request, split over several lines and trimmed. The real request is one line with more parameters:

https://www.facebook.com/tr/?id=1234567890123456
  &ev=AddToCart
  &dl=http%3A%2F%2F127.0.0.1%3A8793%2Findex.html
  &cd[value]=19.99
  &cd[currency]=USD
  &cd[content_ids]=%5B%22sku-1%22%5D
  &cd[content_type]=product
  &v=2.9.433
  &eid=test-order-123
  ...

Two details are worth noticing. Both events went out as image requests that returned HTTP 200 with an empty body, and that was true even though our pixel ID is a placeholder. A 200 response only tells you Meta's server answered. It does not tell you the event was accepted for your account. And our PageView, fired without an event ID, carried no eid at all. If you also send that event from your server, there is nothing for Meta to match the two copies on. Depending on the page and the library version, requests can also be sent as POST, so filter on the URL and not on the request type.

Meta's Test events tool for browser events

For a check that proves Meta received the event, use Test events. In Events Manager, click Data sources, select your pixel, open Test events, enter your site URL and click Open website. Browse in the window that opens, and keep the Test events page open, because browser events are only recorded while it is.

Test your server events and deduplication

A browser extension cannot follow server events, because they go from your server to Meta and never pass through your browser. Meta gives you three places to check them.

Test events, with a test code

1. In Events Manager, click Data sources, select your dataset and open the Test events tab.
2. Find the server events section. Meta generates a test code for you.
3. Send an event from your server with that code as test_event_code at the top level of the request, next to the data array and not inside an event:

{
  "data": [
    {
      "event_name": "Purchase",
      "event_time": 1793600000,
      "event_id": "order-1001",
      "action_source": "website",
      "event_source_url": "https://shop.example/thank-you",
      "user_data": { "em": ["SHA256_HASHED_EMAIL"] },
      "custom_data": { "value": 49.0, "currency": "USD" }
    }
  ],
  "test_event_code": "TEST12345"
}

The event then appears in the Test events window once the request is sent. Two cautions from Meta's documentation: remove test_event_code from your production payload, and remember that test events are not sandboxed. Meta says events sent with a test code are not dropped, and they still flow into Events Manager. Use a real test conversion, not invented orders.

A note on SignalBridge. In your SignalBridge dashboard, the Facebook Ads card has a Test button and an optional Test Events code field. Paste the current code from Events Manager before you press Test, and the verification event shows up in the Test events tab.

Overview and the connection method

After you start sending events, Meta says you should be able to verify them in Events Manager within 20 minutes. Open Overview to see the number of raw, matched and attributed events Meta received, and the Connection method column to see the channel each event was sent through. This is where you confirm that your server events arrive as server events.

Deduplication

If you send the same conversion from the browser pixel and from the server, which Meta recommends, you must deduplicate it. A clean extension panel tells you nothing about this, because it sees one browser event and has no view of the server copy. Meta's rules:

• The recommended key is the event ID plus the event name. The pixel's eventID must match the Conversions API's event_id, and the event names must match too. In the pixel, the event ID is the fourth argument of the fbq call: fbq('track', 'Purchase', {value: 12, currency: 'USD'}, {eventID: 'EVENT_ID'}). In the raw request it is the eid parameter.
• Both copies must reach the same pixel within 48 hours. Meta discards the later event when it finds the same key.
• If the two copies do not differ meaningfully, Meta generally prefers the one it received first.
• fbp or external_id is only a fallback, and it generally only works for events sent from the browser first and then through the server.

To check it:

1. Open your Purchase or Lead event in the extension or the Network tab and read the eid value.
2. Confirm it is an ID you set, such as the order ID, and that your server sends the same string as event_id, with the same event name, to the same pixel.
3. Open the event's details in Events Manager. Meta shows a warning when your deduplication rate is too low.

Our event deduplication guide covers the setup in more depth, and the Event Match Quality guide explains the score you will see in Overview.

Automatic events: what changed on August 3, 2026

Meta's developer page says that starting August 3, 2026, when you set up a new pixel through Data Advisor, the option to automatically detect and add standard events is pre-selected in the setup flow, and you can deselect it before you finish. Meta's Help Center says that when you add a new pixel through Google Tag Manager, you are asked about automatic events on a dedicated screen after setup, and you can decline. Either way, events you never coded can appear in the side panel with the Auto-detected status.

That is worth a quick look for two reasons. First, a detected event may describe a button or a page you did not mean to report. Second, if you also send events yourself or through a server-side tool, you want to be sure the counts still add up. Meta says automatic events are deduplicated against events you set up manually, so check Overview after you switch the feature on. You can review the detected events and turn the feature off in Events Manager, in your dataset's settings.

Why the badge can be empty when nothing is wrong

No badge means the extension saw no pixel events on that page. That is sometimes a real fault, and sometimes correct behavior:

• A consent banner is holding the pixel. In regions that require consent, a marketing pixel should not load until the visitor accepts. When we opened signalbridgedata.com in Chrome, the Network tab showed no request to Meta until we accepted marketing cookies, and fbevents.js loaded straight after. If your own tests show nothing before consent, that is the setup working. Our GDPR guide explains what consent changes for server-side tracking.
• An ad blocker or privacy extension is on. Meta says to disable them for the check.
• The pixel is on a different page. Some setups only fire on the order confirmation page, so you have to complete a purchase to see anything.
• The pixel loads late. If it is deliberately delayed, wait and reload before you conclude it is missing.
• It is inside an iframe or a tag manager that browser settings or privacy tools block. This is one of the five mistakes on Meta's list.
• You are in a browser Meta does not support. The extension runs in Chrome and Edge only.

Our Shopify pixel troubleshooting guide walks through the Shopify-specific causes.

Pixel helpers for TikTok, Pinterest, Google, Microsoft and Snap

Each ad platform has its own helper, and each one checks only its own platform's tag. Use the one that matches the pixel you are testing:

These helpers all have the same blind spot as Meta's: they read your browser, not your server. Each platform has its own test tool for server events, and our setup guides for TikTok, Pinterest, Snapchat, Microsoft Ads and Google Ads show where to find it.

Where SignalBridge fits

A browser extension can only audit the browser half of your tracking. SignalBridge handles the other half. It sends your conversions to Meta from the server through the Conversions API, and gives each event an ID that the browser pixel call and the server copy share, so Meta can deduplicate them.

A sensible routine is to use Data Advisor, or the Network tab, to confirm the browser events, and then confirm the server events in Test events and Overview, where they should show up with the connection method Server. If you want that second half without building it yourself, see our Facebook Ads integration, or what the Conversions API is if you are new to it.

Frequently Asked Questions

Is Meta Pixel Helper the same as Meta Ads Data Advisor?

Yes. It is the same extension with a new name. Meta's documentation calls Meta Ads Data Advisor the extension formerly called Meta Pixel Helper, and the store listing for the old extension now carries the new name. Meta says all existing diagnostic features continue to work.

Is Facebook Pixel Helper still available?

Not under that name. Facebook Pixel Helper is what many marketers still call the extension, and Meta Pixel Helper is the name it carried before the rename. The old Chrome Web Store link for Pixel Helper now redirects to the Meta Ads Data Advisor listing, so search for it under the new name or follow the link in the Sources below.

Is Meta Ads Data Advisor free?

Yes. Meta describes it as a free browser extension for Google Chrome and Microsoft Edge.

Does Meta Ads Data Advisor work in Firefox or Safari?

Meta lists Chrome and Edge only. In Firefox or Safari, open the developer tools, go to the Network tab and filter for facebook.com/tr, then confirm in the Test events tool in Events Manager.

Do I need to log in to use Meta Ads Data Advisor?

Not to check a pixel. Meta says basic pixel detection and troubleshooting work while you are logged out. You need a Facebook profile, access to the ad account and admin access to the connected platform only for the setup and automation features.

Why does Meta Ads Data Advisor show no pixel on my site?

The page may have no pixel, an ad blocker may be active, a consent banner may be holding the pixel until you accept, the pixel may load late or only on another page, or it may sit in an iframe or tag manager that your browser settings block. Open the Network tab and look for fbevents.js and then facebook.com/tr to find which step is missing.

Does Meta Ads Data Advisor show Conversions API events?

Not as they are sent. Server events go from your server to Meta and never pass through your browser, and the toolbar badge counts pixel events fired on the current page. To follow server events, send them with a test code and watch the Test events tab, then use Overview and its Connection method column.

Why does my pixel show a warning when events are sending?

Meta says a pixel's status may be active even if individual events have warnings, and a pixel may show a warning status even if events are being sent. Open the pixel, then each event, and read what the issue is.

Is Meta Ads Data Advisor safe to install?

It is published by Meta. Installing it means accepting broad permissions, including reading and changing data on all websites, and terms that say Meta receives information about your browsing activity. A sensible approach is to install it in a separate browser profile used only for audits and to skip the login unless you need the setup features. If you handle sensitive data, ask your compliance owner first.

How do I test a Meta pixel without the extension?

Open the Network tab, filter for facebook.com/tr, reload, perform the action and read the request parameters: id, ev, cd[...] and eid. Then confirm in Events Manager. Click Data sources, select your pixel, open Test events, enter your URL and click Open website, and keep the Test events page open while you browse.

How do I check that browser and server events are deduplicated?

The pixel's eventID and the server's event_id must carry the same value, with the same event name, sent to the same pixel within 48 hours. The eid parameter in the browser request is that value. Then open the event's details in Events Manager, where Meta shows a warning when the deduplication rate is too low.

What is the TikTok equivalent of Meta Pixel Helper?

TikTok Pixel Helper, a Chrome extension from TikTok For Business that checks pixel installation and flags errors. Pinterest, Snap, Microsoft and Google each have their own helper, listed in the table above.

Sources

• Meta Ads Data Advisor, developer documentation
• About Meta Ads Data Advisor, Meta Business Help Center
• Install or uninstall Meta Ads Data Advisor, Meta Business Help Center
• Meta Ads Data Advisor, Chrome Web Store
• Meta Ads Data Advisor Terms
• Test your server events using the test events tool, Meta Business Help Center
• Conversions API: using the API, Meta for Developers
• Handling duplicate pixel and Conversions API events, Meta for Developers

Related Reading

• Event Deduplication Guide
• What Is Event Match Quality?
• Shopify Facebook Pixel Not Working
• What Is a Tracking Pixel?
• Meta CAPI vs Facebook Pixel
• Tracking Audit Checklist
• Ad Blocker Statistics 2026
• Server-Side Tracking and GDPR