← All posts

Blog

Meta PixelTroubleshootingServer-Side Tracking

Facebook Pixel Not Firing? A Step-by-Step Fix, Plus the Server-Side Backup

22 November 20268 min readSyncBeacon Team

When your Facebook pixel is not firing, Meta never sees the visit, the add-to-cart or the purchase. Ads Manager shows fewer results than your shop reports, and campaigns optimise on a thinner signal than they should. This guide walks through how to confirm the problem, the causes we see most often, and what to do when the browser simply cannot be trusted to deliver the event.

The same steps apply whether you searched for "Meta pixel not working", saw a warning in Events Manager, or hit the classic pixel not tracking purchases symptom while page views look fine. Work through them in order. Most problems are found in the first four.


Step 1: Confirm it is actually not firing

Do not guess. Check what the browser sends, then check what Meta received. They are two different questions.

Use Meta Pixel Helper

Meta Pixel Helper is a free Chrome and Edge extension. Meta has since renamed it Meta Ads Data Advisor, and the diagnostic features still work. Open your store, click the extension icon and look for a badge. No badge means no pixel loaded on that page.

Meta also notes that button-click events and some custom events may not show up in the extension even when they work. Treat the helper as a quick signal, not a verdict.

Use Test Events in Events Manager

Open Events Manager, pick your pixel and go to the Test Events tab. Enter your store URL, open it in the window Meta provides and click through the funnel. Events that arrive appear within moments. Events that never appear were never received, whatever the helper said.


Step 2: Work through the common causes

This table maps the symptom to its likely cause. The sections below explain each one.

What you seeLikely causeHow to check
No pixel badge on any pageBase code missing, in the wrong place or blockedView page source, search for the pixel ID
Pixel on every page, no eventsStandard events not installed or fired too earlyTest Events while clicking the funnel
Events fire twiceDuplicate pixel code (theme plus app plus tag manager)Meta Pixel Helper shows the same pixel or event repeated
Fine for you, missing for customersAd blockers, browser privacy features, consent bannerTest in a clean browser, then with a blocker on
Page views work, purchase does notThank-you page does not load your pixel codePlace a test order and watch Test Events
Event arrives but looks wrongWrong event name, missing value or currencyOpen the event in Events Manager and read its parameters

The base code is missing or misplaced

Meta's guidance is to place the pixel base code in the <head> of every page you want to track, with standard events loading after it. If you pasted the code into a footer block or a page-specific field, it will miss pages. View the page source and search for your pixel ID to see whether it is there.

The code is there twice

Duplicate pixel code is one of the setup errors Meta lists. It usually happens when a theme snippet, a store app and a tag manager container all install the same pixel. Duplicates can inflate counts and make deduplication harder, so keep one source of truth and remove the others.

Wrong pixel ID, wrong event name

A single wrong digit in the pixel ID sends data to a different pixel. Event names are case-sensitive: Purchase is a standard event, while a misspelled or lowercase variant becomes a custom event that your campaigns do not optimise on. Meta's tooling also flags missing parameters such as value and currency on purchase events.

The event only fires on a page load

Meta states that user-triggered events, such as button clicks, are not reliably detected unless they reload the page or trigger a direct pixel call. If your add-to-cart happens through a script that never calls the pixel, nothing is sent. The same applies to a purchase event that depends on a thank-you page the customer never reaches.

The thank-you page does not run your code

On some platforms the checkout and order-confirmation pages do not load your theme code, so a pixel pasted into the theme sees page views but never the purchase. Check where your platform expects pixel code for checkout, or use its own Meta integration. This is the most common reason for a pixel that is not tracking purchases while everything else works.

The visitor blocked it

This is the one you cannot fix in settings. Ad blockers and some privacy-focused browsers stop the pixel script from loading. A consent banner that holds the pixel until the visitor accepts does the same for everyone who declines. In both cases the pixel is behaving as designed. Your test looks fine because your own browser has neither.

Key takeaway: Fix what you can in the browser (placement, duplicates, event names, the checkout page), then accept that a browser pixel will always miss some visitors. The remaining gap needs a server-side event.

Step 3: Add the server-side fix

The Meta Conversions API sends events from a server rather than from the visitor's browser. Meta recommends running it alongside the pixel as a redundant setup: share the same events through both, and make sure they can be deduplicated.

For purchases, SyncBeacon does this without touching your theme. It reads the order from your store and forwards it to Meta, so the event does not depend on the thank-you page loading, a blocker allowing a script, or the visitor accepting a banner script.

Then connect Meta in Integrations with Facebook login and your pixel ID. Each Meta event carries a hashed email and phone where available, the fbc and fbp browser IDs, IP address, user agent, value, currency and an event_id for deduplication. If you want the full list of match keys and how to improve them, read how to improve Meta Event Match Quality.

How to verify it worked

  1. Place a test order on your store.
  2. In Events Manager, open Test Events and look for the Purchase event. Its source should be Server.
  3. If the pixel also fired, check that Meta shows the two events as deduplicated rather than counted twice.
  4. In SyncBeacon, open Conversions and check the delivery status for Meta on that order. Per-destination failures are listed there.

Limits worth knowing


Quick answers

Why is my Meta pixel not working only on some devices?

Different browsers and extensions treat the pixel script differently. Test in a clean browser profile, then with a content blocker enabled, and compare the results in Test Events.

Can I check my pixel without installing anything?

Yes. The Free Tracking Audit scans public pages for the Meta Pixel and other tags and reports which are present. It cannot confirm that Conversions API events are being delivered, so use Test Events for that.


Sources

Get started

Stop losing purchases to a pixel that cannot fire

Connect your store and Meta in one setup. Purchases are sent from the server, with delivery status per ad platform.

Get started