Plugin Support
Hanna
(@hannausercentrics)
Hi @pawandongoloutside ,
Thank you for your message.
To help us investigate this matter thoroughly and provide you with a precise explanation, could you please submit a support ticket including the plugin’s debug information? It seems the issue might be related to the Autoblocking feature.
By opening a support case, we can better understand your setup and address the problem more effectively. We appreciate your cooperation and look forward to assisting you further.
Plugin Support
Hanna
(@hannausercentrics)
Hi @pawandongoloutside ,
Update: We were able to locate your ticket in our system and will be providing a response there shortly. Thank you for your patience!
I have same issue.. Whole eshop is broken if cookies not accepted, also need extra page reload to get js working.
Plugin Support
Hanna
(@hannausercentrics)
Hi @elmando111
Thank you for your message.
A common misconception is that Cookiebot prevents tracking by “intercepting” cookies before consent is given. Technically, this is not how it works.
Cookiebot (and similar CMPs) prevent tracking by blocking the resources that set cookies in the first place. In practice, this means that if a resource (such as a WordPress plugin, inline script, or external file) contains code that sets cookies, that entire resource may be prevented from loading until consent is given.
Because of this, Cookiebot’s auto-blocking feature can sometimes render a website unusable – particularly if a blocked file sets a mix of necessary and non-essential cookies (preferences, statistics, or marketing).
You can usually confirm this behavior if the website works normally only after accepting a specific combination of cookies. If the site only starts working once all cookies are accepted, and no essential resources appear to be blocked, it’s likely that the auto-blocking mechanism itself is causing the issue.
Possible solutions:
- Disable auto-blocking and manually mark up elements that utilize non-essential tracking instead.
Here is a guide that describes how you can apply manual mark-up: https://support.cookiebot.com/hc/en-us/articles/4405978132242-Manual-cookie-blocking.
- Identify which cookies are set from an essential file or a CDN that provides critically important resources in the scan report, categorize these as “Necessary”, and initiate a new scan to update the instructions for the auto blocker.
- Mark up the critically important resource with
data-cookieconsent="ignore" to prevent it from being blocked prior consent. Keep in mind that this can have repercussions in terms of compliance to data protection legislations or cause reference errors. Use this option only as a last resort and consider manually marking up resources instead.
If none of the above resolves the issue, please raise a support ticket so we can investigate your case more specifically. Thank you!
