You are reading this because your facebook pixel is not working. Your ads are running blind, events are missing, and you cannot track conversions properly. This happens when the code is missing, a browser blocks the script, or the event parameters are formatted incorrectly. Here is how to find the exact cause and fix your tracking.
When your facebook pixel is not working, you have to stop guessing and look at the actual data flow. Most tracking failures follow a predictable pattern. You can diagnose the problem in minutes by checking the installation, the browser environment, and the event payloads.
The base code is missing or placed incorrectly
The most common reason your tracking fails is a basic installation error. The code might be entirely absent from the page. It might also be sitting in the wrong part of your website architecture. Meta requires the base code to sit inside the header section of every single page. If you put it in the footer or inside a dynamic widget, it will not fire reliably.
You can confirm this instantly by running your website address through a facebook pixel checker to see if the base code is present and readable on the page.
To fix this, you must open your website builder or tag management system. Find the global header code injection area. In WordPress, this is often found in a dedicated header plugin or your theme settings. In Shopify, you edit the theme file directly. Paste the base pixel code exactly as Meta provides it. Do not alter the script. Save the changes and clear your website cache.
You installed the wrong pixel ID
You might have the code on the page, but it is sending data to a completely different ad account. This happens frequently if you manage multiple business managers. It also happens if you copied an old snippet from a previous website build. One incorrect digit means all your data flows to the wrong destination.
You can confirm this error using the Meta Pixel Helper browser extension. Open your website in Google Chrome. Click the extension icon in your toolbar. Look at the long number next to the pixel name. Now open your Meta Events Manager in another tab. Compare the ID on your website to the ID in your data sources. If they do not match exactly, your data is going to the void.
To fix this, you must delete the incorrect code block from your website header. Go back to your active Events Manager. Copy the correct base code and paste it into your site. If you use a native platform integration, you must disconnect the old account and authenticate the correct one.
Duplicate pixels are firing on the same page
Firing the exact same pixel twice inflates your metrics. It ruins your ad optimization because Meta thinks one user is performing multiple actions. This usually happens when you install the code manually in the header, but a plugin or native integration is also pushing the same pixel ID.
You can confirm this by looking at the Meta Pixel Helper extension. If you see the PageView event listed two or three times under the same pixel ID on a single page load, you have a duplicate installation. You might also see a warning in Events Manager about redundant events.
You must choose one single method of installation. If you want to use a native integration or a dedicated tracking plugin, keep it. Then go into your website header and delete the manual code snippet. Never use both methods at the same time. If you cannot find the source of the duplicate code, reach out through our contact page and we will find it for you.
Ad blockers and browser privacy settings are stopping the script
Sometimes the installation is perfect, but the visitor never triggers the code. Modern browsers like Safari and Brave block third party tracking scripts by default. Ad blocking extensions do the exact same thing. If you are testing your own website with an ad blocker turned on, your facebook pixel is not working from your perspective.
You can confirm this by changing your local environment. Turn off all ad blockers in your browser. Disable strict tracking protection in your browser settings. Reload your website page and check the Meta Pixel Helper again. If the pixel fires now, your code is completely fine. The issue is purely client side blocking.
You cannot force a user browser to accept a third party client script. To capture data from users with ad blockers, you need to move the tracking away from the browser entirely. You do this by setting up server side tracking to send the event data directly from your server to the Meta Conversions API. This bypasses browser restrictions completely. This requires a developer to configure a cloud server and a data routing system.
Event parameters are missing or invalid
Your base code might work perfectly, but your specific conversion events are failing. Meta will reject events if the data payload is formatted incorrectly. The most common failures happen on purchase events when the currency or value parameters are broken.
You can confirm this by opening Meta Events Manager. Click on the Diagnostics tab. Look for error messages about missing values. Meta flags events with a missing or invalid three letter currency code. They also flag events where the value parameter is empty or contains letters.
You have to format the event code properly. The currency code must match standard three letter ISO formats like USD or GBP. The value field must be a decimal number greater than or equal to zero. It cannot contain letters. It cannot contain special characters. It cannot contain currency symbols or commas. If you do not know how to edit JavaScript event payloads, you need to hire a developer to rewrite your conversion tags. You can view our pricing to see what a professional rebuild costs.
Mismatches between the pixel and the Conversions API
If you run both the browser pixel and the Conversions API, Meta tries to deduplicate the events. If the data does not match, the deduplication fails. This creates double counting and breaks your reporting.
You can confirm this by opening the Diagnostics tab in Events Manager. Look for a warning about mismatches in currency and value parameters. This means the browser sent one value, but the server sent a completely different value for the exact same user action.
Check your event setup in both environments. Make sure both the client side pixel and the server side API send the exact same event name. They must send the exact same value. They must send the exact same currency. They must also send a matching event ID so Meta knows it is the exact same action. If the event ID is missing from either payload, deduplication is impossible.
The event code is firing too early or too late
Timing issues destroy data accuracy. If your event code fires before the base pixel loads, the event is lost. If your event code fires after the user navigates away from the page, the event is also lost.
You can confirm timing issues by watching the network tab in your browser developer tools. Load your website and watch the requests going to Facebook. If you see a purchase event request failing or showing as cancelled, the user is leaving the page before the script finishes executing.
To fix this, you must structure your code execution properly. The base pixel must load first. The event code must load second. If you track button clicks, you must make sure the tracking script fires before the browser redirects the user to the next page. You can use Google Tag Manager to control the exact firing sequence of your scripts.
JavaScript exceptions are blocking execution
Your website relies on JavaScript to function. If another script on your page breaks, it can stop all subsequent scripts from running. This means a broken image slider or a faulty popup plugin can prevent your tracking code from executing entirely.
You can confirm this by opening your browser developer tools. Right click on your website and select inspect. Click on the console tab. Reload the page. If you see a wall of red text and error messages, you have JavaScript conflicts. If these errors appear before the Meta scripts load, your tracking will fail.
To fix this, you must isolate the broken script. Disable your website plugins one by one. Reload the page and check the console after each deactivation. When the red errors disappear, you have found the culprit. You must either update that specific plugin, replace it, or hire a developer to fix the code conflict.
Standard events are misconfigured as custom events
Meta relies on standard events to optimize your ad delivery. Standard events include actions like ViewContent, AddToCart, and Purchase. If you misspell these event names, Meta treats them as custom events. Custom events are useful for building audiences, but they are terrible for ad optimization.
You can confirm this error by checking the Overview tab in Events Manager. Look at the list of events receiving data. If you see an event named Purchased or Add To Cart, you have a naming error. Meta expects Purchase and AddToCart. The exact capitalization and spelling matter.
To fix this, you must edit the event code on your website. Change the custom event names to match the exact standard event names required by Meta. Update your Google Tag Manager tags or your website theme files. Once you correct the spelling, Meta will recognize the actions and use them to optimize your campaigns.
Low traffic warnings in Events Manager
Sometimes you see a warning that your pixel has not received any activity recently. This does not always mean your code is broken. If your website has very low traffic, the pixel will sit idle until a real user visits the page.
You can confirm this by looking at your website analytics. Open your Google Analytics account and check your daily visitor count. If you only receive a handful of visitors each week, the Meta pixel will naturally show periods of inactivity. The warning in Events Manager is simply an alert that data volume has dropped.
To fix this, you must generate test traffic yourself. Open a private browsing window and navigate to your website. Click through a few pages and trigger your core events. Wait five minutes and check Events Manager again. If your test events appear in the data source overview, your tracking is completely fine. You just need to run more traffic to the website.
How to test your setup properly
You need a reliable testing process to prove your fixes worked. Never assume the tracking is fixed just because you changed a line of code. You must verify the data flow from your website all the way to the Meta servers.
Create a testing routine using the official tools provided by Meta.
- Open Meta Events Manager and select your data source.
- Click on the Test Events tab.
- Enter your website address and click the open website button.
- Perform the exact actions you want to track.
- Click buttons, add items to the cart, and complete a test purchase.
- Keep the Test Events tab open on a second monitor and watch the events log in real time.
If the events appear in the log with the correct parameters, your setup is fixed. If they do not appear, you still have a problem. You can read the official Meta troubleshooting documentation to check for deeper account level restrictions. Sometimes an ad account is restricted, which stops the pixel from processing new data entirely.
Moving beyond basic browser tracking
Fixing a broken script is the first step. Relying entirely on that script is a mistake. Browser tracking gets less reliable every single month. Apple updates, privacy laws, and default browser settings are actively destroying client side data collection.
If you want accurate ad attribution, you have to upgrade your infrastructure. Look at your current data sources in Events Manager. If you only see browser events, you are missing a massive percentage of your actual conversions. You are paying for ads but failing to record the results.
You must take control of your own data routing. You can read more about building a robust data foundation on our blog. Building a reliable system takes time and technical knowledge.