Implementing the Full Barion Pixel: Difference between revisions

From Barion Documentation
Jump to navigation Jump to search
(Created page with "__NOTOC__ {{PageTitle|title= Implementing the Full Barion Pixel}} = Prerequisites = Implementing the Full Barion Pixel first and foremost requires an implementation of the Ba...")
(No difference)

Revision as of 10:59, 6 February 2020

Implementing the Full Barion Pixel

Prerequisites

Implementing the Full Barion Pixel first and foremost requires an implementation of the Base Barion Pixel on your webshop. It is not necessary that the Base implementation be accepted by Barion however before the start of the implementation, just be aware that only approved events will be sent towards Barion. As the Full Barion Pixel, with the Consent Management implementation in particular, requires that you send user data for marketing purposes towards us, it requires a separate agreement and approval from Barion.

Where to start?

The preferred starting point for implementing the Full Barion Pixel is the Content View event, for cases where the content type is 'Product' in particular. This event is a very often used one, since it should be implemented in every product page at least. This event is also easy to implement, since it should be triggered every page load.

The first step is to create a JS object that contains the event parameters, as detailed in the API reference. See below for an example.