1. Deploying the widget on your site
Once your cookie widget is finalized, go to the "Integrate on your site" section:
You will find in this section the script to integrate Axeptio on your site.
<script>window.axeptioSettings = { clientId: "XXXXXXXXXXXXXXX", cookiesVersion: "myCookiesVersion", googleConsentMode: { default: { analytics_storage: "denied", ad_storage: "denied", ad_user_data: "denied", ad_personalization: "denied", wait_for_update: 500 } }}; (function(d, s) { var t = d.getElementsByTagName(s)[0], e = d.createElement(s); e.async = true; e.src = "//static.axept.io/tcf/sdk.js"; e.type = "module"; t.parentNode.insertBefore(e, t);})(document, "script");</script>
For Axeptio to have control over your other services, it is recommended to load this script as early as possible on your site, for example at the top of your <head> tag.
Once the script is integrated into your site, don't forget to publish your Axeptio project if you haven't already done so to put your widget online on our servers.
The cookie widget should now appear on your site.
2. Conditioning your third-party services to consent
Now that Axeptio is properly present on your site, let's see how to submit your different third-party services to consent.
For IAB vendors
IAB vendors, i.e. services that are compatible with the IAB TCF protocol, automatically read the consent via the tcString. For all these services, you will have nothing more to do. You can find the complete list of IAB vendors here:
If you encounter integration problems of Axeptio with an IAB vendor, check that Axeptio is properly loaded and that the TCF protocol is properly initialized, before loading the vendor.
For other services
Services that are not compatible with the IAB TCF protocol must be managed manually, so that they are not loaded until the user has given consent.
If you load these services via Google Tag Manager
When consent is updated, Axeptio sends Google Tag Manager an "axeptio_update" event, as well as an "axeptio_authorized_vendors" variable. This variable contains the list of accepted non-IAB services, under their technical name (for example facebook_pixel). IAB vendors are never included. To find the technical name of a service, see Get the technical names of your services.
You can use this event and this variable to condition your GTM tags, so that they are triggered only if the service they are attached to has been accepted.
For example, I have a Facebook Pixel initialization tag, currently triggered as soon as the page loads ("All pages").
Instead of this trigger, create a trigger of type "Custom Event" with the following settings:
Event name:
axeptio_updateConditions: select "Some custom events", then
axeptio_authorized_vendorscontainsfacebook_pixel(the technical name of the service)
On first visit, axeptio_update is only sent after the visitor's choice: the tag will not trigger before.
đ Articles written for the Axeptio Brands SDK use axeptio_activate_<service> events. The TCF SDK does not send these events: use only axeptio_update with the condition above.
To create the "axeptio_authorized_vendors" variable, go to the "Variables" section of your GTM, then create a new one. In the variable type, select the banner at the top "Discover more variable types in the community template gallery" and search for the "Axeptio Consent State" template:
In the template settings, choose the "Authorized vendors" signal. The "Google Consent Mode state" signal returns no value with the TCF SDK.
All that's left is to name your variable:
If you load these services directly
Follow this documentation: