- Getting started with Cookie Information
- What is a Consent Solution?
- What are Privacy Widgets?
- What is the Cookie Control SDK?
- What is the Compliance Dashboard?
Getting started with Cookie Information
Do you have an account but no user? Contact us at email@example.com
Do you not have an account? Start a free trial here
Log in to the platform here
First things first!
Create your first consent solution. The consent solution is the control center for the consent pop-up, the text in the consent pop-up, where you can categorize new cookies, and much more.
Enter the domain name (URL) for your solution, make sure the type is set to Public Domain, choose the number of URLs (how big your website is) our scanner should crawl, and lastly how frequent.
If you are not sure how many URLs your site consists of, you can get a good indication with a quick Google Search by typing: site:yourdomain.com in the search field.
Before adding the domain, please consider the following:
- Is the domain live?
- Is the domain accessible without IP-whitelisting?
- Is the domain redirecting to another domain?
- Do you need to have the domain scanned immediately?
Our scanner needs to be able to access the domain, in the same way as a regular visitor would.
After clicking NEXT, choose what languages you need for your solution.
If your website is multi-lingual, then first choose the default language in the first dropdown field and all of the remaining languages in the second field.
Once the Consent solution has been created (and if the domain type is "public domain") our scanner will start. The result of this scan will be available the following day, and you can find it in the platform tab called "Compliance Dashboard".
You are then redirected to the installation tab. Here you are presented with the script for the consent pop-up you need to implement on your website.
Once you have implemented the script on your website, you are ready to collect consent from your users.
The next step is to set up prior consent for all tracking technologies on your website that do not fall under the category of strictly necessary. This way these tracking technologies will not run/execute unless the user gives their consent to the category which it falls under.
What is a Consent Solution?
A Consent Solution should be viewed as a container, which can hold domains, templates (predefined pop-up designs), and languages.
This means that all the domains in one Consent Solution can only have one logo, one design, and one text. The domains can however have different languages. You can read about this here.
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.
Note: all the public domains in the same consent solution will be shown in the policy after "your consent is valid for...".
- Internal Test Domain
This type does not get scanned and will therefore not display any cookies in any of the templates, but will otherwise function as the rest of the solution. You should use this for design and text testing purposes. The URLs for this type could be something like dev.yourdomain.com, test.yourdomain.com, or staging.yourdomain.com.
Note: The URL will not be shown in the policy after "your consent is valid for...".
- Public Test Site
This type can show all templates but is not scanned. Instead it will show scan results from a public domain (if there is one in the same consent solution).
Note: public test sites will be shown alongside public domains in the policy after "your consent is valid for...".
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 less) 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 via opt-in or opt-out toggles. This is meant to be placed on a separate page, most commonly 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 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 yourdomain.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 pushing for new consents.
What are the Privacy Widgets
Cookie Information's Consent Solution includes 3 privacy widgets that can be displayed to your visitors:
- Consent Pop-up
- Privacy Controls
In the sections below, we will descript each widget.
The Consent Pop-up widget also includes the "Renew Consent" Icon. Read more about that here.
Privacy Controls allow the user to selectively opt-in/opt-out to specific categories of cookie tracking.
What is the Cookie Control SDK?
Website owners have to respect the user's right to only be tracked after they have given consent, based on which type of ways the user wants to be tracked (functional, statistics, or marketing).
This means that the website owners need to control when a cookie setting script is being executed on the website and block the cookie setting script until they have collected a valid consent from the user.
Compliant use of cookie tracking can be achieved by using the Cookie Control SDK that allows website owners to control when cookie setting scripts are executed on the website.
The Cookie Control SDK is part of your consent solution and has to be implemented in order to solve prior consent.