Documentation Index
Fetch the complete documentation index at: https://docs.cookiechimp.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
How do I install the CookieChimp script?
You can install CookieChimp two ways. Direct HTML is the recommended approach — it guarantees CookieChimp loads before Google Tag Manager and any other scripts, so it can set consent defaults before any tag fires.
Add your website’s CookieChimp JS snippet at the top of the <head> tag in your HTML, before the Google Tag Manager script and any other scripts.<script src="https://cookiechimp.com/widget/abc123.js"></script>
abc123 with your website’s unique CookieChimp ID.The CookieChimp script needs to be the first script in the <head> section so it can block other scripts before they run and set cookies without consent. If other scripts are added before, they may set cookies and other storage items before consent is granted.
If you can’t edit your site’s HTML directly, you can install CookieChimp through GTM. Fire it from the Consent Initialization - All Pages trigger — this is the earliest trigger GTM exposes, so it gives CookieChimp the best chance of loading before other tags.This method does not guarantee strict ordering. The Consent Initialization trigger controls when GTM injects the CookieChimp <script> tag — but the external script still has to download and execute asynchronously. On slower networks, other tags fired by Initialization or Page View triggers can run before CookieChimp has set its consent defaults, which can lead to cookies being set without consent.If strict ordering matters (and for GDPR compliance it usually does), use the Direct HTML method instead.
-
In your GTM workspace, create a new tag and choose Custom HTML.
-
Paste the CookieChimp script into the tag:
<script src="https://cookiechimp.com/widget/abc123.js"></script>
abc123 with your website’s unique CookieChimp ID.
-
For the trigger, select Consent Initialization - All Pages.
-
Save the tag and publish your container.
You can reduce the async-download race by configuring Tag Sequencing on your other tags so they wait for the CookieChimp tag to finish, or by gating downstream tags on the cookiechimp_consent_update custom event (covered in the section below). Direct HTML remains the most reliable option.
Enable Google Consent Mode
Navigate to “Integrations” from the sidebar and enable the Google Consent Mode integration.
Add/Edit Tag
Create or update a tag and add an additional consent check so the tag only fires once the matching vendor has consent.Navigate to “Advanced Settings” > “Consent Settings”. Select “Require additional consent for tag to fire” and enter the name of the category or service that the tag needs to fire on.
Enter the exact vendor name as it appears in your CookieChimp Vendor Library, e.g Google Analytics, Hotjar, or Facebook Pixel. CookieChimp sends the consent state of each vendor to Google, so the tag will only fire when that specific vendor has been granted consent in the banner.This is the recommended approach because your visitors can opt in or out of individual vendors inside a category, and a tag should usually only fire when its own vendor is allowed, not just when the broader category has consent.The vendor name must match the name configured in your CookieChimp Vendor Library exactly, including capitalisation and spacing.
If you’d rather scope the additional consent to a whole category (so the tag fires whenever any vendor in that category has consent), you can use one of the Google consent types that CookieChimp maps your categories to. For example analytics_storage for the analytics category. See the mapping below for the full list. How does CookieChimp map to Google consent types?
GTM supports 7 different default consent types. CookieChimp maps these Google consent types into the following categories:
| CookieChimp Category ID | Google Consent Type |
|---|
| essential | functionality_storage, security_storage |
| marketing | ad_storage, ad_user_data, ad_personalization |
| analytics | analytics_storage |
| personalization | personalization_storage |
