All Collections
How does Cookie Information work?
Quick implementation guide for web
Quick implementation guide for web

Quickguide on what to do in order for you to become compliant

Anna Madsen avatar
Written by Anna Madsen
Updated over a week ago

Introduction

Are you 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 the great tips and tricks that we have learned along the way.

Start by using the Cookie Information Platform.

A small step for man and also a small step for you! It would help if you had your website whitelisted in a Consent Solution on our platform at app.cookieinformation.com.

When adding your domain, the most important thing is to add it. 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.

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.

Then decide on your consent pop-up.

The next step does require some more action on your part. It would be best to decide on the design of the consent pop-up you see 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 availability standards.

You can make changes to the design of the templates and the text. However, we can no longer promise availability compliance. We also recommend getting your legal experts to approve the texts before making changes.

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 implementation is done directly through the source code of your website or through different integrations we have.

Once implemented, we start to collect the consents 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.

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. 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 before consent.

It is a must for your website 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, we have two handy tools called Auto blocking and the Cookie Control SDK that solves this task. There are multiple ways of implementing the tools as the Consent pop-up, and we have them all listed up in the same article.

* Note that on all Consent Solutions created after May 6th, 2021, Auto blocking will automatically be enabled.

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, you can define or add them directly from our platform.

Did I do it correctly?

You can find out by reading through this article.

Related articles:

Did this answer your question?