Install CookieYes with Google Tag Manager

Watch the step-by-step walkthrough below, then follow along with the guide to create a CookieYes account and use the GTM Community Template to add a GDPR-compliant cookie consent banner to your website.

Follow the Steps Book Coaching
Step by Step

Install CookieYes with Google Tag Manager

Follow these steps alongside the video to set up CookieYes via GTM.

1

Create a CookieYes account

  • Go to cookieyes.com and sign up — a free plan is available that covers basic cookie consent for smaller websites
  • During setup, enter your website URL when prompted so CookieYes can scan your site and categorise the cookies it finds
2

Copy your Website key

  • Inside your CookieYes dashboard, navigate to Settings or the installation section
  • Copy your unique Website key — you will need this in GTM to connect the template to your CookieYes account
3

Navigate to Google Tag Manager

4

Create a new Tag and give it a name

  • In the left navigation, click Tags then New
  • Give the tag a clear name — for example CookieYes — so it is easy to identify in your container
5

Open the Community Template Gallery

  • Click on Tag Configuration to open the tag type selector
  • Scroll down and click Discover more tag types in the Community Template Gallery
6

Search for the CookieYes template

  • In the Community Template Gallery search bar, type CookieYes
  • Click on the official CookieYes template from the results
7

Add the template to your workspace

  • Click Add to workspace and accept the permissions the template requires
  • The CookieYes tag configuration panel will now open inside your new tag
8

Paste your Website key

  • In the CookieYes tag configuration, paste the Website key you copied from your CookieYes dashboard in Step 2
9

Open the Default Consent Settings

  • Scroll down in the tag configuration and expand the Default Consent Settings section
10

Click "Add Setting"

  • Click Add Setting to add consent state defaults for each consent type (analytics, advertising, functionality, etc.)
11

Disable everything and keep Regions as "All"

  • Set every consent type to Denied (disabled) — this ensures all tracking is blocked by default until the user gives explicit consent, which is required under GDPR and similar privacy laws
  • Leave the Regions field set to All so the default denied state applies globally to all visitors
12

Set the Trigger to "Consent Initialization — All Pages"

  • Click Triggering at the bottom of the tag and select Consent Initialization - All Pages
  • This special trigger fires before any other tags load, ensuring the consent state is established on every page before any tracking scripts run
  • Click Save, then Submit and Publish your container to push CookieYes live

Need 1-on-1 help with Google Tag Manager?

Book a 90-minute coaching session and we'll set up and optimise your GTM account together!

Book a Coaching Session
FAQ

Frequently Asked Questions

Common questions about installing CookieYes with Google Tag Manager.

Why do I need a cookie consent banner like CookieYes?

Privacy laws like GDPR (EU), CCPA (California), and LGPD (Brazil) require websites to obtain explicit user consent before placing non-essential cookies — such as analytics and advertising cookies — on a visitor's device. A cookie consent banner handles this by presenting users with a clear accept or decline option, recording their consent, and integrating with tools like GTM to block or allow tracking scripts based on that choice. Failing to comply can result in significant fines.

What is the "Consent Initialization — All Pages" trigger in GTM?

The Consent Initialization — All Pages trigger is a special GTM trigger that fires before the standard Page View trigger and before any other tags load. This ensures that the CookieYes consent state is established first, so that when GTM later checks whether it has permission to fire analytics or advertising tags, the correct consent signal is already in place. Using any other trigger (like All Pages) would risk firing before consent is set, which defeats the purpose of a consent management platform.

Why should I set all Default Consent Settings to "Denied"?

Setting all consent types to Denied by default implements the principle of consent by default — no tracking occurs until the user actively accepts cookies. This is the GDPR-compliant approach. The CookieYes banner will then update the consent state to "Granted" for categories the user accepts, and GTM's Consent Mode will allow the relevant tags to fire. If you set defaults to Granted, tracking would begin before the user has given consent, which is illegal under GDPR for non-essential cookies.

Do I need to publish the GTM container after setting up the CookieYes tag?

Yes. Changes in GTM only go live when you Submit and Publish a new container version. Until you publish, the CookieYes tag exists only in your workspace and will not appear on your live website. After saving the tag, click Submit in the top right of GTM, add a version name and description, then click Publish to push the changes to production.

Will CookieYes block my Google Analytics and Google Ads tags automatically?

CookieYes works with GTM's Consent Mode to control when tags fire. For this to work, your Google Analytics and Google Ads tags must be configured with the appropriate consent checks in GTM — for example, requiring analytics_storage consent before the GA4 tag fires. Most modern GA4 and Google Ads tag templates in GTM support Consent Mode natively. You will need to review each tag's consent settings to ensure it respects the signals sent by CookieYes.

What is the difference between the free and paid CookieYes plans?

The free plan covers one website and provides basic cookie consent functionality including automatic cookie scanning, a customisable banner, and GTM integration — sufficient for most small websites. Paid plans add features such as multiple domains, advanced banner customisation, geo-targeting (showing the banner only to visitors from specific regions), consent logs for audit purposes, and support for Google Consent Mode v2. If you need to comply with GDPR across multiple websites or require detailed consent records, a paid plan may be necessary.

Keep Learning

Related Tutorials

More step-by-step guides to get the most out of Google Tag Manager.

Get Personal Help

Book a 1-on-1 Coaching Session

Need a hands-on walkthrough tailored to your account? Book a 90-minute coaching session and we'll set it up together.