<\/p>\n <\/a><\/p>\n<\/div>\n The Facebook Pixel<\/strong> custom tag template<\/a> is an unofficial<\/strong> tag template for Google Tag Manager\u2019s<\/a> community template gallery<\/a>.<\/p>\n <\/p>\n <\/a><\/p>\n<\/div>\n This template implements the Facebook Pixel<\/a> on the website. You can use it to load the SDK, initiate the pixel(s), and to send custom and standard events to Facebook with any custom properties and user attributes you wish. The template should be equipped to handle all the functionality of the pixel. Please let me know in the comments if there are features that you think are missing!<\/p>\n Here are the features of the pixel, together with some detail on how they work.<\/p>\n In general, when the tag fires, it goes through all the Pixel IDs added to the tag. For each one, it first checks if the pixel has been initialized for the ID. If it hasn\u2019t, it proceeds to initialize it (along with any parameters that can be set with the initialization call). Then, the tag proceeds to do whatever you\u2019ve configured it to do. It will send an event with any properties you have configured, and you can also use the tag to disable things like automatic history event tracking.<\/p>\n NOTE!<\/strong> The pixel DOES NOT<\/strong> automatically send the The first field requires you to add your Facebook Pixel ID. You can add more than one ID by separating each with a comma<\/strong>, e.g. If you add more than one ID, then the tag will initialize (if necessary) and send the hit to all the pixel IDs listed in the field.<\/p>\n If you check this button, then the tag will look in If the Event Name<\/strong> is mapped like this:<\/p>\n An An An An Object Properties<\/strong> are mapped like this:<\/p>\n A Here\u2019s an example of how an Enhanced Ecommerce object gets mapped into Facebook object properties:<\/p>\n NOTE!<\/strong> You can use the Object Properties settings (see below) to override these individual properties, if you are unhappy with how some parts of the automatic integration work.<\/p>\n<\/blockquote>\n If you haven\u2019t selected the Enhanced Ecommerce integration, you can choose an event name from the list of standard<\/a> events. You can also specify a custom<\/strong> event name, or you can use a Google Tag Manager variable<\/strong> to provide the event name dynamically.<\/p>\n If this field gets the value If you check this box, then a new group called Customer Information Data Parameters<\/strong> appears.<\/p>\n You can add supported data processing options<\/a> to this field. They are evaluated on a tag-by-tag basis, and are set for all pixel IDs of any given tag.<\/p>\n You can use this to set pre-defined parameters<\/a> for Facebook\u2019s Advanced Matching feature.<\/p>\n You have three<\/em> options for adding object properties to the hit.<\/p>\n If you checked the Enhanced Ecommerce<\/strong> integration, some properties<\/a> will be automatically populated.<\/p>\n You can also load a properties object using a Google Tag Manager variable<\/strong> that returns an object with key-value pairs that will then be added to the hit.<\/p>\n Finally, you can add properties manually using the table in the tag. Each row represents one property.<\/p>\n You can add pre-defined properties and custom properties. Read this<\/a> for more information.<\/p>\n NOTE!<\/strong> If you define properties using multiple sources (e.g. Enhanced Ecommerce integration AND variable AND the table), then conflicts are resolved in the order of table<\/strong> > variable<\/strong> > Enhanced Ecommerce<\/strong>. In other words, if you set You can check the Disable Automatic Configuration<\/strong> to prevent the pixel from automatically listening to clicks or collecting page metadata<\/a>.<\/p>\n You can check the Disable History Event Tracking<\/strong> to prevent the pixel from automatically tracking You can add an Event ID<\/strong> to deduplicate hits sent from the website and via server-side tracking<\/a>.<\/p>\n The Facebook Pixel custom tag template is an unofficial tag template for Google Tag Manager\u2019s community template gallery. Description This template implements the Facebook Pixel on the website. You can use it to load the SDK, initiate the pixel(s), and to send custom and standard events to Facebook with any custom properties and user attributes […]<\/p>\n","protected":false},"author":1,"featured_media":78040,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12033],"tags":[834,15100,24001,1791,4196],"dealstore":[],"offerexpiration":[],"class_list":["post-78039","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analytics","tag-custom","tag-facebook","tag-pixel","tag-tag","tag-template"],"yoast_head":"\n![\"Facebook](\"https:\/\/www.simoahava.com\/images\/2020\/04\/facebook-pixel.jpg\"){kind=tracking}
<\/p>\n<\/p>\nDescription<\/h3>\n
Instructions<\/h3>\n
\n
PageView<\/code> tracking hit similar to how the Facebook Pixel snippet does. You will need to create a PageView<\/code> tag to send the page view to Facebook.<\/p>\n<\/blockquote>\nFacebook Pixel ID(s)<\/h4>\n
123456789,234567890<\/code>.<\/p>\nEnhanced Ecommerce dataLayer integration<\/h4>\n
dataLayer<\/code> for the most recent<\/strong> object with the ecommerce<\/code> key. If this object has one of the following properties: detail<\/code>, add<\/code>, checkout<\/code>, or purchase<\/code>, the tag will automatically derive the following information from the object to be sent with the tag.<\/p>\n\n
dataLayer<\/code> does not have an ecommerce<\/code> object, or if the ecommerce<\/code> object doesn\u2019t have one of detail<\/code>, add<\/code>, checkout<\/code>, purchase<\/code>, or if the ecommerce<\/code> object doesn\u2019t have a products<\/code> array, the tag will end with a failure.<\/p>\n<\/blockquote>\n\n
ecommerce.detail<\/code> object sets event name as ViewContent<\/code>.<\/p>\n<\/li>\necommerce.add<\/code> object sets event name as AddToCart<\/code>.<\/p>\n<\/li>\necommerce.checkout<\/code> object sets event name as InitiateCheckout<\/code>.<\/p>\n<\/li>\necommerce.purchase<\/code> object sets event name as Purchase<\/code>.<\/p>\n<\/li>\n<\/ul>\n\n
contents<\/code> parameter is created from the products<\/code> array, and it is populated with the id<\/code> and quantity<\/code> of each product in the latter.<\/p>\n<\/li>\ncontent_type<\/code> is set to product<\/code>.<\/p>\n<\/li>\ncurrency<\/code> is derived from ecommerce.currencyCode<\/code>, or set to USD<\/code> by default.<\/p>\n<\/li>\nnum_items<\/code> is used in InitiateCheckout<\/code> and Purchase<\/code> and is aggregated from the total quantity of all products in the products<\/code> array.<\/p>\n<\/li>\nvalue<\/code> is calculated by multiplying the price<\/code> and quantity<\/code> of each product in the products<\/code> array, and summing everything up.<\/p>\n<\/li>\n<\/ul>\n{\n ecommerce: {\n currencyCode: 'EUR'<\/span>,\n checkout: {\n actionField: {\n step: 1<\/span>\n },\n products: [{\n id: 'firstProduct'<\/span>,\n name: 'firstProductName'<\/span>,\n price: '3.15'<\/span>,\n quantity: 2<\/span>,\n category: 'prods'<\/span>\n },{\n id: 'secondProduct'<\/span>,\n name: 'secondProductName'<\/span>,\n price: '7.35'<\/span>,\n quantity: 3<\/span>,\n category: 'prods'<\/span>\n }]\n }\n }\n}\n\n\/\/ BECOMES\n<\/span>\n{\n content_type: 'product'<\/span>,\n currency: 'EUR'<\/span>,\n num_items: 5<\/span>,\n contents: [{\"id\"<\/span>:\"firstProduct\"<\/span>,\"quantity\"<\/span>:2<\/span>},{\"id\"<\/span>:\"secondProduct\"<\/span>,\"quantity\"<\/span>:3<\/span>}],\n value: 28.35<\/span>\n}\n<\/code><\/pre>\n<\/div>\n\n
Event Name<\/h4>\n
Consent Granted (GDPR)<\/h4>\n
false<\/code> (most commonly through a Google Tag Manager variable), the pixel will download the SDK, but it will not initialize nor send any hits to Facebook.<\/p>\nEnable Advanced Matching<\/h4>\n
Data Processing Options<\/h4>\n
Customer Information Data Parameters<\/h4>\n
Object Properties<\/h4>\n
\n
content_type<\/code> in the table, it will override content_type<\/code> set in a variable or the Enhanced Ecommerce integration.<\/p>\n<\/blockquote>\nMore Settings<\/h4>\n
pushState<\/code> and replaceState<\/code> history events.<\/p>\nRelease notes<\/h3>\n
\n\n
\n \nDate<\/th>\n Changeset<\/th>\n<\/tr>\n<\/thead>\n \n 11 November 2020<\/td>\n Added Event ID\tto pixel fields\tfor server-side\tdeduplication.<\/td>\n<\/tr>\n \n 23 July 2020<\/td>\n Fix to prevent template save if Advanced Matching list enabled but empty.<\/td>\n<\/tr>\n \n 6 July 2020<\/td>\n Remove deprecated User Properties<\/strong>. Add Data Processing Options. Fix bug with empty Advanced Matching List.<\/td>\n<\/tr>\n \n 23 April 2020<\/td>\n Add unit tests. Add Enhanced Ecommerce integration.<\/td>\n<\/tr>\n \n 16 April 2020<\/td>\n Add option to disable automatic tracking of history events.<\/td>\n<\/tr>\n \n 1 April 2020<\/td>\n Fix \u201ccountry\u201d in Advanced Matching to use correct key.<\/td>\n<\/tr>\n \n 19 October 2019<\/td>\n Fix object property bug.<\/td>\n<\/tr>\n \n 17 October 2019<\/td>\n Fix object merging. Update event name selection to allow using a variable.<\/td>\n<\/tr>\n \n 12 September 2019<\/td>\n Initial release.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n\n","protected":false},"excerpt":{"rendered":"