Cookiebot offers full support of the required 'prior consent' so that only strictly necessary cookies are set on the user's browser before the user consents.
If you are using automated cookie blocking and you find that cookies are being set before prior consent have been obtained, please make sure that at least 24 hours has passed since you signed up. Cookiebot needs to first complete a scan of your website and analyze your cookies before being able to block all of them correctly. This first scan may take up to 24 hours.
Please also make sure that all of your cookies are properly categorized and classified.
If you are using manual cookie blocking mode and you experience that other than strictly necessary cookies are set before the user has consented, you need to implement prior consent on your website.
To enable prior consent, apply the attribute "data-cookieconsent" to cookie-setting script tags on your website. Set the comma-separated value of this attribute to one or more of the cookie categories "preferences", "statistics" and "marketing" in accordance with the types of cookies being set by the script. Finally change the value of the attribute "type" from "text/javascript" to "text/plain".
Example on modifying an existing Google Analytics Universal script tag:
<script type="text/plain" data-cookieconsent="statistics"> (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)})(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-00000000-0', 'auto'); ga('send', 'pageview');</script>If your website is loading scripts dynamically, use the functions of the Cookiebot API to hold back scripts and cookies that require consent.
Comments
0 comments
Article is closed for comments.