![]() NOTE! 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. Here’s an example of how an Enhanced Ecommerce object gets mapped into Facebook object properties:Ĭontents: , Value is calculated by multiplying the price and quantity of each product in the products array, and summing everything up. Num_items is used in InitiateCheckout and Purchase and is aggregated from the total quantity of all products in the products array. If the dataLayer does not have an ecommerce object, or if the ecommerce object doesn’t have one of detail, add, checkout, purchase, or if the ecommerce object doesn’t have a products array, the tag will end with a failure.Īn tail object sets event name as ViewContent.Īn ecommerce.add object sets event name as AddToCart.Īn ecommerce.checkout object sets event name as InitiateCheckout.Īn ecommerce.purchase object sets event name as Purchase.Ī contents parameter is created from the products array, and it is populated with the id and quantity of each product in the latter.Ĭurrency is derived from ecommerce.currenc圜ode, or set to USD by default. If this object has one of the following properties: detail, add, checkout, or purchase, the tag will automatically derive the following information from the object to be sent with the tag. ![]() If you check this button, then the tag will look in dataLayer for the most recent object with the ecommerce key. 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. You can add more than one ID by separating each with a comma, e.g. ![]() The first field requires you to add your Facebook Pixel ID. You will need to create a PageView tag to send the page view to Facebook. NOTE! The pixel DOES NOT automatically send the PageView tracking hit similar to how the Facebook Pixel snippet does. 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. Then, the tag proceeds to do whatever you’ve configured it to do. If it hasn’t, it proceeds to initialize it (along with any parameters that can be set with the initialization call). For each one, it first checks if the pixel has been initialized for the ID. In general, when the tag fires, it goes through all the Pixel IDs added to the tag. Here are the features of the pixel, together with some detail on how they work. Please let me know in the comments if there are features that you think are missing! Instructions The template should be equipped to handle all the functionality of the pixel. 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. This template implements the Facebook Pixel on the website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |