🍪 In this article, we will focus exclusively on configuring the axeptio widget for publishers.
This is the headquarters where you can put your superpowers to work. Want custom texts? No problem! Prefer Consent Mode V2? We have it too! Need to juggle between versions and languages like a pro? You're in the right place! And of course, never underestimate the power of selecting your favorite vendors.
1-Text Configuration
You have the ability to modify the "overline", "title" and "subtitle" as you wish:
👷🏻 Axeptio provides you with a standard text, previously validated by the IAB Europe. If you still wish to modify this text, please contact your Customer Success Officer or write to help@axeptio.eu.
2- Consent Mode v2 Configuration
You have the ability to enable or disable the Consent Mode v2. Note that, since March 6, 2024, it is mandatory to continue using Google services (Google Ads, Google Analytics, Search Ads 360, Display & Video 360...)
Consent Mode v2 is enabled by default:
One more little effort to properly configure Consent Mode v2, we'll meet you right here for the technical integration part (Google Tag Manager, directly in the SDK, via our plugins)
3-Versions and Languages Configuration
Managing a site with subdomains? A site with multiple languages? Then you'll need to manage "configurations" and "cookie versions" within your project.
But don't worry, we'll explain everything to you right after!
At Axeptio, we love when everything is well organized - not like your teenage bedroom!
To help you find your way around easily, we give you the ability to choose a label. It's a bit like the name of your configuration. And since when you love something you don't count the cost, we also added the cookie version. You can use it for example to differentiate between prod and pre-prod versions, different languages...the cookie version is the limit as they say!
If you manage a multilingual site, and need a default translation of the TCF widget stay put, we have what you need.
You just need to select the desired "widget language" and choose from one of the 7 natively managed languages (🇫🇷🇮🇹🇪🇸🇵🇹🇩🇪🇬🇧🇳🇱). The content texts, buttons and titles will be translated.
4- Vendors Configuration
The time has now come (and not of cathedrals) to configure your TCF widget with your various vendors (or your cookies for the greedy ones 🍪).
To do this, we have provided you with a filter system to best accompany you.
You will be able to quickly distinguish between the different vendors:
- Google ATP: The most used
- IAB Vendors
- Axeptio vendors (custom vendors)
Already have a TCF CMP in place? Want to migrate easily?
Don't move, we're giving you a little hack to migrate your IAB vendors in less than three minutes.
To do this, we invite you to download a Chrome extension, which allows you to decrypt the tc_string. We use this one (but there are others!)
Then simply copy and paste your tc_string into our back-office:
🍪 So Jamy, if I want to add a custom vendor, how can I do it? For this, don't hesitate to write to your favorite Customer Success or send a sweet message to help@axeptio.eu
After selecting your various vendors, you can now select the stacks.
This step is not mandatory! Your TCF consent widget will work perfectly fine.
But what are stacks then? And vendors?
Vendors are entities that provide services related to advertising or user tracking on a website or application. They can be advertising networks, advertising technology providers, measurement companies, etc. Each vendor has a unique numeric identifier within the TCF framework, which allows you to track and manage their consent.
Stacks are sets of vendors grouped according to the services they provide or the purposes for which they use the data. They simplify consent management by offering users more general consent options. Rather than having to consent individually to each vendor, users can consent to the entire stack, which covers a specific set of services.
In summary, vendors are individual entities that provide advertising or tracking services, while stacks are groupings of vendors based on the services they provide, thus simplifying the consent management process for users. And there you have it!