cookiebot

Hi @ufopsi,

Thanks for reaching out!

We’re investigating the issue and will get back once we can reproduce it and have a fix.

[ Signature deleted ]

• This reply was modified 5 years, 11 months ago by Jan Dembowski.

Hi @tt74,

Thanks for reaching out.

1) It says on cookiebot.com site:

“- example.com/en, example.com/it and example.com/da are treated as 1 domain.”

This is how my site is also constructed so one license should be enough. But how can I make this work, when

example.com (is a WP installation)
example.com/blog-1 (is another WP installation), and
example.com/blog-2 (is also a WP installation)

Do I install plugin to each of them but use the same “activation code” or what ever you call it?

You have to install the cookiebot plugin to each of your WP installations. In the cookiebot manager, you have the option to create “Domain groups”. Each domain group has its own settings in regards to how the cookie consent banner is displayed. If you would like to display the same banner on your sites/pages, then you have to use the same CBID (which is a unique ID for each domain group) on all installations.

2) I live in a EU country, and the authorities suggest in their official instructions that if a user opts-in to cookies, by just ticking some boxes and clicking buttons, opting-out should be made as simple, and always available. Is there a mechanism where the site visitor can trigger opt-out option (at any time) as easily as he did opting-in?

If you implement the cookie-declaration that we provide, there is a link to opt out from cookies. When the user visits the cookie-declaration page, they have the ability to withdraw their consent. The shortcode for displaying the cookie-declaration is: [cookie_declaration], also explained in the installation instructions.

Moreover, if you would like to give your users an easier way of opting out, than the one we provide by default, you can implement this yourself, by using our javascript API.

Code examples:

Change consent:
<a href="javascript:CookieConsent.renew();CookieDeclaration.SetUserStatusLabel();">Changing your consent</a>

Withdraw consent:
<a href="javascript:CookieConsent.withdraw();CookieDeclaration.SetUserStatusLabel();">Withdraw consent</a>

For the above methods to work, the cookiebot javascript has to be available on the page.

3) What is considered as a page by Cookiebot? On this plugin’s rating page @arjanolsder is not happy about your pricing model. What I consider as a page, and probably also how others do, is explained here:
http://www.wpbeginner.com/glossary/page/
Having a lot of content doesn’t necessary mean that there are many pages. What is a page by your interpretation?

Our interpretation of a “Page” is not the same as in the link that you’ve provided, since a “Blog post” is not a “Page” in their terminology. For us, blog posts are also pages, and they can contain cookies through pictures, embedded videos and more. Therefor, we have to scan all links on your site, in order to provide your end-users with a full overview of all cookies, including 3rd party cookies, so that the end-users know what they are consenting to. One exception is “dynamic views”, where a page can have unique urls/links, but returns the same content, displayed in different ways. This is actually a single page, and we can filter this.

Hope that we’ve clarified your questions.

[ Signature deleted ]

• This reply was modified 5 years, 12 months ago by cookiebot.
• This reply was modified 5 years, 11 months ago by Jan Dembowski.

Hello @lauraandcelia, thank you for reaching out.

If you are looking to install Cookiebot on your clients’ websites, then our reseller program should be of interest to you.

You can read more here: https://www.cookiebot.com/en/cookiebot-reseller

If you have any questions about our reseller program you are very welcome to contact us on reseller@cybot.com

[ Signature deleted ]

• This reply was modified 5 years, 11 months ago by Jan Dembowski.

Hello again. You have received a notice that you will be upgraded from our free plan (for sites with 100 pages or less) to a premium plan because your website has more than 100 pages. In doing so, we give you 30 days free trial with full functionality and time to decide if you want to continue on the premium plan.

All Cookiebot subscriptions include monthly in-depth scans of the website and all its subpages. We have previously (https://wordpress.org/support/topic/not-interesting-for-bloggers/) clarified the reasons why we do the in-depth scans to uncover all the cookies and trackers in use on your website. It is one thing that you are willing to take a risk and only scan a part of your website. It is another thing that we as a company cannot risk our reputation by providing partial scans that will lead the website user to believe that he is being presented with the full picture of all cookies and trackers on your website when he is asked for a consent (please also see our replies to your review about how cookies and trackers can be found on all kinds of pages and embedded in content such as pictures, videos etc.).

Our solution has these in-depth scans at its core and we cannot offer partial scans. We are in dialogue with various WP parties about the best possible technical ways to ensure GDPR and ePR compliance via WP. For now, the Cookiebot solution in its present form is our best contribution to this.

Thank you very much for elaborating on your answer. We understand that it would be a tough situation for you to try and make a solid business out of installing this on your projects (although we do have a Reseller Program in place partly for the same reason).

There is, however, a clear reason why we do those in-depth scans and it has nothing to do with our company revenue or the approaching 25 May deadline:
Even though all editorial pages are based on the same theme and have the same plugins, it is still possible that cookies are coming from the content on those pages.

Tracking cookies can come from images, embedded videos, audio tags and many more. Many website owners are very surprised to see the number of cookies and trackers in use on their website because they just didn’t realize that they are there.

Our solution – and our reputation, if you will – rests on being reliable in providing the full picture of all cookies and online trackers in place. We would not be able to provide the full picture if we only did a partial scan and the Cookie Declaration that we provide would be incomplete if it did not contain the cookies and trackers from the entire website. This would not only be an issue in terms of GDPR compliance for the website owner but would also be very problematic in terms of providing transparency to the website users.

Hi @ams047,

Thanks for reacing out!

Cookiebot does not per default set third party cookies.

According to our Terms of Service: https://www.cookiebot.com/goto/terms-of-service

2.2.5. Cookiebot itself automatically sets up to two cookies in the user’s web browser when the user visits your website: The first-party cookie “CookieConsent” which stores the user’s consent and – if you enable “Bulk Consent” in Cookiebot – the third-party cookie “CookieConsentBulkTicket” which stores an encrypted key to enable Bulk Consent across your domains as described in clause 2.2.3 above. Both cookies expire automatically for renewal after 12 months from the date of the user’s consent.

The reason that you were seeing third party Google Analytics cookies, set within the .cookiebot.com domain, is because you’ve carried them over after visiting cookiebot.com. If you would have opened your site in Incognito mode, you would see that the GA cookies would not appear.

We’ve wrongfully configured our own Google Analytics setup to point at the subdomain .cookiebot.com, and because the Cookiebot script is hosted on consent.cookiebot.com, which you have to insert on your site, the third party cookies were carried over (but only because you’ve visited cookiebot.com).

Based on your input we’ve fixed this problem, so that our Google Analytics configuration is now pointing at our www subdomain, hence this will not occur again. Moreover, this will not have occurred for your end users, since they probably haven’t visited cookiebot.com. Rest assured, we haven’t used any GA data from any other domain than our own – that would not be compliant!

Thanks again for pointing out the issue.

[ Signature deleted ]

• This reply was modified 6 years ago by cookiebot.
• This reply was modified 6 years ago by cookiebot.
• This reply was modified 5 years, 11 months ago by Jan Dembowski.

You can find the scan report for your site through the Cookiebot manager:

https://manage.cookiebot.com/goto/reports

The report tells you which script tags are initiating the different cookies on your site, and where in the source code these script tags appear.

As you can see from the report, the initiators can both be “Script tag” and “Inline script”. Now you’ll have to figure out how to get to those tags, so that you can you can mark them up according to our guidelines at: https://cookiebot.com/goto/help.

If you open up the source code for your site, and look at the line for Google Analytics cookies (which you can find in the report), you’ll see that the cookies are being set by the plugin:

GADWP v5.3.2 Universal Analytics.

Now, open up your WordPress backend, and go to Plugins -> Editor.
Select “Google Analytics Dashboard for WP” in the top right corner, and click “Select”.
In the file tree go to: front->views->analytics-code.php

In this file, you’ll find the script tag that is setting the Google Analytics code. You have to mark the script tag like this:

<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','https://www.google-analytics.com/analytics.js','ga');
  ga('create', 'UA-112386193-1', 'auto');
  ga('send', 'pageview');
</script>

And it will be executed only when the user gives consent to statistic cookies.

Next, you have to figure out what plugins or templates are setting your facebook and twitter cookies as well. Look at the scan report to figure out where the cookies are initiated.

Facebook code looks something like: ...<script>(function(d, s, id)...

I would use a tool, such as Notepad++, to find out which files in your WP installation contain this code. From there, you can use the plugins editor to edit the files, or edit them directly in Notepad++.

Our goal is to have plugin developers support Cookiebot by default, so users don’t have to do this manually. We’re not there yet, but we are working on it.

Hope this helps,

Let us know if you need further assistance!

[ Signature deleted ]

• This reply was modified 6 years ago by cookiebot.
• This reply was modified 5 years, 11 months ago by Jan Dembowski.