CookieYes Setup and Configuration

You can install it yourself, but the default configuration is unlikely to make your site fully compliant. The automated cookie scanner is a useful starting point but it assigns categories based on a general database, not your specific site setup. Scripts that should be blocked are often not blocked by default. Google Consent Mode v2 requires specific configuration to work correctly. And the GTM integration needs to be set up in the right order to pass consent signals properly.

If you are using CookieYes for a personal blog, the default setup may be acceptable. If you are using it for a business site where GDPR compliance needs to be demonstrable, particularly in a regulated sector, a properly configured setup is worth the investment.

The clearest test is to visit your site with an empty browser cache, deny all non-essential cookies, and then check which cookies and tracking scripts actually load. You can do this with browser developer tools or a cookie auditing tool.

If Google Analytics, Facebook Pixel, or any other non-essential tracking is loading before you accept, your current setup is not compliant regardless of what the banner shows. We commonly find this when auditing existing CookieYes installations.

Google Consent Mode v2 is a framework that tells Google's tools, including Google Analytics 4 and Google Ads, what consent status the current visitor has given. With it correctly implemented, GA4 can use modelled data to fill in gaps where consent has been denied while still respecting the visitor's choice. Without it, you either violate consent rules or lose measurement data entirely.

CookieYes supports Google Consent Mode v2, but the implementation must be configured to fire before the Google Tag Manager container and before GA4 initialises. Getting this sequence wrong is a common problem that results in consent signals being ignored by Google's tools.

Yes, and the integration is important to get right. CookieYes needs to load before GTM so that consent signals are available when GTM fires. Within GTM, you then create consent-based triggers that fire specific tags only when the relevant CookieYes category, such as analytics or marketing, has been granted.

We configure this integration as part of every CookieYes setup so that your GTM tags fire correctly based on consent status.

Any non-essential script on your site. Common ones include Google Analytics, Google Ads, Facebook Pixel, LinkedIn Insight Tag, HubSpot tracking, Hotjar, Intercom, Drift, Mailchimp tracking, ActiveCampaign site tracking, Pinterest Tag, TikTok Pixel, and any other advertising or analytics tools.

We audit every script on your site and configure the appropriate blocking for each one, either through CookieYes's native script manager or through GTM consent triggers.

We use CookieYes's banner builder to create a banner and preference centre that matches your brand colours, typography, and overall site style. We configure the banner position, layout, button labelling, and behaviour including whether it floats, appears as a popup, or uses a banner bar format.

We also ensure the preference centre, where visitors can manage individual consent categories and withdraw consent, is clearly accessible from every page, typically through a persistent link in the footer.

Our CookieYes configuration service covers the cookie audit, category review and correction, script blocking setup, Google Consent Mode v2, GTM integration, and banner design. Cost depends on the number of third-party scripts on your site and the complexity of your GTM setup.

We provide a fixed-price quote after reviewing your site.

CookieYes has a free plan that covers basic consent management, but for most business sites we recommend one of the paid plans. The paid plans include unlimited page scans, consent logs with detailed records, Google Consent Mode v2 support, and priority support, all of which are important for demonstrating compliance. We advise on the right plan for your usage as part of our setup service.