Facebook Pixel Helper
The Facebook Pixel Helper is a tool that helps you validate your Facebook Pixel. Using the tool you can:Download Now
Using the Facebook Pixel Helper
The Pixel Helper works in the background to automatically review the websites for code that looks like the Facebook Pixel. When a website has a Facebook Pixel installed the
If the icon does not turn blue then there are no Facebook pixels installed on this page.
Install Pixel Helper
To use the Facebook Pixel Helper first make sure you have the Chrome web browser installed on your computer. Next, using the Chrome browser install the Pixel Helper from the Chrome Store. Follow the instructions on the Chrome store to install the extension in your browser. Once the Pixel Helper is installed a small icon
</> will appear next to your address bar.
Verifying Pixel Implementation
First, install the Facebook Pixel Helper Chrome Extension. After installation, navigate to your website in your Chrome browser, and click on the Pixel Helper icon.
The popup will tell what pixels were found on the page, and whether they have loaded successfully. If your pixel(s) loaded succesfully, it's time to start running ads with them.
Troubleshooting Pixel Errors
The Facebook Pixel Helper reports common errors. These states are indications that your webmaster needs to fix something in order to use the Facebook pixel product properly.
Pixel Did Not Load
This error means that the Pixel Helper found what looks to be Facebook pixel code on your site, but the actual HTTP call was never made.
This could typically due to an error in the code, but could also occur if the pixel fires on a dynamic event (e.g. on a button click).
In that case, the error will disappear upon clicking on the button.
This error means that the Pixel Helper found what looks to be double-encoded characters.
This could typically due to a tag or CSM system encoding already encoded information. For example, encoding
&amp;. Please confirm that characters are not being encoded twice, for example, try changing
Not a Standard Event
This warning means that the Pixel Helper found an event that is not one of the Standard Events.
For example, the event is named
Purchased instead of
Purchase. Please use one of the standard events. For more information on planning event names, please see Planning Website Custom Audiences.
Pixel Activated Multiple Times
This error means that a pixel with the same ID and event name was sent multiple times to Facebook.
This is typically an error. The same event should only occur once upon page loading.
If it is sent with different custom data parameters, those parameters should be aggregated into a single pixel event.
Invalid Pixel ID
This error means that the sent ID for the pixel did not match a known pixel ID in our system.
The following documentation will show you how to find the correct ID for either your Custom Audience or Conversion Pixel
Can not find Product Catalog
The Product Catalog ID which was passed in the field
product_catalog_id in the pixel fire could not be found on our system.
You can find your Product Catalog ID in Business Manager under Settings > Product Catalogs.
Alternatively to associate a Product Catalog to a pixel follow the steps below.
The Facebook Pixel Helper also reports suggestions. These states are indications that the pixel is working but something could be changed to improve performance.
You Have Opted Out of Tracking
This warning highlights that you have opted out of tracking from Facebook and the pixel fires detected were not logged on our servers.
This prevents any server side validation for the Custom Audience Pixel potentially leaving pixel problems undiagnosed.
You can learn more about our offsite tracking in your Facebook setting including how to turn tracking back on.
Facebook respects mobile device settings regarding advert tracking so you may need to update your devices settings to opt back in. If one or more device has opted out each device will have to opt back in before tracking is enabled.
Pixel is not paired with a product catalog
This warning suggests that the pixel is not paired with any product catalog. It is required to specify relationship between pixels and product catalogs.
There are two ways to pair a catalog with a pixel:
Follow these steps to pair a catalog with a pixel using the Business Manager:
Product Catalog Preferences API
You can use the Product Catalog Preferences API pair a catalog with a pixel.
Pixel Took Too Long to Load
This warning suggests that it took a long amount of time before the pixel was activated. This may be due to where the pixel is located on the page.
If a web page visitor closes the page, clicks on a link, or navigates away before the pixel event activates, the action will not be tracked. A significant percentage of actions and conversions can be lost due to this.
It is recommended to place the pixel code early in the web page, preferably just before the closing
</head> tag in the HTML.
Pixel is not the only conversion
It is not a best practice to load multiple conversion events on a single page. This will result in inefficient optimization and tracking of these conversion events.
Instead, using a single conversion pixel across all ads tracking or optimizing for this event.
In the case that a secondary conversion event occurs based on person's interaction with the web page (e.g. upon a button click), then this warning can be ignored.
Uninstall the Facebook Pixel Helper
To uninstall the Facebook Pixel Helper type
chrome://extensions/ into the address bar of your Chrome web browser and click the trash icon next to the Facebook Pixel Helper extension.