Google Tag Manager consent integration

If you mean Google Tag Manager (GTM) consent integration, the typical setup is to connect GTM with a Consent Management Platform (CMP) or use Google Consent Mode so tags only fire according to the user’s consent choices.

Common setup options

1. Use Google Consent Mode

This lets Google tags adjust behavior based on consent signals like:

• analytics_storage
• ad_storage
• ad_user_data
• ad_personalization

You usually:

1. Set default consent to denied.
2. Update consent after the user accepts or rejects cookies.
3. Let GTM/Google tags read those settings.

2. Use a CMP with GTM

Many CMPs can push consent states into GTM, for example:

• Cookiebot
• OneTrust
• iubenda
• Complianz

They typically:

• Show a banner
• Store the user’s choice
• Fire a dataLayer event or set consent via gtag('consent', ...)

Basic implementation idea

Default consent before tags load

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}

  gtag('consent', 'default', {
    ad_storage: 'denied',
    analytics_storage: 'denied',
    ad_user_data: 'denied',
    ad_personalization: 'denied'
  });
</script>

Update consent when user accepts

<script>
  gtag('consent', 'update', {
    ad_storage: 'granted',
    analytics_storage: 'granted',
    ad_user_data: 'granted',
    ad_personalization: 'granted'
  });
</script>

In GTM

You can configure:

• Consent Overview to see which tags require consent
• Tag-level consent checks
• Consent Initialization trigger for consent defaults

Best practice

• Set consent defaults before any tags fire
• Use Consent Initialization for default settings
• Only update consent after a clear user action
• Test in GTM Preview and Google Tag Assistant

If you want, I can give you:

1. a step-by-step GTM setup,
2. a Cookiebot/OneTrust integration example, or
3. a custom HTML + dataLayer implementation.