Skip to content
  • Features
  • Pricing
  • How it works
  • Sign in(opens in a new window)
  • Sign up
Logo
Sign up now
[email protected]
  • Features
  • Pricing
  • How it works
  • Updates
  • User Area(opens in a new window)
  • Customer Support
  • Documentation & Support
  • Resources
  • Terms of Service
  • Privacy
  • Cancellation & Refunds
ISO 27001ISO 27017ISO 27018ISO 20000-1ISO 14001ISO 9001

© CIVIC 2026. All rights reserved.Version: 2.3.2

You are currently viewing documentation for Cookie Control Premium. View the documentation for Cookie Control v9.
Cookie Control
Premium
  • Getting Started
  • Consent
  • Script Blocking
  • Branding
  • Integrations
  • Templates and Plugins
  • User Area
  • API Reference
  • Migrating from v9
  • Support

Google Tag Manager Premium Template

On this page

OverviewAdvanced vs Basic Consent modeCreate a Custom EventUsing Custom Events

Overview
Anchor link for Overview

The Cookie Control Premium Google Tag Manager (GTM) template provides a simple way to integrate Cookie Control with your GTM container.

Using the GTM template
Anchor link for Using the GTM template

  1. Download template.tpl from the Cookie Control GitHub repository at https://github.com/CivicUK/gtm-premium-template(opens in a new window).
  2. In your GTM container, go to Templates → Tag Templates → New, then use the options menu to Import the template.tpl file you downloaded.
  3. Create a new tag in the GTM container and select the imported Cookie Control template as its tag type.
  4. In the tag configuration, enter your apiKey and domainKey. You can find these in the Domain Management page within the Installation Code, or in the Setup Guide page within the Verify Installation section of the Cookie Control Premium User Area(opens in a new window) . Then set the tag to fire on Consent Initialization - All Pages.
Once published, consent categories, banner content, and all other configuration options can be managed from the user area, and changes are delivered automatically without needing to edit the template.

Advanced vs Basic Consent mode
Anchor link for Advanced vs Basic Consent mode

By default Cookie Control loads using Google's Advanced Consent mode. The consent mode can be updated and set to Basic within the integration's Advanced Settings. For more information on the difference between Advanced and Basic please visit Google's support page.

When using the GTM Template and Basic consent mode, GTM container tag triggers will have to be updated in order to comply. Basic consent mode requires tags not to be fired until consent has been granted. For information on how to fire tags on consent updates please follow the steps below.

Create a Custom Event:
Anchor link for Create a Custom Event:

  1. 1. In GTM, navigate to the 'Triggers' section and create a new trigger.
  2. 2. By default, the template includes custom events for each category: 'analytics_accept', 'marketing_accept', 'functional_accept' and 'preferences_accept'.
  3. 3. Give the trigger an appropriate name (e.g. Analytics Accept).
  4. 4. Select 'Custom Event' as the trigger type found under Other.
  5. 5. Set the event name based on the conset change (e.g. analytics_accept) and set the trigger to fire on 'All Custom Events'.
  6. 6. After defining the custom event settings, 'Save' the trigger.
  7. 7. Repeat this for each consent category (e.g. Analytics, Marketing, Functional, Preferences).

Using Custom Events:
Anchor link for Using Custom Events:

  1. 1. Go to the 'Tags' section in GTM.
  2. 2. Create a new Tag, for example a 'Custom HTML' Tag.
  3. 3. Edit the HTML code block as needed.
  4. 4. Assign the previously created custom event trigger (e.g. Analytics Accept) to this tag.
  5. 5. Name the tag and 'Save'.
  6. 6. To test the custom event, once the event fires, check the browser's console for the message "dataLayer pushed" to confirm the event has been successfully recorded.
Please note, if you require a listener function to execute when the state of the specified consent type changes. Please use Google's addConsentListener API.