cookiebot

Hi @eszdan

One thing I can’t do: how can you translate the labels in the banner? (The expressions “Cookie declaration”, “About cookies”, “Hide details” and “We do not use cookies of this type”) I’d like to use it in Hungarian.

This guide explains how to set the language of the banner and declaration page:

https://support.cookiebot.com/hc/en-us/articles/360003793394-How-do-I-set-the-language-of-the-consent-banner-dialog-

Currently it’s not possible to change the labels from the Manager, but here is a workaround:

<script type="text/javascript">
   function CookiebotCallback_OnDialogInit() {
       Cookiebot.dialog.hideDetailsText = "HIDE text";
       Cookiebot.dialog.showDetailsText = "SHOW text";  
       CookieConsent.dialog.cookiesOverviewText = "My own overview text";
       CookieConsent.dialog.aboutCookiesText = "My own about text";
   }
</script>

Also, I have 52 subpages – and you sent me an email saying you scanned more than 100 – but scanning the images (all of them are in my own media repository within WP) and saying they are separate subpages, that doesn’t seem to be fair… I would be willing to pay for the package too, but this might make me look for a solution that takes the real number of subpages into account.

Wordpress differentiates between pages (static “one-off” pages like “about”, “contact”, “privacy policy” etc.) and posts (actual blog posts).

The Cookiebot scanner scans your website in-depth to identify all cookies and other tracking technology in use. Since blog posts can also contain cookies and trackers – for example in images or in embedded videos – we need to scan not only the static pages but also all the blog posts. For this reason, the number of pages according to WordPress and the number of pages according to the Cookiebot scanner will likely differ. If you are in doubt about how many pages your website has, you can get a non-binding quote here (including the subscription price, the number of subpages and an attached URL list of all identified pages): https://www.cookiebot.com/goto/quote-input/

You can read more about WordPress’ definition of a page vs. a post here: http://www.wpbeginner.com/glossary/page/

• This reply was modified 8 years ago by cookiebot.
• This reply was modified 8 years ago by cookiebot.

Hi @otta,

Thanks for reaching out!

You can find more information on how to enable prior consent for iframes (e.g. youtube and Google Maps) and image tags here:

https://support.cookiebot.com/hc/en-us/articles/360003790854-Iframe-cookie-consent-with-YouTube-example

Several sources claim that you should host Google Fonts yourself, rather than using their CDN. This will ensure that your fonts display nicely, even if the user does not consent to any tracking coming from the CDN (if such tracking exists).

You can follow the discussion at: https://github.com/google/fonts/issues/1495

• This reply was modified 8 years ago by cookiebot.

Don’t all reputable theme/plugin devs use wp_enqueue_script

The short answer is no.

All reputable WP analytics plugins we have seen so far use wp_head or wp_footer to include the script. Few have used wp_enqueue_script to include script files with additional functionality.

It is not possible to add a hook to manipulate wp_head, other than using output buffering, or through the remove_action method, which introduces other problems.

Moreover, your suggested approach is a string comparsion, where we search for javascript files that set cookies on your website. When we find a <script> tag in the wp_enqueue_script pipeline, that contains the javascript file, you propose that we change it so that it works with Cookiebot. What if a WP user has two (or several) plugins that insert a script tag with the same filename, but on different pages? Your proposal would also block the other script from working, even if it isn’t setting cookies. You may think that this is a rare case, but since WordPress runs 30% of the internet, this WILL happen. How will your approach work with inline scripts; those with no src attribute, which we cant filter?

Now you may have various workarounds but unfortunately it isn’t a stable solution at all.

The real solution would be if a users consent state could be signaled to WP Core, and accessed by other plugins through WP Core. Then the plugin developers would not have to create specific support for Cookiebot, but would be working with this framework instead. Hopefully this will come in the future, as WP Core is working hard on making WP GDPR compliant, and we’ll do our best to contribute to this.

That is why we have created a ticket for the WP Core team to add this functionality. Please have patience and stay tuned at https://core.trac.wordpress.org/ticket/44043

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

Hi @eleg7

Thanks for reaching out!

If you can’t change the logo from the Cookiebot administration tool, then you can hide it by adding some CSS to your website.

Try this:

#CybotCookiebotDialogPoweredbyLink {
display: none;
}

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

@tallsam,

You can get a non-binding quote here (including the subscription price, the number of subpages and an attached URL list of all identified pages): https://www.cookiebot.com/goto/quote-input/.

See also: https://support.cookiebot.com/hc/en-us/articles/360003797213

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

@rinch

Please note that if your existing trigger is of the event type “Page View”, you need to change it to event type “Window Loaded” since the visitor’s consent is not available to GTM before the window has loaded.

It’s possible to mark up script tags outside of GTM, and Cookiebot will still work, but you have to insert Cookiebot in GTM, and not in the <head> tag.

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

@tallsam,

1. I’m still not seeing a subpages count on the page you linked to. Perhaps it is on a different page? Just trying to figure out which premium plan I’ll fall under.

Here’s a screenshot of the page count and subscription: http://prntscr.com/jf067z

2. Is Cookiebot compatible with IAB framework for GRDP? This would be helpful as affiliate systems like Skimlinks can detect if consent has already been granted so they don’t ask again.

Not yet, but we are investigating the possibilities of integrating with the IAB framework.

3. I’m not seeing Amazon affiliate cookies listed. Perhaps the reason is that a click on an Amazon affiliate link has to occur before the cookie is sent. Search as I might, I can’t find anything on Amazon affiliate links and GDPR. Do you have any knowledge on this you could share?

As far as we’ve understood by investigating the Amazon afflite cookie, it is first set when they click your affiliate link. Therefor, it is most likely set by Amazon (when visiting their website) and not your website.

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.