Meta Pixel Helper: Is Your Facebook Pixel Not Working?
No purchases in Meta Ads Manager, duplicate leads or no signal at all? Here is how to test the Meta Pixel step by step and find the cause.

When the Facebook pixel is not working, it is usually down to one of a few causes: the pixel does not load, or only loads after consent; it is installed twice; it sends to the wrong pixel ID; the event fires at the wrong moment; value and currency are missing; or the Meta Pixel and the Meta Conversions API count the same event twice. With the Meta Pixel Helper (now Meta Ads Data Advisor) and the test events in Events Manager, you can usually find the cause quickly. A fixed order is important: first check that the pixel loads, then that the right events arrive, and finally that the data in them is correct.
Typical signs that the Meta Pixel is not working
Not every problem is obvious straight away. Sometimes nothing arrives, sometimes too much arrives, and sometimes only the values are wrong. Take these signs seriously:
- Meta Ads Manager shows no purchases or leads, even though orders and enquiries are coming in.
- Meta reports clearly more purchases than your shop system shows.
- Revenue is missing or far too high, and the ROAS looks unrealistic.
- Events Manager shows warnings about missing parameters or about deduplication.
- The number of events suddenly drops on a particular day, for example after an update.
Note down which sign applies to you and since when. That saves time later, because you will search in the right place.
Meta Pixel Helper: the quick first test in the browser
The Meta Pixel Helper is a free browser extension from Meta. According to Meta, it is now called Meta Ads Data Advisor, runs in Google Chrome and Microsoft Edge, and anyone who had installed the Pixel Helper gets the new version automatically. After installation, an icon appears in the browser’s toolbar. Open your website, agree in the cookie banner and click the icon. The Pixel Helper shows you which pixel IDs were found on the page and which events were sent, such as PageView, ViewContent or Lead. Next to each event, you see the parameters sent along and any warnings or errors.
When testing your Facebook pixel, pay attention above all to three things. First: is there only one pixel ID, and is it yours? Agencies and former service providers often leave behind a second pixel that sends to someone else’s account. You find the right ID in Events Manager under your data source. Second: if the same event appears twice on the same page view, the pixel is installed twice. Third: also check the page without consent. If you decline in the banner, the Pixel Helper should report no pixel, or the pixel should send no data. This article is not legal advice, but a pixel that fires before consent is an error you should fix.
→ Cookie banner with Consent Mode v2: compliant, with no monthly licence
How do you run a Meta pixel test in Events Manager?
The extension shows what the browser sends. Whether it arrives at Meta and how Meta understands it, you see in Events Manager. Select your data source there and open the area for testing events. Enter the address of your website and open it from there. Everything you now do on the page appears in the list after a short time: page views, clicks on “Add to basket”, submitted forms, purchases. For each event, you see whether it came from the browser or the server and which parameters it contains.
Here, play through your customers’ most important path once, from start to finish. For a shop, that means: view a product, add it to the basket, go to the checkout and complete a test order. For a service business, it means: fill in the form and submit it. If the Conversions API is set up, you can also use a test code so that server events appear in this view too, without distorting your real data.
The most common mistakes and how to recognise them
An event that fires too early is one of the most common mistakes. If Lead is sent on the click of the submit button, Meta also counts forms that were never sent because of an error. If Purchase is sent on the click of “Buy now”, Meta counts abandoned payments too. The right signal is the confirmation: the thank-you page, the order confirmation or an event that reports the form after successful submission.
| Error | Signs | Solution |
|---|---|---|
| Pixel does not load | The extension finds no pixel, even after consent | Check the installation and trigger in Google Tag Manager |
| Pixel installed twice | The same event twice on the same page view | Remove one installation, for example in the shop plugin |
| Wrong pixel ID | Events in the browser, nothing in your data source | Compare the ID with Events Manager |
| Event fires too early | More leads or purchases than real enquiries | Trigger on the confirmation or thank-you page |
| Value or currency missing | Notices about parameters, no revenue in Meta Ads Manager | Send value as a number, currency as a code such as EUR |
| No deduplication | Duplicate purchases despite one pixel | Same event_id and same event name for pixel and Conversions API |
You recognise missing values in Events Manager by notices about parameters. For Purchase, Meta needs value as a number and currency as a three-letter code. A common mistake is a value as text with a comma, for example “49,90” instead of 49.90, or a value that includes shipping and taxes in one place and not in another. Decide which amount is reported and keep it the same on all routes. Another point is domain verification in the Business settings at Meta. It confirms to Meta that the domain belongs to your business. It is not required for sending events, but it is part of a clean set-up and can be done quickly later.
Consent also often leads to a Meta Pixel that seems not to work. If the pixel loads only after consent, that is correct. But if the consent never reaches the pixel, because the cookie banner does not pass its decision on to Google Tag Manager, the pixel stays silent even after a click on “Accept all”. So test both cases separately in a private window: decline once and check that nothing is sent, then agree once and check that PageView arrives immediately, without you having to reload the page. If the page first has to be reloaded, you miss the first page view of every new visitor. With a wrong pixel ID, the case is clear: the Pixel Helper shows events, but nothing arrives in Events Manager for your data source. Compare the ID character by character.
→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant
Pixel and Conversions API: avoiding double counting
Many shops now send events to Meta by two routes: through the pixel in the browser and through the Conversions API from the server. This makes sense, because the server still reports events even when the browser blocks them. But so that Meta does not count a purchase twice, both routes must send the same event_id and the same event name. Meta then recognises the two reports as one event and keeps only one. If the event_id is missing on one route or differs, you see duplicate purchases or a notice about deduplication in Events Manager. So check in the test area whether, for the same purchase, a browser event and a server event with the same ID arrive.
Worked example: a small online shop with duplicate purchases
A natural cosmetics shop on WooCommerce sees almost twice as many purchases in Meta Ads Manager as in the shop. The Pixel Helper shows two Purchase events with the same pixel ID on the order confirmation. The cause: a plugin for the Meta catalogue switched on its own tracking in the last update, while the pixel continues to run through Google Tag Manager. In addition, the plugin sends purchases through the Conversions API, but with a different event_id from the pixel in Google Tag Manager. The solution: the tracking in the plugin is switched off, and the pixel and Conversions API run through one source with a shared event_id. In the test area of Events Manager, there is then one browser event and one server event per purchase, and one of them is marked as deduplicated. The numbers in Meta Ads Manager match the shop again.
Having the Facebook pixel tested instead of searching yourself
If you have no time for the Facebook pixel test, the free Trackum check opens your site three times in a real browser: cookie banner ignored, declined and accepted. It shows whether the Meta Pixel loads, whether it already sends before consent and whether page views are counted twice. The check does not trigger purchases or forms, which you test with a test order in Events Manager. Every finding comes with a fixed price to fix it. The repair for €79 excl. VAT fixes all findings in your existing Google Tag Manager. If you need Meta set up from scratch, or the Conversions API in addition, both are available as extras at €50 each, cleanly deduplicated and only with consent.
Frequently asked questions
Does the Meta Pixel Helper also work on a smartphone?
No. The Meta Pixel Helper, now called Meta Ads Data Advisor, is an extension for Google Chrome and Microsoft Edge on a computer. To test on a phone, open Test events in Events Manager and visit your site on the smartphone. The events then appear in the same list.
Why does the Meta Pixel Helper not show a pixel?
Either the pixel is not installed, or it only loads after consent in the cookie banner. Agree in the banner and reload the page. If it still does not appear, check whether a plugin update or a theme change has removed the code.
Why does Meta count purchases twice?
Usually the pixel is installed twice, for example through a shop plugin and additionally through Google Tag Manager. Another common reason is a Conversions API without a matching event_id, so that Meta does not recognise the browser event and the server event as the same.
Do I have to send a value and currency with the purchase event?
Yes. For the Purchase event, Meta requires a value as a number and a currency as a three-letter code, for example EUR. If they are missing, Meta Ads Manager cannot calculate revenue or ROAS.
Sources
- Meta for Developers: Meta Ads Data Advisor (formerly Meta Pixel Helper) developers.facebook.com
- Meta for Developers: Meta Pixel API reference developers.facebook.com
- Meta for Developers: Handling duplicate Pixel and Conversions API events developers.facebook.com
- Meta for Developers: Domain verification developers.facebook.com
Read more
FeaturesCookie banner with Consent Mode v2: compliant, with no monthly licence
Reject on the first layer, settings per purpose, Consent Mode v2 with every consent type and a record of each choice. No monthly licence.
FeaturesSetting up Google Consent Mode v2 correctly: no warning in Tag Assistant
The most common warning in Tag Assistant says a tag read consent before a default was set. How to avoid it, and what else matters.
FeaturesMarketing dashboard with GA4 and Google Ads: every number on one page
Visitors, leads, orders, ad spend and ROAS per campaign on one page, compared with the previous period. One link, nothing to set up.
FeaturesRevenue from your CRM, shop and ERP in one dashboard: HubSpot, Shopify, Odoo and more
Google Analytics only sees what happens on the website. Orders by phone or email are missing. With a data connection, the real revenue from your system appears in the dashboard.
FeaturesWebsite leads with their source in your CRM: HubSpot, Pipedrive, Brevo, Salesforce or webhook
Where did the lead come from? The CRM handover writes source, campaign and click ID into the CRM with every enquiry, without a form plugin.
FeaturesOffline conversions: report sales from your CRM to Google Ads and Meta
Google Ads and Meta learn from what you report to them. If they only get form fills, they optimise for form fills. With offline conversions, they optimise for sales.