Saved pages

    No saved pages yet

    Start
    Small and medium-sized enterprises Franchises & store networks Publicists and media houses
    Prices & plans Move to Abicart Customers Support

      No saved pages yet

      Login Start a Webshop
      A part of Textalk
      English Svenska
      4 min read

      Set up and check Google Consent Mode v2

      By Althea.

      Let Google's tags get the right consent signals and check that they follow the visitor's choice.

      This guide is for those who administer Google measurement and advertising in Abicart. The built-in connection is described for Diversity themes with Google's settings. If you use TPL or an external consent platform, you should follow that solution's own connection. Check the store's active theme first; do not change the theme to make a field appear.

      1. Distinguish the consent banner from Consent Mode

      The consent banner collects the visitor's choice. Consent Mode sends the consent status to Google's tags. It does not replace a functioning consent solution, information for the visitor, or the assessment of what data you are allowed to process. Turning on two settings is no guarantee of GDPR compliance.

      Consent Mode v2 includes, among other things, ad_storage, analytics_storage, ad_user_data and ad_personalization. The last two apply to user data for advertising and ad personalization, respectively. Google's requirements for ad measurement and personalization depend on the service, usage, and region; this is not a general legal requirement for all websites to activate all signals.

      2. Check the store's consent solution

      1. Open the active Diversity theme under Appearance → Themes → Edit.
      2. Open the settings for Cookies under Add-ons.
      3. Check that the consent function is on. If non-essential cookies require active consent, they should not be allowed before the visitor has made a choice. Check this in the public store according to the steps below; the default mode does not have a separate visible choice in all themes.
      4. Check the texts, choices, and link to your cookie information.

      The option Require consent (Demand consent) makes the consent banner a modal dialog: the visitor needs to approve or deny before the store can be used. This choice alone does not determine which tags or cookies are allowed. A modal banner is not in itself proof that the installation complies with all applicable regulations.

      Do not turn off the consent function to make measurement work. A disabled feature or a permissive default mode can send granted signals before a new choice is made. Custom scripts and tags must also respect the consent; the theme's setting does not automatically control every custom integration.

      3. Select Google's marketing signals

      1. Open Add-ons → Google in the same active theme.
      2. Find Marketing settings for Google Consent Mode API (v2).
      3. Select Share and use user data (ad_user_data) and Track user for personalized ads (ad_personalization) only for the use you have decided on and provided information about.
      4. Save the theme's changes and check the correct published store.

      These choices do not mean that all visitors have consented to marketing. The signals are granted only when both the corresponding theme choice and the visitor's marketing consent allow it. If one of the theme choices is turned off, that signal must remain denied even after marketing consent is given.

      4. Check before and after the visitor's choice

      1. Open the store in a new browser session without previously saved consent and connect Google Tag Assistant.
      2. Check the initial consent status before making a choice. If active consent is required, relevant advertising and analytics signals must be denied before consent is granted.
      3. Choose to deny and verify that the relevant signals remain denied.
      4. Test granting consent in a separate, clean session and check the consent update.
      5. Open the page again with a saved choice. A previous consent can explain why signals are already granted; this is not the same test as for a new visitor.

      Also, verify that the default consent values are set before Google's tags and that the correct container is used. Do not place the same Tag Manager container in both the theme's Google field and as an extra script in the page header. Duplicate installations can cause incorrect ordering or duplicate events. Do not disable visitor protection to hide a warning.

      If you use TPL, an external CMP, or are missing the fields

      The instructions for Diversity should not be copied directly to TPL's separate Consent Manager (TPL) or an external CMP. Determine the active theme, what sets the default values, and what updates the consent. If this is unknown, contact support with the store ID, theme name, CMP, and a description of the setup before adding new scripts.

      Quick start

      1. Identify the active theme and consent solution.
      2. Check the consent feature and how a new visitor is handled.
      3. Select the relevant Google signals and save.
      4. Check a new visitor, a denied choice, and a granted choice in Tag Assistant.

      Subscription and applicability

      The consent settings in a Diversity theme are not a separate Plus or Pro add-on. The available fields depend on the theme and its version. Changing your subscription does not replace a correct consent setup. Google accounts, any CMP, and custom tags have their own terms.