Cookiebot doesn’t know about know about BigCommerce and BigCommerce doesn’t know about Cookiebot! Tag Rocket acts as the middleman to ensure consent signals are managed across the entire system – all the while, providing as much data as is consent-compliant.
We recommend installing Cookiebot using the inline, manual method without using Cookiebot’s automatic cookie blocking feature. This ensures you have the right balance of control, performance and data.
On This Page:
Configure Cookiebot
Follow Cookiebot’s instructions located here and follow the additional advice below for some of the steps:
Step 1 – Create a Cookiebot CMP account and add your domain
No Additional Advice
Step 2 – Choose the cookie consent banner you want to display on your website
No Additional Advice
Step 3 – Insert 2 scripts on your website to make the cookie consent banner and Cookie Declaration appear
a) Add the Cookie consent banner script to your templates/layout/base.html & templates/layout/empty.html theme files just below the <head> element.
*NOTE: Ensure automatic cookie blocking is not enabled – you can check this by ensuring your script does not include the following attribute:
data-blockingmode="auto"b) For the optional declaration, feel free to add this wherever you want but a common method is to create a new BigCommerce Web Page to add this as below:
Step 4 – Mark up cookie-setting script tags on your website to control cookies
It is important to classify your scripts so that they can be correctly handled:
- Script Manager – Ensure scripts added into your BigCommerce Script Manager are marked appropriately as Essential/Analytics/Functional/Targeting/Advertising
- Other Scripts – For scripts added to your theme files or elsewhere within BigCommerce, ensure you add Cookiebot’s “data-cookieconsent attribute” to control how they are loaded – see Cookiebot’s instructions for more specific details.
script type="text/plain" data-cookieconsent="marketing" - Google Tag Manager – Tag Rocket largely replaces the need for many Tag Manager tags and other scripts can generally utilize the BigCommerce’s Script Manager. If Google Tag Manager is used, follow Google’s specific advice for Cookiebot.
Configure BigCommerce
Even though Cookiebot’s banner will be used, we still recommend enabling the BigCommerce consent banner. That way Tag Rocket will pass on any consent changes to BigCommerce so its consent system can correctly control scripts. Tag Rocket hides the BigCommerce consent banner so it does not get in the way.
Configure Tag Rocket
For a more nuanced discussion of Tag Rocket’s consent-related features, please read our more comprehensive article “Google Consent Mode V2 on BigCommerce” but below is an example of a common configuration.
Note: Enabling “Set Default if No Cache” means you don’t need to set defaults in Cookiebot (their instructions here) unless specifying for certain regions
References: