Why?
In order to comply with data protection and privacy regulations that cover visitors to your site from territories like California, Quebec or the European Union, you are required to obtain consent about the cookies that are being used on your site. You can check here whether you have users from regulated regions.
What?
We provide a compliant solution that can be enabled for your site on request, triggering a cookie banner asking all your users for consent. The user's consent is stored in a cookie called tscc which is valid for one year, only then a user will be asked for consent once again. In case a user doesn't accept the default cookie settings (i.e. all), consent is being asked again after half a year.
Action Required
Once your site has the cookie consent module activated, every visitor will get the cookie banner to provide full or partial consent, or refuse the non-compulsory cookies entirely. If no consent for all or a certain cookie category has been given, the according script won't be loaded.
By default all site-related cookies are being covered by the cookie consent banner, but it is your responsibility to check whether third party scripts that you embed yourself through Raw HTML are using cookies.
Examples of third party scripts that require cookies
- YouTube videos that ARE NOT embedded through our content slots (please note that there's a no-cookie URL that allows to embed YouTube videos without cookies)
- Marketing snippets or scripts that you added through Raw HTML slots to analyze traffic, create heatmaps, etc.
How to remain compliant while using third party scripts?
To only load the cookie-triggering third party script when your user has consented, you need to modify the scripts that you are importing inside Raw HTML slots.
Warning: without this modification, scripts (including the cookies that come with them) will continue to be loaded, ignoring the users' cookie consent!
Loading a script through <script href>
You need to make the following modifications:
- change the script's type from text/javascript to text/plain to stop immediate execution
- add the data-category as shown below to make it run if the user consented to analytics cookies
Loading a script through code
If you have a bunch of code that resides inside a <script> tag, you need to make the following modifications:
- ensure that the script's type is text/plain (and not text/javascript) to stop immediate execution
- add the data-category as shown below to make it run if the user consented to analytics cookies
<script type="text/plain" data-category="analytics"> // the code </script>