This article will try its best to serve as a map for your compliance journey. It will give you the best practice sequence on when to do what. It will link to other articles that go in-depth with our products, and it gives you some of the great tips and tricks that we have learned along the way.
Using the Cookie Information Platform
When adding your domain you should configure the scanning depth, scanning frequency and language. Please keep in mind that the depth and frequency affect pricing.
The domain has to be added as a "public domain" for our scanner to start. Once added, a scan result should be ready in about 24-48 hours. You can also add both internal and external test domains, however, neither of these is scanned.
Deciding on your consent pop-up.
You'll then need to decide on which consent pop-up you'd like to use on your website.
Overlay v2 and v3 are our newest versions fitted for the most strict interpretation of the regulations and laws covering cookie consents on websites. It also follows the latest accessibility standards.
You can make changes to the design of the templates and the text. However, in this case, we can no longer promise accessibility compliance. We also recommend getting your legal experts to approve the texts before making changes.
How do I install the script?
When you have completed the above steps, all you need is to implement the consent pop-up on your website. This implementation is done directly through the source code of your website or through different integrations we have.
Once implemented, we start to collect the consent your visitors give through the consent pop-up. These are stored safely in our databases for five years. The consent is valid for 12 months when consent is given for all categories, and only for 14 days when one or more categories are declined.
Do you support other languages?
We have more than 40 translations of our pop-up, all free to use. Make sure you have added the languages in the Consent Solution(s) you have created. This way, you can control which language is used on the pop-up.
Holding back cookies before consent is given
It is a must for your website to become compliant. So, you are not allowed to set any cookies before the user has given consent, and your website has to respect the choices made by the user.
In Cookie Information, we have two handy tools called auto-blocking* and the Cookie Control SDK which solve this task. There are multiple ways of implementing the tools as the Consent pop-up, and we have them all listed in the same article.
*Note that on all Consent Solutions created after May 6th, 2021, auto-blocking will automatically be enabled.
Classify all your cookies
The last point of the agenda is to make sure all cookies are classified and listed in the consent pop-up. If some of them are unclassified because we do not recognize them, you can define or add them directly from our platform.
Did I do it correctly?
You can find out by testing your implementation.