Skip to main content
Skip table of contents

Axeptio

About Axeptio

Axeptio is a French consent management platform, GDPR and ePrivacy compliant. The tool relies on simple integration with no technical prerequisites, as well as a pleasant user experience that respects users. Axeptio strives to establish a bond of trust between the platform and its users so that consent is given in full awareness. The solution is installed on over 33,000 sites and applications, and reaches nearly 33 million users every day.

To learn more, visit: https://www.axept.io/  

PA Connect Axeptio

The Axeptio connector allows you to manage the visitor consent through the audience measurement cookies thanks to our “Consent Management” tagging methods, but also to automatically tag your visitors' interactions with your consent management platform. This provides you with numerous indicators for analyzing consent, such as:

  • Number of times the CMP is displayed

  • Response rate

  • Consent rate

  • etc

Important

Marking interactions on your CMP is based on the declaration of two custom events (see below). Collecting these events is optional (the option must be checked via the Axeptio CMP). If you accept and declare these events in your Piano Analytics Data Model, they will be invoiced like standard events.

Connector principles

This document aims at guiding you through the activation of the Hybrid measure using PA Connect Axeptio. Hybrid measure combines the best of both worlds by allowing you to combine CNIL exemption with consent (opt-in).

CMP (1).png

Prerequisites

  • Your site must be tagged with the Piano Analytics SDK

  • You must have access to Axeptio and Piano Analytics

The Axeptio connector calls on events and properties that are not included in the default Piano Analytics data model. It is then necessary to configure these elements so that they are taken into account.

Privacy

If you benefit from the ePrivacy exemption, it is necessary to authorize the collection of these elements prior to the collection of consent: you must include them in the list of authorized elements for your default consent mode.

More information here : https://developers.atinternet-solutions.com/piano-analytics/data-collection/how-to-send-events/consent  

Installation guide

Setting up the integration on Axeptio

Once in your project, click on the parameters, then Analytics Connectors:

mceclip0.png

In the pop-up window that opens, you can choose to activate the two options managed by this connector:

  1. Check to activate the service. The consent.display and consent.answer events will be sent (see “Customizing the Piano Analytics data model” below).

  2. Check the privacy mode to manage the Consent of your visitors. The consent mode will be updated if the visitor validates the Piano Analytics vendor in the Axeptio widget.

mceclip1.png

Publish your widget with Piano Analytics enabled.

Once these steps have been completed, Piano Analytics will start collecting data from your visitors' interactions with the Axeptio consent form.

Customizing the Piano Analytics data model

The PA Connect Axeptio requires the declaration of two events in the Piano Analytics data model:

  • consent.display (On site) - Event corresponding to the display of the consent management platform (CMP)

  • consent.answer (On site) - Event corresponding to an explicit response from the user (click on a CMP button, CMP exit click, save preferences, etc.)

And two properties attached to the consent.answer event:

  • privacy_consent_value (string) - Property indicating the value of the consent expressed: 'full', 'partial' or 'refusal'.

  • privacy_consent_type (boolean) - Property indicating the type (binary) of consent expressed: true in the case of total or partial consent, or false in the case of refusal

Events can be declared from the interface Data Management > Data Model > Events. More information here.

Properties can be declared from the interface Data Management > Data Model > Properties. More information here.

Configuring some performance indicators

To analyze the events collected by the connector, it can be useful to set up customized segments, metrics and reports. Here are a few examples:

  • Number of times the CMP is displayed

To get this indicator, start by creating a segment to include only the consent.display events: 

Next, create a custom metric to display the total number of events, to which we apply the previously created segment in integer format:

  • Response rate:

The response rate is the ratio between the number of times the consent platform is displayed and the number of responses obtained.

To get this indicator, start by creating a segment to include only consent.answer events, corresponding to the number of responses obtained:

Next, create a custom metric to calculate the ratio between the number of responses and the number of displays, using the segments created previously:

  • Consent rate

The consent rate is the ratio between the number of consents obtained and the number of modal displays.

To get this indicator, start by creating a segment to include only consent.answer events with the privacy_consent_type=true property, corresponding to obtained consent:

Next, create a custom metric to calculate the ratio between the number of consents and the number of displays:

By applying this methodology, it is possible to obtain numerous indicators enabling in-depth analyses of user consent:

  • Number of responses

  • Number of consents

  • Number of non-consents

  • Rate of consent among respondents

  • Non-response rate

  • Rate of non-consent

  • Number of visits with consent

  • Number of consenting visitors

  • Rate of visits with consent

  • Rate of consenting visitors

  • Etc

Here is an overview of the results:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.