You click the button in Events Manager, but the send test traffic facebook pixel not working error stops you cold. The dashboard shows no activity. Your pixel is either blocked by your own browser, installed on the wrong domain, or missing the correct event parameters. Here is how to find the break and fix it.
Before you rewrite your website code, you need to isolate why send test traffic facebook pixel not working errors happen. The problem is usually on your local machine. When you see this status, the issue is rarely a total platform failure. The Meta dashboard relies on your local browser to trigger the initial page view. If your local setup blocks the request, the dashboard stays blank. You need to test the connection systematically.
Your browser is blocking the tracking script
Most test traffic failures happen because the person testing the site has an ad blocker turned on. Meta relies on a network request from your browser to their servers. If you use Brave, Safari, or a Chrome extension like uBlock Origin, that network request is killed before it leaves your computer.
You click the test button in Events Manager. The page opens. Your browser blocks the script. Events Manager receives nothing.
To rule out a missing script, run your URL through a Facebook pixel checker to see a plain text list of every Meta script firing on your page. If the script is present on the live site but Events Manager shows no activity, your browser is the problem.
Turn off all ad blockers. Disable strict tracking protection in your browser settings. Open an incognito window with extensions disabled. Go back to Meta Events Manager and send the test traffic again. If the activity registers, your code is fine.
The pixel ID does not match your ad account
Business Manager accounts often contain multiple pixels. You might install one pixel on your website but look at the Events Manager for a different one.
Open your website in a normal Chrome window. Press F12 to open the developer tools. Click the Network tab. Type "facebook.com/tr/" into the filter box. Refresh your page.
You will see a network request appear in the list. Click it. Look at the Payload tab. You will see a parameter called "id" followed by a long number. This is the pixel ID firing on your website.
Copy that number. Go to Events Manager. Look at the top left corner of the screen. The ID listed under your data source must match the ID from your network tab exactly. If the numbers are different, you are sending test traffic to a pixel you do not own or a pixel attached to an old ad account.
To fix this, you must log into your website content management system. Locate the header code injection area. Delete the old base code and paste the correct code from your current Events Manager.
Your website cache is serving an old page
You add the tracking code to your website header. You save the changes. You send test traffic. Nothing happens.
This occurs when your website uses a caching plugin or a content delivery network like Cloudflare. The server builds a static version of your website to serve to visitors. When you add the Meta script, the server does not immediately build a new static version.
Your browser loads the cached version of the page. The cached version does not contain your new tracking code.
You must purge your website cache. If you use WordPress, clear your caching plugin. Navigate to the settings panel of WP Rocket or W3 Total Cache and click the purge all button. If you use Cloudflare, log in and turn on development mode to bypass the edge cache entirely.
Once the cache is clear, reload your website and check the network tab again. The network request should now appear with a status code of 200. If you use a managed hosting provider, you must also clear the server cache from your hosting dashboard. Caching layers stack on top of each other. You must clear every layer before your new tracking code reaches the live browser.
Meta Pixel Helper shows missing parameters
Sometimes the page view event fires, but specific conversion events fail. You can diagnose this using the Meta Pixel Helper Chrome extension.
Install the extension and click the icon while on your website. It will list every event firing on the page. If an event has a yellow warning icon, you have a formatting error in your code. You can review the official Meta Pixel error documentation to see a full list of warnings.
Here are the most common formatting errors that break test traffic:
- Missing currency code: Your code snippet must contain both a value and a currency parameter. The currency code must match the standard three letter ISO format, such as USD or GBP.
- Invalid price format: The value field must contain a decimal number greater than or equal to zero. You cannot include letters, currency symbols, or commas. If your website outputs a price like "$1,000.00", the pixel will fail. You must format it as "1000.00".
- Mismatched parameters: The currency and value parameters differ between your browser setup and your server setup. This causes deduplication failures.
If you see these errors, you need a developer to rewrite the data layer variables on your website. The raw output from your shopping cart must be cleaned before it is passed to the Meta script.
Server side API payloads are failing
If you rely on the Conversions API alongside the browser pixel, testing becomes more complex. The browser pixel sends data directly from the user. The Conversions API sends data from your server to the Meta Graph API.
When server events fail to appear in the test events tab, the issue is usually missing user data or incorrect hashing.
Meta requires user data like email addresses and phone numbers to be hashed using the SHA-256 algorithm before they leave your server. If you send plain text emails, the Graph API will reject the payload. The event will not appear in your test traffic.
You can test your server payload by sending a cURL POST request directly to the Graph API at the version 16.0 endpoint. You need your pixel ID and a valid access token. Include the event name, the event time, and the hashed user data.
If the Graph API returns an error, your server code is formatting the payload incorrectly. You must check your server logs to see the exact response from Meta. Fixing this requires deep technical knowledge of your specific backend architecture. If you cannot resolve the API errors, you should consider moving to a managed server side tracking setup. This removes the need to maintain the API connection yourself.
You have not verified your domain
Meta restricts which domains can send data to a specific pixel. This prevents competitors from putting your pixel on a spam website to ruin your data.
If your pixel is installed correctly but Events Manager rejects the test traffic, your domain might not be authorised.
Go to your Business Settings. Click on Brand Safety and Suitability. Click on Domains. Your website domain must be listed here. It must have a green verified badge next to it.
If your domain is not verified, you must add a DNS TXT record to your domain registrar. Meta provides this record in the Business Settings interface. Once you add the record, click the verify button. DNS changes can take a few hours to propagate.
After the domain is verified, you must assign the domain to your pixel. Go to the pixel settings and configure your web events. Once the domain is linked, your test traffic will start appearing in the dashboard.
Content security policies are blocking the script
Some strict website setups use a Content Security Policy to prevent malicious code from executing. This policy tells the browser exactly which external servers are allowed to run scripts on the page.
If you still experience send test traffic facebook pixel not working issues after checking your extensions, your website policy might be the culprit. If your website has a strict policy and Facebook is not on the allowed list, your browser will refuse to load the tracking code. The send test traffic button will open the page, but the script will never execute.
Open your Chrome developer tools and click the Console tab. Refresh the page. Look for a red error message mentioning a Content Security Policy violation. The error will specifically state that the script from connect.facebook.net was blocked by the browser.
To fix this, you must edit the security headers on your server. You need to add the Facebook domains to your script-src and connect-src directives. This tells your server that Meta is a trusted data partner. Once the headers are updated, the browser will allow the script to fire. If you do not have server access, you must ask your hosting provider to update the headers for you.
How to run a clean test from scratch
To be absolutely certain your tracking works, you must test it in a sterile environment. Follow these exact steps to run a clean test.
First, open a completely new browser profile. Do not use your daily browser. Create a guest profile in Chrome with zero extensions installed. This ensures no hidden ad blockers interfere with the network requests.
Second, open Events Manager in one tab. Navigate to the Test Events tab for your pixel. Click the clear activity button to remove any old test data.
Third, open your website in a second tab within the same guest profile. Do not use the send test traffic button in Events Manager. Just type your URL into the address bar and press enter.
Fourth, click around your website. View a product. Add an item to your cart. Fill out a lead form. Perform the exact actions you want to track.
Fifth, look at the Events Manager tab. You should see the events appearing in real time. The list will show the event name, the time it was received, and the parameters attached to it.
If the events appear here, your setup is perfect. The send test traffic button is just a shortcut to open your website. If typing the URL manually works, you do not need to worry about the button.
If you have followed every step and the dashboard remains empty, your tracking architecture is fundamentally broken. You might have conflicting scripts, a corrupted tag manager container, or server rules blocking the outgoing requests. At this stage, you need professional help to rebuild the system. You can review our pricing to see how we structure tracking audits, or reach out through our contact page to speak with a systems engineer.