Overview of consent frameworks
CookieHub supports multiple consent frameworks to help you comply with different privacy regulations and platform requirements. A consent framework defines how user choices are collected, stored, and communicated to vendors.
What is a consent framework?
A consent framework provides a structured way to:
- Collect and manage user consent or opt-out preferences
- Communicate these preferences to third-party vendors, ad tech platforms, or analytics tools
- Ensure compliance with regional laws and industry standards
Frameworks standardize how consent data is shared across the ecosystem using machine-readable strings or signals.
Frameworks supported by CookieHub
CookieHub supports three frameworks:
CookieHub Choices
Default framework using category-based consent. Suitable for most global privacy laws when no external signaling is required.
IAB Transparency and Consent Framework (TCF) 2.2
Used for GDPR/ePrivacy compliance in the EU and UK. Required by many ad platforms (e.g., Google Ads, Meta) for personalized advertising.
IAB Global Privacy Platform (GPP)
Used for US privacy laws. Supports opt-out signals for states such as California (CPRA) and Colorado (CPA).
Integrations with external systems
In addition to these frameworks, CookieHub integrates with industry tools that require specific consent signals:
Google Consent Mode v2
Communicates consent status to Google tags for measurement and advertising.
Google Additional Consent Mode
Handles vendors not registered with the IAB TCF.
Microsoft UET Consent Mode
Sends consent signals to Microsoft advertising tags.
IAB US Privacy (legacy)
Maintains backward compatibility with older US Privacy strings.
Choosing the right framework
- Use CookieHub Choices if you do not need to send IAB strings and prefer category-based consent.
- Use IAB TCF 2.2 if you serve personalized ads in the EU or UK through vendors that require TCF signals.
- Use IAB GPP if you need to comply with US state privacy laws and signal opt-out preferences to vendors.