Facebook Tracking Pixel Drupal Module

This module is meant to manage Facebook tracking pixels on your site. This module is similar to other modules that allow you to put code into a page. The difference is this module caters to the advanced marketing capabilities that are possible with Facebook's new advertising tools and the ability to track multiple pixels for your marketing needs.


This module was created to fill a need to support pushing Drupal as an advanced sales marketing platform. While there are sites that use Drupal to accomplish their marketing needs, there has never been a lot of sharing of the technology created to make Drupal do this. We intend to change that with this module and several others that we maintain or co-maintain.


Work for this module was a team effort between a developer/eCommerce operator and a marketing professional (Sil Kogelman). This module has been developed with input from advertising agencies and Facebook Advertising support staff. We only implement best practices based on input from Facebook Advertising support on what can and cannot be done for tracking. Great work has been put into making this an powerful module for implementing Facebook advertising for Drupal.

This module undergoes continuous testing using Travis-CI. View the status.


This module allows for tracking of multiple base Facebook Pixel IDs and the ability to track events tied to those base IDs on any location throughout the entire site by using paths.

Performance and flexibility are the top priorities for this module. The unique nature of the Facebook Tracking Pixels required a module be developed to support the richness of the Pixel tracking offered. This module was heavily influenced by how the Code Per Node module handles CSS and JS on an ad-hoc basis. By writing the codes to the file system, Drupal core aggregation or AdvAgg module (supported by this module) can be used to compress and aggregate the JS code. Since the code is in a file, this increases the ability for browsers and CDNs to cache the pixel tracking codes as well. Flexibility was also needed to track events across the entire Drupal installation no matter what the content type or page - the ability to track based on a path.

Code Browsing

Want to take a look a the code of this module? We replicate the Drupal.org Git repository to Github that has a little nicer tools for browsing code.

Also located on Bitbucket as well.

Supporting organizations: 

Project information