In this article, we will try to explain the concept of a Consent Solution, within our platform and how it should set up.
A Consent Solution should be viewed as a container, which can hold domains, templates (predefined pop-up designs), and languages.
You have 3 different types of domains for a Consent Solution, which are the following:
- Public Domain
This type is the domain that gets scanned. You should set your URL production-site as a Public Domain
- Internal Test Domain
This type does not get scanned and will there not display any cookies in any of the templates but will otherwise function as the rest of the solution. You should use this type for testing purposes. The URL's for this type could be something like dev.yourdomain.com, or staging.youdomain.com.
Note: The URL will not be shown in the policy, along with the other domains.
- Public Test Site
This type can show all templates but is not scanned, but will instead show scan results from a public domain.
Note: It will be shown alongside public domains in the policy.
When you create a new Consent Solution it will be assigned 3 templates, one for each widget (These can be changed and modified later).
These templates have a 1:1 correlation with this Consent Solution, therefore changes made to any of the templates will only affect that Consent Solution and show up on each of the domains within it.
- Pop-up Template
This template is for the consent pop-up and depending on which template you choose can have different functionality and show more or fewer data. This is implemented via the pop-up script. Learn more here
- Policy Template
This template is for the cookie-policy which shows the scan data and policy-text. This is implemented via the policy script. Learn more here
- Privacy Controls
This template is for the Privacy Controls, in which the user has the option of changing their consent, by opt-in or opt-out toggles. This is meant to be placed on a separate page, mostly underneath or above the cookie-policy. It's only required to do so if you don't use a pop-up template that has this feature within it. This is implemented by placing a <div> element onto the webpage. Learn more here
When you first set up the Consent Solution, you add in a domain and then lastly choose which languages you want to use for the Consent Solution. You can add more languages later.
If you have a multilingual website, you would want to add the same language to the Consent Solution that is used on the website. You DO NOT need to add every domain path of your languages in the domain list, like yourdomain.com/de/. You only need to add the base-domain, like youdomain.com.
Which language is displayed is controlled via a data-culture attribute on the scripts.
On each script for the solution, you have the option of choosing, which language to pull from the Consent Solution, by defining the correct language-code. Learn more about choosing languages.
In the tab LANGUAGES & SETTING, you have further options of changing the name of the Consent Solution itself, adding more languages, Enabling Shared Consent, and Push for new consents.