The following are the consent options we offer. These configuration options determine the conditions and settings under which the website is requesting consent, e.g., who sees the consent popup, how broadly consent is applied, and how long consent should last. These options can be configured on the “Edit a Site” page inside the Choice Portal.
"Which users should be asked for consent" (Edit a Site)
Determines which users will be shown the CMP UI. Note that the frequency of prompting is set using the configuration option "Min Days Between UI Displays".
Note: Publishers established within the EEA and the UK are required to apply GDPR and ePrivacy Directive to any user (option "Everyone") regardless of the user's location.
"Consent Scope" (Edit a Site)
How consent given by a user applies to sites other than the current site. The value "global" includes all IAB framework sites—except those with a "service" level consent scope. The value "service" restricts consent choices only to the current site, and does not honor choices made on other sites.
|
Consent scope |
Consent (euconsent-v2) |
What does this scope mean? |
|
global |
Third-party cookie stored on IAB Europe central domain consensu.org |
Global consent means if a user sets consent preferences on another site using global consent, those preferences will apply to your site, and the user will only see the consent window again if there are new vendors to consent to. Consent set on your site will apply to other sites using global consent. |
|
service |
First-party cookie stored on publisher site domain |
Service consent means global consent will not apply to your site, and the user will be asked to set consent preferences for your site and vendors. Preferences set on your site will not apply to other sites with either global or service consent. |
|
global group |
Third-party cookie stored on IAB Europe central domain consensu.org |
Global group consent means if a user sets consent preferences on another site using global consent, those preferences will apply to all sites within your group of sites, and the user will only see the consent window again if there are new vendors to consent to. Consent set on your sites will apply to other sites using global consent. |
|
service group |
Third-party cookie stored on publisher group domain |
Service group consent means global consent will not apply to your group of sites, and the user will be asked to set consent preferences for your group of sites and vendors. Consent will apply to all sites within your group. Preferences set on your group of sites will not apply to other sites with either global or service consent. |
Note: Google will only accept Service consent scope.
"Consent Scope Group URL"
Note: using a group-level consent scope requires significant development on your part in order to implement a JSON API or a shared consent cookie destination that is accessible via iframe. Please see the Group Consent API section for more details.
This value is only needed if the consent scope is set to either "global group" or "service group". This is the Group Cookie Access API URL for group-level consent scope. If "Consent Scope Group URL" is not set, but a group-level consent scope is specified, the consent scope will fall back to either "global" (for "global group") or "service" (for "service group").
"Show New Vendors Every..." (Edit a Site)
Determines how frequently, in days, the CMP will check for additions or changes to the vendor list, and re-prompt users for consent if changes are found.
Note: Vendors who are added to the list before a user is re-prompted will not receive a consent signal until this value is exceeded.
If the Vendor is blocked manually in the Vendor list, the user will be be re-prompted immediately. Hence, we suggest to do the changes to the Vendors' list in bulk. Indeed, if you have made a manual change to your IAB or non-IAB vendor lists, this will cause the CMP to prompt the user to adapt their consent to the latest version of your vendor list.
"Your consent configuration" (Edit a site)
Purposes for which the site owner is requesting consent for herself or on behalf of its partners (vendors). The purposes will be displayed, either as purposes or as the proposed stacks that result based on the purposes selected. Choice provides one recommended stack out of the box that covers many use cases. But you can configure your own purposes and resulting stack using the “Customize Settings” workflow.
More information about the purposes and stacks can be found in the IAB Framework Policies.