cookiebot
Forum Replies Created
-
@dan14 – did not hear back from you in regards to our latest response by mail. Will close this issue for now.
We’re happy to see that you’ve decided to stay with Cookiebot.
Let us investigate the issue and get back you. We may be able to provide a fix for this.
@dcart87 Just checked and it seems good ! 🙂
Hi @jhanbackjr
To the best of our knowledge, Jetpack has had a cookie banner for quite a while. The difference from the old and the new one, is that the new banner works with Jetpack Ads. So if your user has opted-out, Jetpack Ads may be displayed differently.
However, this does not necessarily help you become 100% GDPR compliant. You have to take prior consent into consideration. Several of Jetpacks 3rd party integrations bring along cookies which are stored in the users browser for marketing purposes. If the user has opted-out of this category, then these cookies should be blocked as well.
With our latest release, Cookiebot has added support for multiple Jetpack plugins/integrations, so that you have an easy way of applying prior consent to them.
As for your questions; how did you deactivate the Cookiebot banner? From the backend? Do you happen to have a test page where we can check.
- This reply was modified 7 years, 9 months ago by cookiebot.
You can insert that code in the header.php (Theme Header) file.
Have a look at the following, which shows how to apply prior consent:
You could also use one of the many plugins for Google Analytics. MonsterInsights has built-in support for Cookiebot. Some of the GA plugins that we have “addons” for are:
GA Google Analytics
Google Analyticator
Google Analytics +Hi @andyt1980
Amazon is setting the cookie when your user enters their website, so you are not reliable for it.
If you want prompt help then hurry up as the weekend is coming.
We can continue through mail and update this thread once the issue is resolved, with information on what caused the issue and how to fix it.
As we haven’t heard more, we’ll go ahead and resolve the issue for now.
Hi @ddpatohs
Did you follow our guide on implementing Prior Consent:
https://cookiebot.com/en/help/
?
Regards
This error may have been related to a bug we had earlier, where changes would not be persisted immediately. This has since been fixed.
Regards
Hi @cicado
We just checked your site, and can see that we found 5 necessary cookies, and 13 not classified.
You can classify the cookies under the Cookies menu:
Hi @genius2012,
Glad to hear you like the plugin!
1. Is Google Analytics already GDPR conform by using the plugin? Or do i need the change the script?
You should change the script. Do you use a Google Analytics plugin, or did you insert Google Analytics manually?
2. Is there anything to do with Adsense, Adwords, Doubleclick, GTM or did that all the plugin?
You need to apply prior consent manually, or use one of the Addons under the “Prior consent” menu of the Cookiebot plugin.
Hi there @dan14,
The banner should only pop up if the CookieConsent cookie is not present in a users browser. If you can provide your domain name, we can have a look. You can either write it here, or send it to wpsupport@cybot.com.
Hi @fastnormal
I just checked your site. It seems that your theme is causing the issue.
The HTML for the OK button looks like this:
<a id="CybotCookiebotDialogBodyLevelButtonAccept" href="javascript: void(0);" tabindex="1" lang="de"> OK </a>Your theme is setting a click event on the OK button.
The code that is causing this behaviour is in https://kunz-pr.com/wp-content/themes/salient/js/init.js?ver=8.5.5, and looks like this:
$('a[href]:not(.envira-tags-filter-link):not(.no-ajaxy):not([target="_blank"]):not([href^="#"]):not([href^="mailto:"]):not(.comment-edit-link):not(.magnific-popup):not([data-fancybox]):not(.magnific):not(.meta-comment-count a):not(.comments-link):not(#cancel-comment-reply-link):not(.comment-reply-link):not(#toggle-nav):not(.logged-in-as a):not(.add_to_cart_button):not(.section-down-arrow):not([data-filter]):not(.pp):not([rel^="prettyPhoto"]):not(.pretty_photo)').click(function(e) { ... };This fiddle demonstrates that the above click event is set on the OK button:
https://jsfiddle.net/4mdqjwbf/3/
Could you reach out to your theme developers and ask them if they have any advice, as we discourage changing their files. You are welcome to link to this thread.
- This reply was modified 7 years, 9 months ago by cookiebot.