Prompt
I'm building a site that uses Google Tag Manager and Segment. What should I use for consent management?
Latest observation
Nov 16, 2026
OpenAI APIWeb search: off
If you’re using Google Tag Manager + Segment, the best choice is usually a real Consent Management Platform (CMP), not just a cookie banner.
Recommended approach
Use a CMP that can:
- Collect consent by category
- Store and update consent preferences
- Integrate with Google Consent Mode v2
- Control Segment loading / tracking
- Support regional rules like GDPR, UK GDPR, ePrivacy, CCPA/CPRA
- Provide an audit trail / consent logs
Good options
If you want the simplest reliable setup
Use a CMP such as:
- Cookiebot
- OneTrust
- Didomi
- Usercentrics
- Osano
- Termly / iubenda for smaller setups
These are commonly used with GTM and can be wired to Segment.
What you should do technically
1) Put consent in front of tracking
Before GTM or Segment fires:
- Default analytics/marketing consent to denied
- Only enable after user opt-in where required
2) Use Google Consent Mode v2
Since you use GTM, this is important for Google tags:
ad_storageanalytics_storagead_user_dataad_personalization
3) Gate Segment based on consent
You can either:
- Load Segment only after consent, or
- Initialize Segment in a limited mode and only send events after consent
For most sites, the cleanest method is:
- Do not load Segment until consent is granted for analytics/marketing categories that apply
4) Map consent categories consistently
A common mapping:
- Necessary: always on
- Analytics: Segment analytics, GA4, Hotjar, etc.
- Marketing: ads pixels, remarketing, LinkedIn, Meta, etc.
- Preferences: personalization features
- Functional: chat/support tools if they’re non-essential
Practical recommendation by site size
Small team / simple needs
- Cookiebot or iubenda
- GTM + Google Consent Mode v2
- Segment loaded only after consent
Mid-size SaaS / ecommerce
- Didomi, Osano, or Usercentrics
- Server-side GTM if you have it
- Segment consent gating + strict tag governance
Enterprise / multi-region
- OneTrust
- Strong consent logging, workflows, geo rules, DSAR support
Important note
A “cookie banner” alone is not enough if it doesn’t:
- record consent choices,
- prevent tags from firing before consent,
- and support consent updates/revocation.
My short recommendation
If you want a solid default: Use Cookiebot or OneTrust with Google Consent Mode v2, and configure Segment to load only after analytics consent.
If you want, I can also give you:
- a recommended architecture diagram for GTM + Segment + CMP, or
- a specific implementation plan for your stack (client-side vs server-side GTM, regions, and which tools you use).