Articles on: Consentik Cookies

✨ Google Consent Mode V2 Integrated

The Google Consent Mode Integration feature within the app provides a seamless way for merchants to implement Google's Consent Mode on their e-commerce platform. This feature allows merchants to respect user consent for cookies, ensuring compliance with data protection regulations while still enabling the collection of critical analytics and ad performance data.


Setup Options

In your Consentik Admin → Integrations → Google Consent Mode V2, toggle Enable Google Consent Mode V2 to activate the feature.

You can then choose how you connect your Google services:


1. Use Google Tag Manager (GTM)

If you use Google Tag Manager, you have two options to integrate Google Consent Mode V2:

  • This option is fully automated.
  • No manual code setup is required.
  • The Consentik CMP Tag is added to your GTM container, and it manages consent signals for Google Analytics, Google Ads, and other Google tags automatically.
  • 👉 Follow this guide: How to integrate Consentik CMP with Google Tag Manager

Option 2 – Manually Setup

  • For users who prefer to manage GTM configuration manually.
  • Set default consent values for each parameter (e.g. ad_storage, analytics_storage, ad_user_data, ad_persionalization etc.) in the admin panel.
  • Copy the generated Head Script and insert it into your theme file (theme.liquid) right after the <head> tag.


2. No GTM (Manual Code or Other Tool)

If you’re not using GTM, choose how to implement Google services:

  • Input your Google Services Tracking IDs (e.g., G-XXXXXXXX, AW-XXXXXXXX).
  • Consentik automatically inserts the required Google tracking code and implements Consent Mode V2 behavior.
  • This setup ensures proper initialization and consent-based tag control without manual coding.

Option 2 – Keep Current Setup (Manual Code Integration)

  • Suitable if you already have Google Analytics or Ads tracking code manually added.
  • Select the default consent state for each parameter (e.g., Denied, Granted) in the Config default events section.
  • Copy the generated Head Script and paste it into your theme.liquid file, right after the <head> tag.


Configurable Parameters

You can configure the default state for each Google Consent Mode parameter:

  • security_storage
  • functionality_storage
  • personalization_storage
  • ad_user_data
  • ad_personalization
  • ad_storage
  • analytics_storage

Additionally, optional parameters are available:

  • ads_data_redaction
  • url_passthrough



Based on the setup you set, the app will default all Google Consent Mode parameters to a 'denied' state. This ensures that no data is collected without the explicit consent of the user.



When a user visits the merchant's website, they will be prompted to provide consent for various categories of cookies, including:


  • Marketing Cookies: Related to advertising and marketing efforts.

  • Analytics Cookies: Used for collecting data on user interaction and behavior.

  • Functionality Cookies: Essential for certain website features and personalization.



If the user provides their consent:


  1. Consent Update: The app will update Google Consent Mode to 'granted' for the cookie categories the user has accepted.

  1. Consent Storage: The user's preferences are stored in a cookie on their device, ensuring that their choices are remembered for future visits.

  1. Automatic Consent Application: On subsequent visits, the app will automatically read the stored cookie and apply the user's preferences without requiring them to consent again.


With this feature, merchants can manage user consent for cookies in a way that is compliant with privacy laws, user-friendly, and minimizes the impact on data collection for critical website functions. The process is designed to be transparent for users and straightforward for merchants to implement and manage.



Method 1: Using Tag Assistant


If you go to https://tagassistant.google.com/, you can debug the consent states for any sites running Google Tags.


After adding the domain that you want to debug, you can choose a Tag ID from the top of Tag Assistant, then choose the first Consent event from the navigation on the left, and select the “Consent” tab to see default value of consent, all of consent types are denied:



Come back to your website and click to "Accept" button and you can see another consent event is fired. Click to Consent Tab and see the update event



If you see a warning that “a tag read consent before a default was set”, it means you have a race condition where your consent states are not established in time before any tags that reference them have time to fire.


Method 2: Using Console on DevTool


  1. Open your site

  1. Press button F12 or **Ctrl + Shift + J** on Windows ( **Cmd + Option + J** on MacOS) or Right Mouse and select Inspect to open Console Tab on

  1. Type **dataLayer**

  1. When cookie banner show, you can see the default consent event is fired



  1. When you click to "Accept" button, you can see an Update event is fired


Updated on: 17/10/2025

Was this article helpful?

Share your feedback

Cancel

Thank you!