Meta pixel not working: What should you check if events are missing, including purchases and forms?

What does Meta Ads Data Advisor (formerly Pixel Helper) show?

Meta’s browser extension lets you see which pixel and events load on a page without entering the advertising account; the extension is now called Meta Ads Data Advisor rather than Meta Pixel Helper. Meta’s about Meta Ads Data Advisor page refers to the tool by its former name, Meta Pixel Helper, and describes it as a free extension for Google Chrome and Microsoft Edge.

According to the same page, the extension verifies pixel installation and event firing, and flags broken events or missing parameters such as price and currency. Meta for Developers documentation states that it shows pixel statuses such as Active, Warning, and Inactive, and lists duplicate pixel code among common errors. Pay attention to the following in use:

• Ad blocker: Meta states that browser ad blockers must be disabled so the extension can detect the pixel and website events.
• Page-by-page checks: Page views should appear on every page, while purchases should appear only on the confirmation page.
• Tag manager: If code was added through Google Tag Manager, it will not appear in the page source; Meta recommends troubleshooting in the tag manager in this situation.

When the extension sees events but data is missing from Events Manager, the most common cause is the page’s pixel ID differing from the pixel used in the advertising account.

Wrong pixel ID, duplicate pixels, and misspelled event names

In many accounts where the Facebook pixel appears not to work, the pixel actually works but sends data to another pixel or an incorrectly named event. If an old agency’s pixel remains on the website while ads use a new pixel, the campaign’s connected pixel appears empty in Events Manager. Check this by comparing the pixel ID displayed in the extension with the data source selected in the ad set side by side.

Event name spelling directly affects the result too. Meta’s best practices page states that events are case-sensitive: writing viewcontent instead of ViewContent creates a separate custom event in Events Manager. Likewise, a misspelled Purchase event records the purchase as an unrecognized custom event rather than a standard event.

Two pixels are not always an error. Meta acknowledges that two pixels may be needed when two different agencies advertise for a business. However, Meta for Developers’ tracking events with multiple pixels documentation explains that when multiple pixels are initialized on one page, an event can go to all of them and inflate reports. It recommends trackSingle to send an event to only one pixel; adding the same pixel twice through theme code and a plugin is a separate cause of double counting.

Why are purchase and form events missing? Thank-you pages and in-page forms

If page views arrive but purchase or form events do not, the real problem is usually the page the event is attached to rather than “the Meta pixel not working”. Meta’s specifications for standard events page defines purchase with the example of reaching a thank-you or confirmation page, and Lead with a form submission example. The sample Purchase event code also includes value and currency parameters.

Common points where the chain breaks include:

• In-page form: If the address does not change after submission and a success message appears on the same page, an event attached to the thank-you page never fires.
• External checkout page: If payment completes on an intermediary page without returning to the website, the event on the confirmation page may not run.
• Theme or plugin change: If a new form plugin uses a different success flow, the old configuration stops working unnoticed.
• Missing parameter: If a purchase event arrives but value or currency is empty, a warning may appear on the Diagnostics tab.

For in-page forms, measurement is attached to successful form submission rather than page loading. How this is done varies by form plugin; choose the correct method by actually submitting the form in Test events and confirming that the event arrives once. If the same form also needs measuring in Google Ads, the form steps in the Google Ads not recording conversions guide can be carried out alongside this check.

How do cookie consent and consent management silence the pixel?

If Meta pixel events stopped appearing after a cookie banner was installed, meaning events suddenly decreased or stopped, consent management is the first suspect; the pixel does not send data before consent is obtained. Meta for Developers’ pixel consent management documentation explains that revoke pauses pixel transmissions and grant starts transmission after cookie consent is given. The same document emphasizes that every company is responsible for its own regulatory compliance.

During diagnosis, seek answers to the following:

1. Does accepting the banner actually send a consent signal to the pixel?
2. Do events appear in the test tool on the same page after consent?
3. Is the pixel tag connected to the correct consent category in the tag manager?
4. Is the absence of events from visitors who declined read separately in reporting as expected behavior?

If consent rates are low, fewer events are a natural result of consent choices rather than a fault. The problem is an event not being sent despite consent being granted. Note: This section provides technical information and is not legal advice regarding KVKK (Turkey’s Personal Data Protection Law); having cookie wording and the consent setup confirmed by legal counsel is recommended.

iOS, ad blockers, and Conversions API: What do Meta’s documents say?

Because the pixel runs in the browser, browser errors, connection problems, and ad blockers can cause some events to be lost; Meta recommends using Conversions API alongside the pixel to address this gap. Meta’s about Conversions API page states that data from the API is less affected by browser loading errors, connection problems, and ad blockers than Meta pixel data.

For iOS, Meta’s own explanation is more limited. Its Aggregated Event Measurement page says this protocol helps compensate for limited measurement of website conversions from devices running iOS 14.5 and later. The same page notes that events sent through Conversions API may also be processed under Aggregated Event Measurement limitations; a server connection therefore does not resolve every missing item on its own.

Conversions API setup is outside this article’s scope, but diagnosis requires knowing which method is in use. Meta’s Conversions API setup options page lists three routes:

• Meta-supported Conversions API: Free and works alongside the pixel; events shared through the pixel are also shared this way and automatically deduplicated.
• Direct integration through code: Requires a developer; Meta estimates 2 to 4 weeks for new integrations.
• Partner integrations: Can be configured in commerce platforms such as Shopify, WooCommerce, Wix, and BigCommerce, and partner platforms such as Google Tag Manager.

Meta’s best practices page calls sharing the same events through both the pixel and Conversions API a “redundant event setup” and recommends it to capture events the pixel might miss because of network issues or page loading errors.

Event deduplication: If the same purchase is counted twice

If the pixel and Conversions API send the same event, Meta must be able to match the two records as one event; without that matching, one purchase can count twice. Meta for Developers’ deduplicating pixel and server events documentation explains that the recommended method is matching event IDs and event names. The pixel’s eventID must match the server’s event_id, and the pixel’s event name must match the server’s event_name.

The document’s rules are used directly in diagnosis:

• 48-hour limit: Events are deduplicated if they arrive within 48 hours after the first event with the same ID is received.
• The first arrival remains: Of matching events, the first received is generally preferred and the later event discarded.
• Alternative method: Matching through fbp or external_id works only when the browser event arrives first and the server event afterward.

If purchase counts significantly exceed order counts in the store dashboard, first check whether events appear as “deduplicated” in the test tool. In the opposite case, where events are missing, check whether the server side sends no events or IDs are generated differently each time.

Domain verification and Aggregated Event Measurement: Current status

The “prioritize 8 events per domain” step found in older guides is no longer mandatory; Meta has removed this configuration for website events. Meta’s about Aggregated Event Measurement page states that no steps remain necessary for events to be processed through Aggregated Event Measurement, and that the update brings the following changes to accounts with access:

• Prioritizing 8 conversion events per domain for web conversion optimization is no longer required.
• The Aggregated Event Measurement tab in Events Manager has been removed.
• Domain verification is not required for event configuration, though it may be required for other reasons.
• Selecting a conversion domain when creating a campaign in Ads Manager is unnecessary.

Since Meta says the update is rolled out gradually, some accounts may still see the old screen. Domain verification remains important for link editing permissions: Meta’s about domain verification page explains that verification is free and helps manage editing permissions for links and content. Do not conclude that the Meta pixel is broken because the 8-event setting cannot be found; that screen’s absence is part of the current situation.

Checklist when you suspect the Facebook pixel is not working

Starting with the most fundamental layer when the Facebook pixel is not working avoids wasting time on small settings. We follow this sequence in account reviews:

1. Pixel status: Confirm in Events Manager that the pixel is Active and receives page views.
2. Correct pixel: Compare the website’s pixel ID with the data source selected in the ad set.
3. Live test: Actually make a purchase and submit a form on the website while using the Test events tab.
4. Diagnostics: Read important red issues and yellow warnings and follow their instructions.
5. Extension check: Use Meta Ads Data Advisor to look for duplicate code and missing parameters.
6. Event name and page: Verify correct event spelling and firing at the correct step.
7. Cookie consent: Confirm in the test tool that events are sent after acceptance.
8. Server side: If Conversions API is present, check that events also appear on the server side.
9. Deduplication: Verify that the same event from two channels counts only once.
10. Delay: Allow enough time for data processing before interpreting the report.

Keeping this order prevents wasted effort, such as adjusting deduplication while the pixel ID is wrong.

Measurement first, budget second: When does specialist support make sense?

Increasing the budget while the Meta pixel is not working means increasing spending without knowing which ad generates sales; measurement is repaired first, then a budget decision is made. A campaign that does not receive correct event data cannot learn what works. Even after measurement is corrected, the results of a budget increase cannot be predicted; measurement only makes a data-based decision possible.

The differences between common practice and a systematic approach are:

• Instead of increasing the budget because “the ad is not selling”: First confirm in the test tool that the purchase event is actually recorded.
• Instead of creating a new pixel: Find why the existing pixel receives no data; a new pixel often worsens duplicate pixel problems.
• Instead of constantly changing the campaign: Distinguish whether the missing event breaks on the website, in consent management, or on the server side.

If the pixel and Diagnostics screens are clear but the ad never goes live, the problem concerns delivery rather than measurement; the Instagram ad not publishing guide helps in that case. If the account is restricted, the steps in the Meta ad account disabled article come first. For budget planning, the Instagram advertising prices page explains which factors determine costs.

Specialist support becomes useful when problems overlap: an event appearing in the test tool without a reported conversion, suspected double counting, broken server-side integration, or events stopping after a theme change are typical examples. At Onur Freelance, this review is part of the Meta advertising management service, and its scope is clarified in the initial consultation. Since Onur Freelance is not Meta’s official support channel, it cannot make decisions on Meta’s behalf; requests on Meta’s side are handled through the account’s own support channels.