Meta Pixel Helper is Meta's free Chrome extension that shows which Meta pixels load on a page and which events they send. Meta has renamed it Meta Ads Data Advisor, and because it watches your browser, you need Events Manager to confirm your Conversions API events are arriving too.
This guide shows how to install it, read its results, find your pixel ID, and run an "is my pixel working?" check on Shopify. For why the browser pixel alone misses conversions, see our guide to Meta CAPI and first-party data.
What is Meta Pixel Helper?
Meta Pixel Helper is a Google Chrome extension that detects Meta pixel code on a website and shows the events each pixel sends. Meta has renamed it Meta Ads Data Advisor. Existing installs update automatically, the diagnostic features still work, and logged-in users get new setup tools for platforms including Shopify.
When a page has a Meta pixel, the extension's icon shows a badge with a dot or a number for the pixel events fired on that page. No badge means no Meta pixel was found. Click the icon to open a side panel with the details. Most people still search for Pixel Helper or Facebook Pixel Helper, so we use the old name too.
How do you install Meta Pixel Helper?
Meta lists Google Chrome as a requirement.
- Open the Chrome Web Store and search for Meta Ads Data Advisor.
- Click Add to Chrome, review the permissions, then click Add extension.
- Pin the extension so you can see event counts as you browse.
- Optionally, log in with your Facebook profile. Basic pixel detection works logged out; setup and automation features need a login and admin access to your ad account.
If your old Pixel Helper shows as deactivated, switch it back on at chrome://extensions/ and accept the updated permissions. Turn off your ad blocker on your own store, as Meta requires. The new version asks to read and change data on all websites, so we suggest a separate Chrome profile used only for testing.
How do you read Meta Pixel Helper results?
Open your store, click the icon, then do the action you want to test.
Pixels found
The panel lists each pixel on the page and whether it loaded. Check that the ID matches your dataset in Events Manager. Agency or partner pixels may appear too. In the Shopify accounts we audit, more than one of your own pixel IDs on the same page points to a duplicate install.
Events and parameters
Select a pixel to see its events, then click an event to see its data: content IDs and types, the URL where it fired, Advanced Matching data, and parameters such as value, currency and content_name. Show all events logs events across your whole browsing session.
Look closely at Purchase. Meta's pixel reference lists value and currency as required for Purchase, and contents or content_ids as required for Advantage+ catalog ads.
Statuses, warnings and errors
| Status | Applies to | What Meta says it means |
|---|---|---|
| Active | Pixel or event | Working and sending correctly |
| Warning | Pixel or event | Not set up correctly, or issues that may affect performance |
| Inactive | Pixel or event | Not sending events or data correctly |
| Error | Event | A critical issue such as blocked parameters, duplicate events or a compliance violation |
| Auto-detected | Event | Picked up from site activity without extra code |
A pixel can show Active while its events carry warnings, so click into each event. Common culprits: duplicate pixel code, base code outside the <head>, missing parameters, and ad blockers blocking the pixel. If the same event appears more than once for a single action, check its event IDs before changing anything: the FAQ below explains how to read them.
How do you find your Meta pixel ID?
Your Facebook pixel ID is also your dataset ID: Meta's Dataset Quality API describes dataset_id as the ID of the dataset (pixel). Find it here:
- Events Manager: open Data sources and select your pixel; the ID is listed with its details.
- Pixel Helper: the side panel shows the pixels found on the page.
- Page code: Meta's base code contains the pixel ID twice, in
fbq('init', ...)and in the<noscript>image tag. - Shopify: Sales channels > Facebook & Instagram > Settings > Data sharing settings is where you pick the connected pixel.
Meta's Conversions API setup guide says to use the same pixel ID for browser and server events.
What can't Meta Pixel Helper show?
The extension watches what your browser sends. Conversions API events travel from a server (Shopify's, or your tracking provider's) straight to Meta, so the extension never sees them individually. Meta says Data Advisor can verify a Conversions API installation, but its documentation still points to Events Manager's test events tool for in-depth troubleshooting, and notes that custom conversions and some button-click events may not appear in the extension.
Nor can it show deduplication, match quality, or how your numbers compare with Shopify.
How do you check Conversions API events in Events Manager?
- Test events. Go to Events Manager > Data sources > your pixel > Test events. For server events, Meta's API documentation says to send the generated code as
test_event_code; the events then appear in the Test events window. Remove the code in production, since test events are not dropped. No test code option? Use the Overview. - Overview and connection method. Meta's setup verification guide says the Overview shows events received before deduplication, with a Connection method view showing each event's channel.
- Event deduplication tab. Inside an event's details, this shows the rate of events deduplicated and how often each dedupe key arrived from each source.
Meta pairs a browser event with its server copy when the pixel's eventID equals the server's event_id and the event names match, per Meta's deduplication guide. Our pillar post explains how Meta deduplicates pixel and CAPI events and how to check if the Conversions API is working.
How does Meta Pixel Helper work with Shopify?
Shopify runs pixels in a sandbox
Pixels managed in Settings > Customer events run in sandboxes. Shopify's developer docs say app pixels load in a strict sandbox built on web workers, and custom pixels in a lax sandbox (an iframe). Meta doesn't document how its extension handles these, so treat Pixel Helper results on Shopify as possibly incomplete and confirm in Events Manager.
Shopify has its own tester, the Shopify Pixel Helper. In Settings > Customer events, open a pixel's menu and click Test. A green dot means the event was received and its callback succeeded; red means an error. You may need to give consent first, and Shopify's event names differ from Meta's (checkout_completed may map to Purchase). Shopify says you can run a third-party pixel helper in the same browser session, so open both.
The Facebook & Instagram app
Shopify's Facebook & Instagram app has three data sharing levels. Standard uses the pixel only; Enhanced and Maximum add the Conversions API, which sends the purchase event from Shopify's servers to Meta. Shopify also says that if you added a pixel to your theme code, you need to remove it, or your store will have more than one pixel.
What we see in audits:
- Event IDs beginning with
sh-come from Shopify's own sales channel app. In Chrome DevTools > Network, filter forfacebook.com/trand read theeidvalue (the event ID parameter in Meta's image-pixel example). If one event arrives with ansh-ID and again with another tool's ID, two sources are sending it. - Keep the Facebook & Instagram app installed for your catalog and Shops, but turn its data sharing off if another tool sends your server events.
- Data Advisor may offer to connect your Shopify store to Meta. If another tool already runs your Conversions API, decline or check first.
Theme changes can switch tracking off
Shopify notes that when you change your published theme, you need to re-activate apps in the new theme because they won't be active by default. We've seen a new theme launch silently switch off a tracking app embed, so browser events quietly stopped. After any theme change, check Online Store > Edit theme > App embeds.
How do you check if your Meta pixel is working on Shopify?
In the Shopify accounts we audit, the most common problem is duplicate tracking, not missing tracking. So start with an inventory.
- List every source that could send Meta events: Facebook & Instagram app data sharing, app and custom pixels in Customer events, pixel code in your theme, old Google Tag Manager containers, a forgotten Conversions API Gateway connection, and off-Shopify landing-page snippets pasted into the theme.
- Open a clean Chrome profile with ad blockers off, and accept your cookie banner.
- Walk the funnel with Pixel Helper open: product page, add to cart, checkout, then a test order for
Purchase. Note which pixel IDs appear, and for any event that shows up more than once for one action, note its event IDs. - Check parameters on
AddToCartandPurchase:value,currencyandcontent_ids. - Repeat with the Shopify Pixel Helper for each app pixel.
- Use Test events in Events Manager to watch events arrive.
- Check the Overview the next day. For
AddToCartandPurchase, the browser and server lines should move together. The server line is often a little higher, because it catches events the browser misses, but one line at double or half the other points to a duplicate or missing source. Our guide to Meta event duplication on Shopify shows how to trace it. - Compare yesterday's purchases with Shopify, not today's, matching time zone and attribution window. Meta should never report more purchases than Shopify recorded for the same day. If it does, there's a duplicate source.
- Check Event Match Quality. Meta suggests aiming for 6.0 or higher; our EMQ how-to covers the fixes. Then check how many events carry the ad click ID, using the click ID coverage check in our fbclid guide.
Why is my Facebook pixel not tracking purchases?
- No completed checkout. Shopify's Meta pixel tracks
Purchasewhen a visitor completes a purchase and views the thank-you page, so place a test order. - Consent. Shopify says third-party cookie banners must sync consent through its Customer Privacy API, or pixels might not fire even after a shopper accepts.
- Data sharing or app embed switched off, often after an app update or theme change.
- Ad blockers. Shopify notes they can block a web pixel entirely. Server-to-server events aren't affected, which is why the Conversions API matters.
- Paused data access. Under Shopify's default Optimized setting, Shopify can pause data from a marketing app pixel it judges to be oversharing. Check the pixel's activity log in Customer events.
If you're missing a server-side source, Upstack Signal sends browser and server events that share one event ID, so Meta can deduplicate them.
Frequently asked questions
Is Meta Pixel Helper the same as Meta Ads Data Advisor?
Yes. Meta renamed Meta Pixel Helper to Meta Ads Data Advisor, and existing installs update automatically. The diagnostic features still work, and the new version adds logged-in setup tools for platforms including Shopify and Google Tag Manager.
Can Meta Pixel Helper see Conversions API events?
Not event by event. Conversions API events go from a server to Meta without passing through your browser, where the extension looks. Use Test events and the connection method view in Events Manager instead.
Why does Pixel Helper show my event firing twice?
Compare the event IDs of the two copies. If they're different (in the Shopify accounts we audit, one often starts with sh-, from Shopify's Facebook & Instagram app, and the other doesn't), two sources are sending the event, such as the app plus another tracking app or pixel code left in the theme. Find and remove the extra source.
Why doesn't Pixel Helper show my pixel on Shopify?
Check for an ad blocker, an unaccepted cookie banner, or an app embed switched off after a theme change. Shopify also runs app and custom pixels in sandboxes, so confirm with Shopify's Pixel Helper and Events Manager.
How long do events take to show in Events Manager?
Meta says you should be able to verify events within 20 minutes of sending them. When comparing counts with Shopify, use yesterday's data, not today's.
Key takeaways
- Meta Pixel Helper is now Meta Ads Data Advisor, a Chrome extension that shows browser pixel events.
- It can't show each Conversions API event, deduplication or match quality. Events Manager can.
- On Shopify, run the Shopify Pixel Helper alongside it.
- Duplicate tracking is more common than missing tracking. Two copies of an event with different event IDs mean two sources are sending it.
- Browser and server lines should move together, and Meta should never report more purchases than Shopify for the same day.
Request a demo and we'll review your setup.