bmlcybot
Forum Replies Created
-
Hi Vincent,
I’ve reached out to you through our support channel as well as writing here.
I am sorry you are unhappy with our solution. We do our best to provide a great service and this case does not reflect the experience of most of our clients.
Please find my response to your individual claims below.Our software does indeed work and enables compliance across hundreds of thousand of domains.
It seems that you never enabled the IAB TCF 2.0 framework in your configuration.
In order to enable the framework, you must include the following in your script snippet:
data-framework=”IAB” or by activating the IAB framework in our wordpress plugin.We have a great support team, doing their best to help our customers, however we should have advised you on the configuration mentioned above.
I am confident that your experience would have been much different, had we managed to provide you with this support on our first interaction. I am sorry that we failed to do this.We did not charge you without authorization.
We charged your account on cancellation as you authorized us to do when converting your account to a paid premium account.
We offer a 30-day free trial for anyone wanting to test our full functionality. You opted out of this by converting to a full paid subscription, accepting these terms when providing your credit card details.Cookiebot follows all applicable law and legislation.
Consumer protection law is not applicable for you as a company purchasing a service from another company.Again, I am sorry you had a poor experience and I am sure that if you are to give our solution a try again in the future you will see that it can work just great for you as well.
Hi
This is due to text required to be shown in the banner when using the IAB integration. This is necessary to comply with the IAB TCFv2 guidelines.
See more here: https://support.cookiebot.com/hc/en-us/articles/360015693200-Your-Cookiebot-banner-when-using-the-IAB-TCF-v2-0-integrationDear Ciro
We’re still here, but unfortunately at this time we are not able to offer support outside of regular EU business hours.
We are looking into the issues reported. To move things forward we need you to correct your implementation as suggested in our ticket dialogues. This is an issue occurring specific to your implementation and not one that can be mended from the Cookiebot side of things.We will follow up shortly in your open ticket with our support team. We ask kindly that you keep communication in one single ticket thread to allow for all information to be present in the case and to help us help you faster.
Well this is odd.
I do see the script again now.
It sits within an Elementor shortcode widget, which makes me think you’ve possibly inserted it manually through Elementor rather than through our Cookiebot plugin or perhaps both?
Normally removing our plugin also removes the script from your website.Hi
Sorry for the delay in following up on this.
This certainly looks like a caching issue, and I am no longer able to find any trace of Cookiebot on your website, so I believe all should be good now?Thank you very much, we are happy that you like our solution! 🙂
Hi gupster,
I’m very sorry to see this review, this must clearly be a misunderstanding that I hope we can clear up.
Our solution is built to enable and provide cookie compliance for our users.
A key to compliance in this area is gathering a valid consent from your website visitor before setting any cookies or activating any tracking scripts.
A valid consent must be transparent and fully informed.To make sure we provide proper and full information in our cookie solution we scan each unique url on the domain responding with html content to identify any possible cookies being set or tracking scripts executed, to be able to report this to your visitor when asking for their consent.
Our pricing is based on the number of pages we scan on a website. This leaves our solution free for a large number of users running smaller websites. Larger websites must be subscribed to our Premium plans. This is what allows us to run a free service for thousands of users.
If you are looking to reduce the number of pages on your website or want to read more about this topic, we have a number of articles in our help center addressing this – I recommend you start here:
Hi,
In the Cookiebot manager you can login and configure your consent banner behavior.
Go to “dialog” and check if you have “Active consent” enabled and if the check box for consent on page scroll is active.
Change to “Explicit consent” if you want to make sure that nothing happens until the visitor confirms their choice through the buttons on your consent banner.Hehe thank you – I will forward your feedback regarding ux to our product team 🙂
Hi Sosvoile
Thank you for your feedback.
We’re sorry about your poor experience with both our product and support.
While what you describe is a big contrast to what the majority of our users experience, we do acknowledge that out auto-blocking mode can have an impact on your website performance. The severity of this impact will always depend on implementation specifics of your website but for the most part it will be minimal.
In the cases where it isn’t we are happy to advise and help find a solution – Using our solution in manual mode is one certain way around this.Support is always available though our help center and our service desk at Cookiebot.com
Hi
Please write us an email at support at cookiebot, or post a support request by going to our HelpCenter (support.cookiebot.com) We will then take a closer look at this as soon as possible.
Hi sosvoile
Thank you for this.
Cookiebot’s auto blocking mode works by evaluating all elements of the DOM before releasing them to the browser. For large DOMs and sites with lots of processing, this can have an impact on performance.
In that case, we recommend that you use our manual implementation instead as this will not have the same impact on performance.Hi marcinos06
When testing this I am not able to identify any JS conflicts.
Could you provide a screenshot of what you see either here or by sending it directly to cookiebot support?
ThanksHi efi
This sounds odd. To the best of my knowledge we do not manipulate or remove classes.
Could it be that the classes are added by scripting that is being blocked by Cookiebot, or are the classes in fact on the elements in the raw source, only to disappear when the page renders?
Automatic blocking of cookies relies on our solution successfully scanning your website. This is likely not being done if it’s a staging site unless you have had authentication for the scanner setup by Cookiebot.I would suggest you a greeting at support@… with more detail and perhaps a way for us to take a look at your dev site.
Thanks!
Hi Simon
We find 129 pages on the linked site – No CDN urls as far as I can see. Can you clarify what specific urls you are referring to and where you’re seeing an excessive page count?
Thanks