If the Cookiebot script blocks scripts on your website, then this is likely due to our scanner determining that the script is responsible for setting one or more cookies on your website, which needs to be prevented until consent has been given.
There are situations where you may need the script to execute regardless of consent and have employed alternative ways of ensuring that the cookies are only set after consent has been obtained.
You can exclude a specific script from the control of the Cookiebot automatic blocking functionality, by adding an attribute to your script tag with the name data-cookieconsent and the value "ignore"
You shouldn't use this attribute arbitrarily though. Any element that has this attribute can set tracking without the user's consent.
Furthermore, make sure that the script you assign this attribute to is in fact being blocked. You can check this by ensuring that the script has these attributes:
data-cookieconsentwith one, or a combination of these values separated with commas: "Preferences, Statistics, Marketing"
Assigning this attribute to a script that wouldn't be blocked anyway, can interfere with the automatic cookie blocking function's ability to process the page, resulting in errors which can break the page.
If a script fails to execute, despite it not setting cookies, adding the attribute won't fix the issue.
If you require further manual control, you may choose a complete manual implementation either by using our manual cookie consent script and marking up scripts individually as described here: Manual implementation guide
Or you my implement our solution using Google Tag Manager or a other tag management solutions. See our Google Tag Manager deployment guide here: Google Tag Manager deployment