This tab is dedicated to the consent notice configuration in GDPR mode.
With this section, you have the opportunity to enable an paying alternative to data sharing to your end-user.
For more details on the feature and how to configure it, refer to Getting started with Fair Choice.
By default, the stack selection will be:
- Stack 1: Precise geolocation data, and identification through device scanning
- Stack 9: Personalised ads, ad measurement, and audience insights
- Stack 14: Personalised content and content measurement
With this option you can choose which standard stack you want to use in your consent notice.
You will only be able to select a given stack if it does not contain any purpose that is already part of a selected stack.
For a definition of the stack please refer to the TCF objects page.
Consent for your own data processing
If you also collect and process your users’ data, you can add yourself to the Partners’ list in the Consent Notice.
Depending on the Version of the TCF you have different options available
With this option, you are able to declare your own data collection and choose:
- The Purposes of your data collection with their legal basis.
- Possible legal basis: Consent or Legitimate interest
- NB: Purpose 1 (Store and/or access information on a device) is the only purpose that can only be declared under Consent legal basis as per the IAB TCF.
- The Special Purposes of your data collection (if necessary)
- Possible legal basis: Legitimate interest only
- The Special Features that are necessary for your data collection for one or more purposes declared
- Possible legal basis: Consent only
- The Features that are part of your data processing
- No legal basis on Features
With this option you are able to select the purposes you want to ask consent for.
The consent notice allows the user to :
- Pay (Fair Choice feature)
- Accept fully or partially
Depending on his answer, the consent notice displays a specific message giving confirmation of his choice.
These confirmation pages can be disabled, completely or partially, to reduce the action needed to close the consent notice.
For reference, the confirmation pages are as follow.
Paying Users confirmation page
Consented Users confirmation page
The confirmation page for consented users also contains a section allowing the user to receive an email with a link to revoke his consent.
This section can be hidden by ticking off the dedicated check box in the Confirmation Pages section.
Refusal Users confirmation page
You can decide to display the Consent Notice to your users again in two cases:
- to those who refused to give their consent (full refusal),
- to those that accepted a previous version of the vendor list (either an update was done on the IAB list or new vendor(s) added Ogury side).
Reminders frequency on refusal
This parameter gives the opportunity to user who refused to see the consent notice and change their mind.
Depending on the value chosen for the Reminder property, the consent notice will be re-displayed when the app is opened again and the “reminder” value is reached ( e.g. the next day or after a week, etc).
Consent Update on updated list
This second parameter is grouping all the updates occurring during the period selected to display the non-consented vendors (either because they were not part of the list when the user first gave his consent or because the user refused this particular vendor). In this case, an incremental Consent Notice will be displayed to the user.
When the DCO feature is used, the Reminder might be “overwritten”, meaning that the algorithm calculates when is the optimal time to re-display the Consent Notice in order to have a better acceptance rate.