Getting started with the Barion Pixel
Getting started with the Barion Pixel
The Barion Pixel is JavaScript code that allows us to help you to track visitor activity on your website. It works by loading a JavaScript function which you can use whenever a site visitor takes an action that you want to track (these actions are referred to as an 'event'). Implementing the Barion Pixel and sending usage data towards Barion in a way that conforms to our recommendations is fully compliant with the GDPR.
Your webshop and Barion as its payment processor has a legitimate interest in collecting data to help prevent fraudulent payments, and it is beneficial to both your webshop and Barion. As such, implementing at least the Base Barion Pixel is required in order to use the Barion Smart Gateway. Barion also uses the more expansive data collected by the Full Barion Pixel for these purposes if your webshop implements it, but without express user consent and an agreement between Barion and your webshop, none of the user data or Personally Identifiable Information is used for marketing purposes.
Your webshop can receive more favourable terms for the Barion Smart Gateway if a complete implementation for the Full Barion Pixel is provided alongside with user consent collected according to our consent management requirements. This allows us to collect and use data for marketing purposes and enables us to provide the other marketing related services of the Barion Marketing Cloud (coming soon). Receiving these benefits is contingent on an approved implementation of the following:
- the Full Barion Pixel on top of
- the Base Barion Pixel implementation with
- a compliant Consent Management system.
The Base Barion Pixel
The Base Barion Pixel is a partial implementation of the Barion Pixel that serves two purposes. First, it links and initializes the code required by the Barion Pixel as a whole. This means that any Barion Pixel implementation needs the Base Barion Pixel functioning to send data towards Barion. Fortunately, the Base Barion Pixel is trivial to implement, as it is a single snippet of code. Furthermore, if you have a webshop from one of our partners that supports that, you can implement the Barion Pixel with a single click, as with UNAS and Shoprenter. Otherwise, the Base Barion Pixel consists only of a single JS snippet that you must paste into your HTML on each page of your webshop, editing your Barion Pixel ID into it.
As mentioned above, the Base Barion Pixel in itself does not enable us to give you better terms for the Barion Smart Gateway, and it only provides rudimentary data about your user activity which in turn affects the quality and quantity of services that we can provide to you. It only sends 'init' events that show us the fact that a user has visited a certain page, but we receive no details on the actual activity on the page, or data about the nature of the page itself. However, implementing the Base Barion Pixel serves as a requirement for proceeding to implement the Full Barion Pixel, and is also a requirement to use the Barion Smart Gateway.
The Full Barion Pixel
Implementing the Full Barion Pixel is dependent on a working Base Barion Pixel implementation, and requires including details from the nature of user activity from an e-commerce perspective, such as viewed product and user cart activity details. The Full Barion Pixel hovewer provides us with detailed user data, with which we can give you better fraud prevention, and if paired with a compliant Consent Management solution, other marketing related benefits such as better terms for the Barion Smart Gateway and services from the Barion Marketing Cloud (coming soon). The better your implementation follows the logic of your webshop and the provided documentation, the better services we can provide for you.
The Full Barion Pixel implementation consists of various 'events', actions that your visitors take that are recorded and sent towards Barion. These events are either triggered by a page load, such as those detailing the contents of the viewed page, or they can be triggered by a mouse click, such as those showing us the actions, such as searches or cart interactions, that the user took. As a rule of thumb, a full implementation consists of the implementation of all events at all applicable places, so that only events that refer to actions that cannot be taken in your webshop can be omitted, for example if your webshop has no search feature.
Where to start?
In order to implement the Pixel, you will need your Barion Pixel ID and either:
- full access to your website's codebase (Implementing the Base Barion Pixel is your next step) or
- a webshop implementing the Google Tag Manager (Implementing the Barion Pixel in the Google Tag Manager is your next step) or
- an UNAS webshop (Implementing the Barion Pixel in UNAS webshops is your next step) or
- a Shoprenter webshop (Implementing the Barion Pixel in Shoprenter webshops is your next step)
- a Woocommerce webshop ( Implementing the Barion Pixel in woocommerce webshops is your next step)
- a Viltor webshop ( Implementing the Barion Pixel in Viltor webshops is your next step)