cookiebot
Forum Replies Created
-
Why not? In the case of Google Fonts for example the connection is not allowed without consent. To be honest: This is not my opinion, but common sense for example in Germany.
We do not log the visitors IP number or any other personal data when the visitors browser connects to Cookiebots servers, so you do not need consent for this. We only handle personal data as described in our privacy policy.
- This reply was modified 8 years ago by Jan Dembowski.
Hi Edi,
Thanks for reaching out!
The services of Cookiebot are compliant.
No personal data is transferred to or processed on Cookiebot’s servers when the user loads our script from their browser. A connection to our server alone does not require consent.
Our Terms of Service and Privacy Policy are acceded by both parties when you sign up for our service, and is the legal basis for storing consents:
https://www.cookiebot.com/goto/privacy-policy/
https://www.cookiebot.com/goto/terms-of-service/- This reply was modified 8 years ago by Jan Dembowski.
Step 3 on our help page describes what you have to do:
To enable prior consent, apply the attribute “data-cookieconsent” to cookie-setting script tags on your website. Set the comma-separated value to one or more of the cookie categories “preferences”, “statistics” and “marketing” in accordance with the types of cookies being set by each script. Finally change the attribute “type” from “text/javascript” to “text/plain”
Example:
<!-- Global site tag (gtag.js) - Google Analytics --> <script type="text/plain" data-cookieconsent="statistics" async src="https://www.googletagmanager.com/gtag/js?id=UA-XXXXXXXX-X"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-XXXXXXXX-X'); </script>This will ensure that gtag.js is executed when the user gives consent to statistics cookies.
If you are using gtag for marketing purposes as well, you have to use
data-cookieconsent=”statistics,marketing”
Example:
<!-- Global site tag (gtag.js) - Google Analytics --> <script type="text/plain" data-cookieconsent="statistics,marketing" async src="https://www.googletagmanager.com/gtag/js?id=UA-XXXXXXXX-X"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'UA-XXXXXXXX-X'); </script>- This reply was modified 8 years ago by Jan Dembowski.
Hi Pete,
Thanks for reaching out!
Just installed your WordPress plugin on our site, but I’m not sure how much more I need to do to configure it?
With the plugin installed, will it (for example) stop Google Analytic cookies being dropped on a user’s computer if they refuse cookies? Or is further work needed?
Once you’ve installed the Cookiebot plugin, your site is not necessarily GDPR complaint, until you mark your cookie setting script tags with Cookiebots data attributes.
You can find more information on how to do that at our help page:
https://www.cookiebot.com/goto/help
After you’ve installed the Cookiebot plugin, you need to scan your website for cookies.
If you’re already signed up, you can request a scan for your domain through our manager:
https://manage.cookiebot.com/, under the “Cookies” tab.
Once the scan is complete, you can check the scan report, under the “Reports” tab, which shows all cookies our scanner found, and which JavaScript files set those cookies.
Once you have that information, you should be able to mark your script tags.
Also, I get how to apply the attribute “data-cookieconsent” on cookie-setting scripts – but the GA example applies to the Universal script tag, not the Global Site Tag (gtag) we use. Is there a significant difference to apply this?
There is no difference, you can use the same data attribute on the Global Site Tag. Alternatively, you can choose to control the cookie consent for Global Site Tag through Google Tag Manager:
https://cybot.uservoice.com/knowledgebase/articles/425087-google-tag-manager-deployment
- This reply was modified 8 years, 1 month ago by cookiebot.
- This reply was modified 8 years ago by Jan Dembowski.
Hi there,
Thanks for reaching out!
Once it’s installed and activated on my site, do I need to add any code, do anything with script tags etc? If so, is there help available for installing and getting this set up correctly?
Once you’ve installed the Cookiebot plugin, your site is not necessarily GDPR complaint, until you mark your cookie setting script tags with Cookiebots data tags.
You can find more information on how to do that at our help page:
https://www.cookiebot.com/goto/help
After you’ve installed the Cookiebot plugin, you need to scan your website for cookies.
If you’re already signed up, you can request a scan for your domain through our manager:
https://manage.cookiebot.com/, under the “Cookies” tab.
Once the scan is complete, you can check the scan report, under the “Reports” tab, which shows all cookies our scanner found, and which JavaScript files set those cookies.
Once you have that information, you should be able to mark your script tags.
Is the plugin definitely GDPR compliant? My understanding is the GDPR legislation is still changing at the moment.
The plugin is 100% GDPR complaint. As mentioned above, you have to use it correctly. You can read more about why you should choose Cookiebot here:
https://www.cookiebot.com/en/why-choose-cookiebot/
Through your main website, I’ve just requested an offer for my blog, based on the number of pages, will this the same price for the plugin?
The price is per domain. If your blog runs on WordPress and you are using the Cookiebot WP plugin, then you only need one subscription. If you need to test the plugin on develop/staging environments before going live, you can do that for free, by adding “Domain Aliases” through our manager.
- This reply was modified 8 years, 1 month ago by cookiebot.
- This reply was modified 8 years, 1 month ago by cookiebot.
- This reply was modified 8 years, 1 month ago by cookiebot.
- This reply was modified 8 years ago by Jan Dembowski.