Pixel Helper

If you are new to the pixel, or are having trouble tracking conversions, use our pixel helper chrome extension to help you with debugging.

Migrating Pixels

We deprecated the Custom Audience and Conversion Tracking pixels in February, 2017. They have been combined into a new, single Facebook pixel. If you are using the old pixels, you should migrate to the new pixel.


What data does the Facebook pixel collect?

See our Cookie Policy for details about the cookies used and the data received. The Facebook pixel receives these types of data:

  • Http Headers – Anything present in HTTP headers. HTTP Headers are a standard web protocol sent between any browser request and any server on the internet. HTTP Headers include IP addresses, information about the web browser, page location, document, referrer and person using the website.
  • Pixel-specific Data – Includes Pixel ID and the Facebook Cookie.
  • Button Click Data – Includes any buttons clicked by site visitors, the labels of those buttons and any pages visited as a result of the button clicks.
  • Optional Values – Developers and marketers can optionally choose to send additional information about the visit through Custom Data events. Example custom data events are conversion value, page type and more.
  • Form Field Names – Includes website field names like email, address, quantity, etc., for when you purchase a product or service. We don't capture field values unless you include them as part of Advanced Matching or optional values.

Does the Facebook pixel impact website performance?

The Facebook pixel is loaded asynchronously and does not block the display of the web page. Because all advertisers use the same pixel script, the pixel code will be already be in the browser’s cache If a user has visited any website with the pixel installed.

Need more information?

Learn more about GDPR: