christianusercentrics

Hi @colinfroggatt,

The Cookiebot WordPress plugin does not add or manage any page response headers.
We have also not been able to detect any issues in our own tests with the Lightspeed Cache plugin against our own plugin.

If you have any additional questions, feel free to contact our Support via this form: https://support.cookiebot.com/hc/en-us/requests/new.

Hi @haeki1!

I can see that you are loading your GTM script (which includes your GA4 tag) before the automatic blocking Cookiebot script in your source code. Due to the asynchronous load of GTM, it might have been a racing condition that determined whether or not GTM loaded before or after the Cookiebot auto-blocker was able to block it.

In order for the Cookiebot automatic blocking to work, you will need to ensure that the Cookiebot script is the first to load on your website.
You can read more about our automatic blocking mode and best practices here: https://support.cookiebot.com/hc/en-us/articles/360009074960-Automatic-cookie-blocking.

You are right, Cookiebot can only automatically block website elements that actually set some sort of cookies.
You can manually block website elements from loading, such as Google Maps iframes or scripts, by following our manual markup guide, found here: https://support.cookiebot.com/hc/en-us/articles/4405978132242-Manual-Markup-Guide.

If there is anything else we can assist with, please don’t hesitate to reach out to us directly via our Support form, found here: https://support.cookiebot.com/hc/en-us/requests/new.

Hi @regvdfregv ,

You will need to have one subscription per subdomain, even with a multi-site setup in WordPress.
If the visited subdomain URL does not match a domain added in your Cookiebot Manager, the banner will simply not show up on that subdomain and no consent management will be performed.

As long as all your subdomains are added in the same domain group, you can use the same Cookiebot ID in your Cookiebot WordPress plugin for all your domains/subdomains.

Hi @dan14 ,

I agree. We did also set up an auto-reply, but it was set up a little too late to apply to the first tickets that came through on Thursday.
Sorry!

Hi @dan14 ,

I can see that you have sent us a ticket about this issue and I’ve made sure to send you a reply just now.

Hi @dan14 ,

Unfortunately your ticket was opened in the Easter holidays. We do not offer Support during public holidays or weekends meaning that your ticket could not be picked up and answered until today.

We apologize for the inconvenience this has caused.

Hi @dan14 ,

Our banner is designed to be hidden for Google PageSpeed tests, but we are aware that this functionality does not currently work.
We are trying to find a solution, to make sure our banner does not unjustly interfere with our customers’ web vitals scores.
?
You can read more about Cookiebot and Google Core Web Vitals here:?https://support.cookiebot.com/hc/en-us/articles/360020501579-Google-Core-Web-Vitals-and-Cookiebot-CMP.

Hi Veera,

Thank you for your patience!
We have just released a new version of our plugin which solves this issue by isolating the plugin installation to the site it was installed on, rather than place it on the network level.

Updating the plugin should solve the issue now.

Let me know if you still experience any issues with this or if there is anything else we can assist with!

Hi Veera,

Thank you for reporting this behaviour!
I have reported this to our developers who will make sure to investigate it to see if we need to take any action.

I will update this thread once our developers have made a conclusion on the matter.

Hi,

If you are using the auto-blocking mode for Cookiebot, we strongly advise not to load it asynchronously or defer it. This is because our auto-blocker will need to load before any other scripts that may be setting non-necessary cookies in order to block those scripts before they can set cookies.
If you switch to manual blocking mode, you can choose to defer the Cookiebot script or load it asynchronously directly in the Cookiebot WP plugin.

It is not possible to add the Cookiebot script directly in the footer via our WP plugin, but if you have access to your source code, you can copy your manual blocking-mode version script from your Cookiebot Manager (via ‘Settings’ –> ‘Your scripts’) and insert it where you want it to load.
This should not be done with the auto-blocking version of the script, as this will need to load as soon as possible on your website for the automatic blocking to work as intended.

With manual blocking-mode, you will need to manually mark up your cookie-setting website elements, following our manual implementation guide, found here: https://support.cookiebot.com/hc/en-us/articles/4405978132242-Manual-Markup-Guide.

Hi @edithmayerhofer,

We have gotten confirmation from both our internal tests and external validation from other customers who experienced the same issue, that the 4.2.2 plugin version resolves issue that caused the Sucuri security warning.

Do you still get a warning in your Sucuri dashboard today?