How to Install Kukie via Google Tag Manager

Kukie is now available as an official template in the Google Tag Manager Community Template Gallery. If your website already uses GTM, this is the recommended way to install Kukie - no code editing required.

Before you start

Make sure you have the following ready:

• A Kukie account with at least one site added. Create a free account if you haven't already.
• Your Kukie Site Key - find it in your Dashboard under Sites, click your site, then open the Embed Code tab. It looks like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
• A Google Tag Manager container installed on your website.
• Edit access to your GTM workspace.

Step 1: Add the Kukie CMP template to your workspace

1. Open your GTM container at tagmanager.google.com.
2. Click Templates in the left sidebar.
3. In the Tag Templates section, click Search Gallery.
4. Search for "Kukie CMP".
5. Click the Kukie CMP template, then click Add to workspace.
6. Review the permissions and click Add.

Step 2: Create a new tag from the template

1. Click Tags in the left sidebar, then click New.
2. Click Tag Configuration.
3. Under the Custom section, select Kukie CMP.
4. Paste your Site Key into the configuration field.
5. (Optional) Configure any additional options if available in the template.

Step 3: Set the trigger

Important: The Kukie tag must fire on Consent Initialisation - All Pages, not on "All Pages". This ensures that Google Consent Mode v2 defaults are set before any other tags fire. If you use "All Pages" instead, other tags may execute before consent is configured, which can lead to compliance issues and incorrect consent signals.

1. Click Triggering below the tag configuration.
2. Click the + icon to add a trigger.
3. Select Consent Initialisation - All Pages.
4. Click Save.

Step 4: Name and save the tag

1. Click the tag name at the top (e.g. "Untitled Tag") and rename it to something descriptive, such as Kukie CMP - Consent Mode.
2. Click Save.

Step 5: Test in Preview mode

1. Click Preview in the top right corner of GTM.
2. Enter your website URL and click Connect.
3. Confirm that the Kukie consent banner appears on your site.
4. In the GTM Preview panel (Tag Assistant), verify that the Kukie CMP tag fired on the Consent Initialisation event.
5. Test accepting and rejecting cookies. Confirm that the consent state updates correctly in the Tag Assistant's Consent tab.

Step 6: Publish your container

1. Exit Preview mode by closing the Tag Assistant tab.
2. Click Submit in the top right corner of GTM.
3. Add a version name, for example: Added Kukie CMP consent management.
4. Click Publish.

Your Kukie consent banner is now live on your website via Google Tag Manager.

Verifying Google Consent Mode integration

To confirm that Google Consent Mode v2 is working correctly with Kukie:

1. Open your site in an incognito or private browser window.
2. Open DevTools (press F12) and go to the Console tab.
3. Run the following command:

   dataLayer.filter(e => e[0] === 'consent')

4. You should see two types of entries:
   • A consent default entry with all parameters set to denied (set before any tags fire).
   • A consent update entry after accepting the banner, with relevant parameters set to granted.

You can also use Google Tag Assistant to inspect consent state visually, or check your GA4 DebugView to verify that events respect consent choices.

Tip: Add ?kukie_debug=1 to your URL to see detailed Kukie consent logs in the browser console, including all Consent Mode parameter updates.

Troubleshooting

Banner not appearing

If the consent banner does not show up after publishing, check the following: your Site Key is entered correctly in the tag configuration (it should match the UUID shown in your Kukie dashboard), the tag trigger is set to "Consent Initialisation - All Pages", and your site is verified in the Kukie dashboard. You can also check the browser console for error messages by adding ?kukie_debug=1 to your URL.

Tags firing before consent

If other tags are executing before Kukie has set consent defaults, the most likely cause is using the wrong trigger. The Kukie CMP tag must use the Consent Initialisation - All Pages trigger, not "All Pages". The Consent Initialisation trigger fires before all other trigger types, ensuring consent defaults are in place before any tracking tags execute.

Permissions warning when adding the template

When you add the Kukie CMP template from the Community Gallery, GTM will ask you to review its permissions. This is standard for all community templates. The Kukie template only injects scripts from cdn.kukie.io and app.kukie.io, and accesses the dataLayer for consent signalling. It is safe to approve these permissions.

Official Google Documentation

For Google's authoritative reference on Consent Mode v2, see:

• Consent Mode (Google Tag Platform documentation)
• Consent Mode for Google Ads
• Consent Mode for Google Analytics 4
• Google EU User Consent Policy
• Google Privacy & Terms

Need help?

If you run into issues or have questions about the GTM installation, we are happy to help:

• Email us at support@kukie.io
• Browse other installation guides: WordPress plugin, Direct HTML embed
• Learn more about Google Consent Mode v2 in Kukie