Meta Pixel Helper (Now Meta Ads Data Advisor): How to Check Your Pixel Is Working

If you run Facebook or Instagram ads to a website, the Meta pixel is what tells Meta who added to cart, who bought and who left. When it's broken, everything built on top of it breaks quietly too: your sales campaigns optimise for the wrong thing, your retargeting audiences stay empty and your reports don't match your store.

For years, the quickest way to check it was a free Chrome extension called Meta Pixel Helper. If you search for it today, you'll find something with a new name. Meta has replaced Pixel Helper with Meta Ads Data Advisor, and it does a lot more than the old tool did.

In this guide I'll show you how to install it, what its statuses mean, how to test your events properly (including a purchase), and the problems I'd check first on Shopify and WordPress stores. Everything here comes from Meta's Business Help Centre and developer documentation, plus the Shopify and WordPress plugin pages, which I checked on 2 November 2026.

Meta Pixel Helper is now Meta Ads Data Advisor

Meta's About Meta Ads Data Advisor page describes it as a free browser extension for Google Chrome and Microsoft Edge, formerly known as Meta Pixel Helper. It still does the diagnostics Pixel Helper did, and it can now also help set up data connections, flag problems and suggest fixes that it applies only with your approval.

If you already had Pixel Helper installed, Meta's developer documentation says the extension updates automatically to Data Advisor and the existing diagnostic features keep working.

The new features include:

• Setting up the Meta pixel and Conversions API through Google Tag Manager, including standard events
• Connecting a Shopify store or WooCommerce site to Meta (pixel, Conversions API and catalogue)
• Flagging broken events and missing parameters such as value and currency
• Giving you a summary of every action it has taken

For this guide, I'm focusing on the part most people need: checking whether the pixel is actually working.

How to install it

Meta's install page lists these steps for Chrome:

1. Open the Chrome Web Store and search for Meta Ads Data Advisor.
2. Click Add to Chrome.
3. Review the permissions and click Add extension.
4. Pin the extension so its icon stays visible next to the address bar.

On Edge, install it from the Microsoft Edge Add-ons store instead.

A few things worth knowing before you start:

• Read the permissions. The extension asks to read and change data on all websites and to access the page debugger, because its automation features work on other sites on your behalf. I'd install it on the browser profile you use for work, not on a shared family computer.
• Do you need to log in? Meta's developer documentation says basic pixel detection and troubleshooting work while you're logged out. The setup and automation features need you to log in with Facebook, plus admin access to the ad account and to the platform you're connecting (such as Shopify or Google Tag Manager).
• Turn off your ad blocker on the site you're testing. Meta says Data Advisor can't detect pixels and events while an ad blocker is running.

How to read what it shows

Open any page on your website. Meta says the extension icon shows a small badge with a dot or a number, which tells you how many pixel events fired on that page. No badge means no Meta pixel was found on that page.

Click the icon and a side panel opens. It lists the pixels on the page and their events. Meta uses these labels:

One detail that confuses people: Meta notes that a pixel can show as Active even when individual events have warnings. So don't stop at the pixel status. Click into the pixel and check each event.

Click an event to see the data it sends, such as content IDs, content type, value and currency. This is where you catch the sneaky problems, like a Purchase event with no value or the wrong currency.

How to test your events properly

Seeing PageView on your home page only proves the base code loads. What matters for ads is the events further down the funnel. Meta's testing guide recommends this routine:

1. Go to the page where the pixel is installed.
2. Click the Data Advisor icon.
3. Do the action you want to track, for example add a product to the cart to test AddToCart.
4. Check that the pixel is found and that the expected event appears as successful.
5. If there are errors or warnings, apply the suggested fix.
6. Repeat for every event you care about.

Turn on Show all events in the side panel. It keeps a log of events across your browsing session instead of only the current page, which is exactly what you need when you're walking through product page, cart, checkout and thank-you page.

Here's the order I'd test a store in:

1. ViewContent on a product page
2. AddToCart when you click the button
3. InitiateCheckout when the checkout opens
4. Purchase on the order confirmation page

For Purchase, there's no way around placing a real order. Use a cheap product, or create a test product, and cancel the order afterwards. Then check that Purchase fires once, with the right value and currency (PKR, INR or whatever your store uses).

If you run a cash-on-delivery store, remember what the pixel can and can't see. It records the order being placed on your site. It doesn't know whether the parcel was later refused at the door. That's one reason your Ads Manager "purchases" can look better than your bank account.

When the extension isn't enough: use Test Events

Meta is upfront about the extension's limits. Custom conversions and some advanced events may not appear in it even when they're working, and it may not reliably detect button-click events unless they reload the page or call the pixel directly.

For those, use the Test events tool in Events Manager. Meta's test events guide explains the steps:

1. In Events Manager, open Data sources and select your pixel (dataset).
2. Go to the Test events tab.
3. Enter your website URL and click Open website.
4. Use your site as a customer would. Your events appear in the Test events tab as you go.
5. Click Clear activity when you're done.

Two details from that page: website activity is only recorded while the test events page is open, and test information stays there for 24 hours or until you clear it. Meta also says data can take 30 minutes or more to show in your analytics after you set up an event, so don't panic if a brand-new event isn't in your reports straight away.

My rule of thumb: use Data Advisor for quick checks on any page, and Test Events when something looks wrong or when you're checking button clicks and custom conversions.

The most common pixel problems (and what to check)

Meta's troubleshooting checklist covers the basics: the base code should be in the <head> of every page you track, it shouldn't be duplicated on any page, standard events should load after the base code, and usually there should be only one conversion event per page unless extra events come from actions like button clicks.

In practice, here's how those problems show up.

Duplicate pixels or events firing twice

This is the one I'd check first on any store that's been through a few developers or apps. The pixel ends up installed in two or three places at once: pasted into the theme, added through an app or plugin, and added again through Google Tag Manager. The result is double-counted events and inflated results.

What to do: open your product page and thank-you page with Data Advisor and look for the same pixel ID loading more than once, or the same event (especially Purchase) firing twice for one action. Then pick one installation method and remove the others.

Purchase is missing

Check that the event fires on the actual order confirmation page. Common causes are a checkout hosted on another domain, a thank-you page your app or plugin doesn't cover, or an ad blocker in your test browser. Place a test order with the side panel open and Show all events turned on.

Value or currency is missing or wrong

Data Advisor flags missing parameters. If Purchase fires without value and currency, Meta can't tell a small order from a big one, and value-based reporting becomes useless. Also check that the currency code matches what your store actually charges in.

Pixel and Conversions API counting the same sale twice

Many Shopify and WordPress setups now send events from both the browser (pixel) and your server (Conversions API). That's fine, but the same event needs to be deduplicated. Meta's deduplication guide says the event_name must match and the event_id must be identical for both, or alternatively the event name plus external_id or fbp must match. If you see suspiciously high conversion numbers after adding the Conversions API, this is the first thing to ask your developer about.

Events Meta added on its own

Meta says that from 3 August 2026, when you set up a new pixel through Data Advisor, the option to automatically detect and add standard events is pre-selected. You can untick it during setup, or turn it off later in Events Manager under Settings > Track events automatically without code. If your site already sends coded events, review the auto-detected ones to make sure you're not counting the same action twice.

Shopify and WordPress: where the pixel usually comes from

Shopify. Most stores connect the pixel through the free Facebook & Instagram sales channel (shown as "Facebook and Instagram by Meta" in Shopify's Help Center). That's where you create or add the pixel, choose your customer data-sharing level and set up the Conversions API. If you use the sales channel, don't also paste the pixel code into your theme. That's a classic cause of duplicates. Meta says Data Advisor can also connect a Shopify store for you, including the pixel, Conversions API and catalogue.

WordPress. Meta's official plugin is Meta pixel for WordPress. The listing says it captures events like Lead, ViewContent, AddToCart, InitiateCheckout and Purchase and supports the Conversions API. The install steps on the listing say to search for "Facebook for WordPress" in Plugins > Add New and pick the one authored by Facebook. Again, if you install the plugin, remove any old pixel code from your theme header or other tracking plugins.

Before you spend on ads: a 10-minute pixel check

Run this before every new campaign, and after any theme change, new app or checkout update:

1. Turn off your ad blocker and open your site with Data Advisor pinned.
2. Check that the home page shows your pixel, and only one copy of it.
3. Walk through product page, add to cart and checkout with Show all events on.
4. Place a cheap test order and confirm Purchase fires once, with value and currency.
5. Open Test Events in Events Manager and repeat if anything looked odd.
6. Check your privacy policy explains your use of the pixel, as Meta's Business Tools Terms require.

Once your tracking is right, the rest of your ads get easier to judge. If you're just starting, read my Meta ads for beginners guide. With a working pixel you can also build the website audiences in my Meta ads retargeting guide, and plan your spend with my guide on Facebook ads price in Pakistan. For quick maths on ROAS, CPA and break-even, use the calculators on my Facebook ads page. There are more guides on my blog, and more about me on my home page.

FAQ

Is Meta Pixel Helper still available?

Meta Pixel Helper has been replaced by Meta Ads Data Advisor, a free extension for Chrome and Edge. If you already had Pixel Helper installed, Meta says it updates automatically to Data Advisor and the diagnostic features keep working.

How do I know if my Meta pixel is working?

Open your website with Meta Ads Data Advisor installed. A badge with a dot or number on the extension icon means pixel events fired on that page, and no badge means no pixel was found. Click the icon to check each event's status, then confirm with the Test events tool in Events Manager.

Why does the extension show no pixel on my site?

The most common reasons are an ad blocker running in your browser, the pixel not being installed on that page, or the code being placed incorrectly. Meta recommends placing the base code in the head section of every page you want to track.

Why is my Purchase event firing twice?

Usually the pixel is installed more than once, for example in your theme and through an app, plugin or Google Tag Manager. If you also use the Conversions API, both sources need matching event names and event IDs so Meta can deduplicate them.

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

Meta's developer documentation says basic pixel detection and troubleshooting work without logging in. To use its setup and automation features, you need to log in with Facebook and have admin access to your ad account and the platform you're connecting.

Why don't my button clicks show up in the extension?

Meta says the extension may not reliably detect button-click events or custom conversions, even when they're working. Use the Test events tool in Events Manager to check them.

Keep reading

• Meta ads for beginners: your first campaign on a small budget
• Meta ads retargeting on a small budget: bring back WhatsApp chats and site visitors
• Facebook ads price in Pakistan: what decides your cost (with PKR budget maths)
• Abandoned cart emails: timing, templates and discounts for Shopify and Klaviyo
• Click-to-WhatsApp ads: how to turn chats into sales
• See all posts on the blog
• Back to my home page