2023-03-01 | Release notes (by date) |Preview of Tealium Docs

Consent Integrations Launch
Tealium is excited to introduce Tealium iQ Consent Integrations, a new consent enforcement framework to enforce end-user consent decisions captured by non-Tealium consent management platforms (CMPs). Consent Integrations offers the following capabilities:
- A flexible consent enforcement framework to ensure consent preferences are managed properly.
- Each consent integration provides the option for both opt-in (GDPR-style) and opt-out (CCPA-style) enforcement patterns, ensuring compliance with critical data privacy regulations.
- Integrations are available for Didomi, OneTrust, and Usercentrics, with an integration that respects any opt-out cookie or the Global Privacy Control (GPC) signal.
- Supports custom integration development with other CMPs.
For more information about Consent Integrations, see the About Consent Integrations.

Renamed legacy consent management tools to remove specific regulation names
Updated the name of Consent Management components to remove references to specific regulations and remove GDPR Rule Creator. There are no changes in behavior.
Added new Consent logging templates to Template Status Checker
Added support for the new consent logging templates fullConsentEventHandler and partialConsentEventHandler to Tealium iQ’s Template Status Checker.
Updated partialConsentEventHandler and fullConsentEventHandler templates to version 1.0.2
Updated partialConsentEventHandler and fullConsentEventHandler templates to version 1.0.2. This fixes an issue where consent logging payloads could include the wrong cookie value as the trace_id if a cookie name included the string “trace_id”.
Updated Tealium GPC support to be more conservative and compliant out-of-the-box
The opt-out logic related to Global Privacy Control (GPC) in the cmDoNotSell template has been updated to be more conservative out-of-the-box. Previously, when a user’s consent cookie explicitly allowed tracking but the GPC signal indicated an opt-out, the GPC opt-out signal was ignored in favor of the cookie. As of version 1.2.0 of cmDoNotSell, the GPC opt-out signal is always respected, even if there is a cookie indicating that the user agrees to the sale or sharing of their data.