CookieYes Configured Properly, Not Just Installed
CookieYes setup and configuration that covers the full job, from a proper cookie audit and accurate categorisation through to real script blocking, Google Consent Mode v2 and Google Tag Manager. Built by UK specialists so consent is genuinely respected and your analytics stay accurate.
Some of our direct clients
Why Businesses Choose Zestcode
UK specialists with 7+ years of website compliance work who configure CookieYes properly, so consent is genuinely respected and your analytics stay accurate rather than a banner sitting over scripts that fire anyway.
Accurate Cookie Categorisation
We manually review and correct every cookie category beyond what the automated scan assigns, so nothing is miscategorised and nothing is missed.
Working Script Blocking
We configure CookieYes to actually block analytics and marketing scripts until consent is given. Not just display a banner while scripts load anyway.
Google Consent Mode v2
Full Google Consent Mode v2 implementation so GA4 and Google Ads respect consent choices while maintaining accurate conversion measurement.
GTM Integration
CookieYes wired correctly into Google Tag Manager so consent signals fire in the right order and tag triggers respect consent categories.
Third-Party Script Configuration
HubSpot, Facebook Pixel, LinkedIn Insight, Hotjar, and other marketing tools assigned to the correct categories and blocked until consent is given.
Branded Banner and Preference Centre
Banner and preference centre designed to match your brand, positioned correctly, and with a clearly accessible consent withdrawal mechanism.
The Platforms And Tags We Configure Across
WordPress, Google Tag Manager, GA4 and Google Consent Mode v2, plus third-party scripts such as HubSpot, Facebook Pixel, LinkedIn Insight and Hotjar, each assigned to the right category and blocked until consent is given.
Laravel & Bespoke Platforms
For systems and platforms that require bespoke processes, data handling complex integrations or internal business platforms with security at the forefront of the build.
WordPress & WooCommerce
For fast, reliable and easy to manage brochure based websites built following best practice with a bespoke theme powered by ACF Pro and supporting custom built plugins.
Shopify & Shopify Plus
For eCommerce and retail brands looking to grow revenue significantly online. Built using a bespoke theme specific to your brand and with a full seamless migration from legacy platforms.
Recently Completed Projects
Clintons Cards
A full migration from Magento 2 to Shopify Plus, with order, customer, product, stock and finance integrations kept live through the switch.
Ecommerce · Shopify Plus · IntegrationsQualityHive
A Laravel platform that web agencies use to capture, assign and close website bugs, taken from wireframe to launch, then handed over as clean, documented code.
SaaS platform · Laravel · API integrationsThe Sauce Foundry
A brand, a WooCommerce store and product photography for an artisan hot sauce startup, launched to a 3.8% conversion rate from day one.
Ecommerce · Branding · WooCommerceHave a project like these in mind?
Get in touchHere's What Our
Clients Say
Consistently rated 5* on Google by our full build clients and retainer clients.
CookieYes Setup FAQs
CookieYes Setup and Configuration for Genuine Consent Compliance
Installing CookieYes and getting a banner to appear is the easy part. The questions that matter are whether every cookie is categorised correctly, whether your analytics and marketing scripts actually wait for consent, and whether Google's own consent signals are wired up the way GA4 and Google Ads now expect. Here is how we handle all of it.
Why installing CookieYes yourself usually is not enough
CookieYes is a capable tool, and installing the plugin genuinely is quick. The problem is that the default install shows a banner while your analytics and marketing scripts carry on loading in the background exactly as before. Consent gets recorded, but nothing is actually being held back, which is the part that matters under UK GDPR and PECR.
A compliant setup needs the cookies categorised correctly, the scripts blocked until consent is given, and the consent signal passed on to the tools that rely on it. None of that happens on its own. It is configuration work, and it is where most self-installs quietly fall short.
We treat the plugin as the front end of a job that mostly happens behind it.
Accurate cookie categorisation beyond the automated scan
CookieYes runs a scan and takes a reasonable first guess at what each cookie is for. It is a starting point, not a verdict. Scans miss cookies set only after a form submission or a login, and they routinely file unfamiliar third-party cookies as necessary when they are anything but.
We go through the results by hand, identify what each cookie actually does, and move it into the right category. A marketing cookie sitting in the necessary bucket is not a small slip, because necessary cookies are exempt from consent and that is precisely the mistake a regulator or a complainant looks for.
The result is a cookie table you can stand behind, not a list of best guesses.
Making script blocking actually work
This is the heart of a proper configuration and the part people are most often surprised by. Prior blocking means analytics, pixels and other tracking scripts do not run at all until the visitor consents to their category. If they load first and the banner simply appears over the top, you are not compliant no matter how the banner looks.
We configure CookieYes to hold those scripts, whether they are hard-coded in the theme, added through a plugin, or injected by a tag manager. Each one is assigned to the correct category so it releases only when that category is accepted, and we confirm it by watching the network requests as we accept and reject each option.
If your consent handling sits alongside a wider compliance piece, it pairs naturally with our GDPR cookie consent setup work.
Does your banner actually block anything?
Most banners look compliant while analytics and pixels load regardless. Send us your site and we will check what fires before consent and what it would take to fix.
Google Consent Mode v2, done as a separate job
Consent Mode v2 is not the same thing as the cookie banner, and this is the point most setups get wrong. It is a set of signals that tell Google's tags whether they are allowed to use cookies and collect data. Since it became mandatory for advertisers using audiences and remarketing, leaving it out means Google Ads features quietly stop working properly.
We implement Consent Mode v2 so GA4 and Google Ads read your visitors' choices correctly. Where consent is declined, Google's tags fall back to cookieless pings, which keeps a degree of modelled conversion measurement rather than losing the data entirely.
Done properly, you respect consent and still keep your reporting and ad performance as intact as the rules allow.
Google Tag Manager integration and firing order
If your tags run through Google Tag Manager, CookieYes has to be integrated there rather than fighting it. Order matters: the consent state needs to be established before any tag evaluates whether it is allowed to fire, otherwise a tag can slip through in the moment before the banner is even answered.
We set the Consent Mode defaults early in the container, wire CookieYes to update that state on the visitor's choice, and set your tags to respect the relevant consent categories through GTM's built-in checks. Then we test it with the tag manager in preview mode to confirm each tag waits for the right signal.
The outcome is a container where consent is the gate every tag passes through, in the right sequence, every time.
A banner and preference centre that fit your site
The banner is the one part everyone sees, so it should look like it belongs to your site rather than a default template dropped on top. We style the banner and the preference centre to match your brand, position them so they are visible without burying your content, and make sure the layout holds up on mobile.
Just as important is the way out. Withdrawing consent has to be as easy as giving it, so we make sure there is a clearly accessible control to reopen preferences and change a choice at any time, which is a requirement people often forget once the initial banner is signed off.
If the banner work is part of a broader front-end refresh, it slots in well with our web design and development service, and ongoing tweaks are covered under a WordPress support retainer.
Partner with Zestcode for Industry Leading Quality and Reliability
Tell us what you're looking for and we'll see how we can help. Quotes are typically provided within 2 working days of the initial call.