- Start by using the platform
- Then make a decision about your Consent pop-up
- How do I install the damn thing?!
- But what about the other languages?
- Now you need to hold back cookies prior to consent
- Lastly, you should be checking that all the cookies are classified
- Did I do it correctly?
Looking to become compliant eh? Well, you have come to the right place. 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 our greatest tips and tricks that we have learned along the way.
Start by using the platform
A small step for man and also a small step for you! You need to have your website whitelisted in a Consent Solution on our platform at app.cookieinformation.com.
When creating your domain the most important thing is to set it up, and then you can return to configure the scanning depth and scanning frequency at a later point, but do keep in mind that this affects pricing.
For our Cookie Crawler to start the domain has to be listed as a public domain. Once it has been added a scan result should be ready in about 48 hours.
Then make a decision about your Consent Pop-up
The next step does require some more action on your part. You need to make a decision on the Consent pop-up you see on your website and your visitors will interact with.
Overlay V2 is our most updated version fitted for the most strict interpretation of the regulations and laws covering cookie consents on websites. It is also updated with the latest availability standards.
You are able to make changes to the design of the templates and the text. However, In this case, we can no longer promise the availability standards are as they should be and we recommend getting your own legal experts to approve the texts before making changes.
- See the templates
- How to change the template
- How to change the text of the template
- How to make changes to the template
How do I install the damn thing?!
Easy breezy lemon squeezy! When you have completed the above steps all you need is to implement the consent pop-up on your website. This can be done directly through the source code or through different integrations we have.
Once this is implemented we start to collect the consents your visitors give through the Consent pop-up. These are stored safely in our databases for 5 years. The Consent itself is valid for 12 months when it is a big YES, and only for 14 days when it is not a big yes.
- Implementation guides
- Changing the lifetime of the consent
- Finding a users specific consent
But what about other languages?
We have a little more than 40 translations of our widgets all free to use. Make sure you have added the languages in the Consent Solution(s) you have created and then you can control which language is used on which website during the implementation of the Consent Pop-up.
Now you need to hold back cookies prior to a consent
Is a must for your website in order for you to become compliant. Therefore 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 country this is solved by our handy tool called the Cookie Control SDK. As the Consent pop-up, this can be implemented in different ways and we have them all listed up in the same article.
Lastly, you should be checking that all the cookies are classified
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 or some of them have not been found you can simply define or add them directly from our platform.
Did I do it correctly?
You can find out by reading through this article.