You changed a theme, installed a new app, or just noticed Meta reporting fewer purchases than Shopify. The first tool most people reach for is the Meta Pixel Helper, the free Chrome extension that shows which pixel events fire on a page. It still does that job, but it has a new name, and it only shows you half of your Meta tracking.
Short answer: The Meta Pixel Helper is now called Meta Ads Data Advisor, a free extension for Chrome and Edge. Install it, browse your Shopify store and check that PageView, ViewContent, AddToCart and InitiateCheckout fire once each without errors. Then open Events Manager, because server-side Conversions API events never pass through your browser and have to be checked there.
Below: the full check on a Shopify store, the common errors, and how to verify the server side.
What Happened to the Meta Pixel Helper?
Meta renamed the extension. Its developer documentation now describes Meta Ads Data Advisor as the tool "formerly Meta Pixel Helper", available for Google Chrome and Microsoft Edge. If you already had Pixel Helper installed, it updated itself automatically and the diagnostics you know still work.
The extension now opens in a side panel, and if you log in with your Facebook profile it can suggest fixes and run guided setup flows, such as connecting a catalog. Logging in is optional; basic pixel detection works without it. Most people still search for "Meta Pixel Helper", so we use both names here. They are the same extension.
How to Install the Meta Pixel Helper (Data Advisor)
-
Open the Chrome Web Store (or Microsoft Edge Add-ons) and search for Meta Ads Data Advisor.
-
Check that it is offered by Meta (lookalike extensions exist), then click Add extension.
-
Pin it to your toolbar.
-
Pause your ad blocker for your own store. Meta notes that blockers stop the extension from detecting the pixel, which is a good reminder that they stop the pixel itself for many of your shoppers too.
How to Check Your Shopify Pixel Step by Step
Walk through your store like a shopper would with the extension active. We assume the pixel is connected through Meta's Facebook & Instagram sales channel app, as on most Shopify stores.
Step 1: Load Your Homepage
Click the extension icon. The side panel lists every pixel found on the page with a status of Active, Warning or Inactive. You want to see exactly one pixel ID, and it should match the pixel in your Events Manager. A second, unfamiliar pixel ID usually means an old app or a hard-coded snippet in your theme is still firing.
You should see a PageView event.
Step 2: Open a Product Page
Look for ViewContent. Click into the event to see its parameters. A healthy ViewContent carries content_ids, content_type, value and currency. The content ID should match the product or variant ID in your catalog, or your catalog ads will struggle to match products.
Step 3: Add a Product to the Cart
Look for AddToCart with a value and currency. If you use a slide-out cart drawer, check that one click gives one AddToCart; some themes and cart apps fire it twice.
Step 4: Start Checkout
Look for InitiateCheckout. This is where the extension often goes quiet. Shopify runs checkout pixels through Customer Events in a sandboxed environment, so an extension frequently shows little or nothing on checkout and thank-you pages even when events reach Meta fine. If AddPaymentInfo or Purchase are missing from the side panel, confirm them in Events Manager (below).
Step 5: Read the Event Details
For every event, open the detail view and check three things:
-
Value and currency are present on ViewContent, AddToCart, InitiateCheckout and Purchase.
-
Advanced Matching data shows up where you expect it, for example after a shopper logs in.
-
No warnings or errors sit next to the event.
If that all checks out, your browser pixel is healthy. That is half the picture.
Common Meta Pixel Helper Errors and What They Mean
Meta lists the issues the extension flags, and on Shopify a handful come up again and again.
| What you see | What it usually means on Shopify | How to fix it |
|---|---|---|
| Pixel not found | Facebook & Instagram app not connected, consent banner blocking the pixel, or your ad blocker is on | Reconnect the app, accept cookies in your test session, pause the blocker |
| Two pixel IDs on one page | An old pixel in `theme.liquid` or a second app firing its own pixel | Remove the hard-coded snippet or disconnect the extra app |
| Duplicate pixel code | The same pixel loaded twice, often from the app plus a manual install | Keep one installation, usually the Facebook & Instagram app |
| Missing parameters (value, currency, content_ids) | A custom or app-based event without product data | Use the native app events or fix the custom event code |
| Multiple conversion events on one page | Purchase or AddToCart fired several times on load | Find the second source (theme code, app, tag manager) and remove it |
| Blocked parameters | Data Meta does not accept, for example certain health or financial information in URLs or parameters | Remove the restricted data from URLs and custom parameters |
Note that Meta also says custom conversions and some advanced events may not appear in the extension even when they are sent correctly. Missing in the side panel does not always mean missing in Meta.
How to Spot Duplicate Events
Duplicate events are the most expensive pixel problem, because they inflate reported purchases and teach Meta's algorithm that a campaign works better than it does.
In the side panel, a duplicate looks like the same event name listed twice for one action: two AddToCart events after a single click, or two PageView events on one page load. The usual causes on Shopify:
-
The pixel installed through the Facebook & Instagram app and pasted into the theme by a previous developer or agency.
-
A tracking app and the native app both sending browser events.
-
A Google Tag Manager container that also fires the Meta pixel.
Keep one browser source and remove the rest.
One kind of duplicate is intentional. When you send a purchase from both the browser pixel and the Conversions API, Meta receives it twice on purpose and deduplicates it, as long as both copies share the same event_id. The extension can't check that part. For background on why you want both streams, read why profitable ad campaigns need event deduplication and two tracking methods.
What the Meta Pixel Helper Can't See
A browser extension watches what happens in your browser. The Meta pixel runs in the browser, so the extension sees it. The Conversions API sends events from a server (Shopify's, or your tracking provider's) straight to Meta. Those events never touch your browser, so the side panel can't show them firing in real time, no matter how well they work.
Meta does say Data Advisor helps verify Conversions API installation, but the event-by-event view you watch while clicking through your store is the browser pixel.
That matters because the browser pixel is the weaker half. Ad blockers, Safari's tracking limits (ITP), iOS privacy settings and consent banners all stop it, and browser pixels miss around 30-60% of conversions. A store can pass every check in the Meta Pixel Helper and still be losing a large share of its purchases, because the shoppers whose pixel never loaded are exactly the ones you can't see when you test from your own laptop with the blocker paused.
The extension answers "is my browser pixel firing correctly?" It can't answer "is Meta receiving all of my conversions?" That takes Events Manager.
How to Check Conversions API Events in Events Manager
Use the Test Events Tool
-
Go to Events Manager > Data Sources > your pixel > Test Events.
-
For browser events, enter your store URL and open it from there. For server events, Meta generates a test code that your server-side integration sends as
test_event_code. Many Shopify apps and tracking tools have a field for this code. -
Walk through the same journey as before, and this time place a real test order.
-
Watch the events come in. Each one is labelled with its source: browser or server.
Meta's Conversions API documentation says server events appear in the Test Events window once the request is sent, and that you should be able to verify regular events in Events Manager within 20 minutes. Remove the test code afterwards. Test events are not thrown away; they flow into your data like normal events.
This is also where the checkout events the extension missed show up, with value and currency.
Check Deduplication
When an event arrives from both the browser and the server, Meta matches the two copies using the event name plus the event ID. According to Meta's deduplication guide, the pixel's eventID must match the server event's event_id, and Meta deduplicates events with the same ID received within 48 hours, generally keeping the first one.
In Events Manager, look at each event in the Overview tab. A healthy setup shows both "Browser" and "Server" as connection methods and no deduplication warnings. If Meta flags low deduplication or you see purchase counts close to double your Shopify orders, the event IDs don't match. The glossary entry on event deduplication explains the logic in more detail.
Check Event Match Quality
While you are in Events Manager, open the Purchase event and look at Meta's Event Match Quality score. It is a diagnostic that tells you how well Meta can connect your events to real people, based on the customer information you send (hashed email, phone, click ID and so on). Server events usually carry more of that information than browser events. If your score is low, read how to improve Meta's Event Match Quality score.
Compare Against Shopify Orders
Finally, put a week of Meta-reported purchases next to the orders in Shopify for the same week. A modest gap is normal because of attribution windows and modeled conversions. A platform reporting far more than your real orders usually means duplicates; far fewer means lost signal. Our guide on how to check your Shopify conversion tracking is actually working gives you thresholds for what each kind of gap means.
Where Shopify's Native Setup Leaves Gaps
Shopify's Facebook & Instagram app has a data sharing setting with Standard, Enhanced and Maximum levels. Standard relies on the browser pixel; the higher levels add the Conversions API. If you are still on Standard, the Meta Pixel Helper can see your whole setup, and that setup is the one losing the most data.
The native setup still has limits: it does not build persistent shopper profiles across sessions and devices, so many events reach Meta with thin customer information. That is the gap TrackBee fills. It sends your Shopify events server-side to Meta, Google, TikTok, Pinterest, GA4 & Klaviyo, enriches them with first-party data such as hashed emails and click IDs from earlier sessions, and deduplicates against the browser pixel so purchases aren't counted twice. For the full setup, see our Meta Conversions API guide for Shopify or how Shopify conversion tracking works with TrackBee.
Frequently Asked Questions
Is the Meta Pixel Helper still available? Yes, under a new name. Meta renamed it Meta Ads Data Advisor. It is still free, works in Chrome and Microsoft Edge, and existing installs updated automatically.
Why does the Meta Pixel Helper say no pixel found on my Shopify store? The most common causes are an ad blocker in your own browser, a cookie banner that holds the pixel until you accept, or a Facebook & Instagram app that is disconnected. Pause the blocker, accept cookies and reload. If it is still missing, reconnect the app in Shopify.
Why doesn't the Meta Pixel Helper show my Purchase event? On Shopify, checkout and thank-you pages run pixels through Customer Events in a sandbox, so a browser extension often can't detect them there. Place a test order with Events Manager's Test Events tool open to confirm the Purchase arrives with value and currency.
Can the Meta Pixel Helper check the Conversions API? Not event by event. Conversions API events go from a server to Meta and never pass through your browser. Use Test Events in Events Manager, where each event shows whether it came from the browser or the server.
Why does the Meta Pixel Helper show two pixels? Usually a pixel is installed twice: once through the Facebook & Instagram app and once hard-coded in the theme or added by another app. Keep one installation and remove the rest, or you will report duplicate events.
See Everything Meta Receives, Not Just What the Browser Sends
The Meta Pixel Helper tells you whether your browser pixel works. TrackBee makes sure Meta gets the conversions the browser misses, with server-side tracking that enriches every event with first-party data and deduplicates it cleanly.
.png)
