Supported vendor integrations
This article describes the supported CMPs in Tealium iQ Consent Integrations and how to easily gather the relevant vendor-specific information to complete your Consent Integrations setup.
How it works
Tealium iQ Consent Integrations supports integration with various consent management platforms (CMPs). You can access relevant vendor-specific information from the user interface of the supported consent management platforms (CMP) or the web page. To keep this documentation reliable and user-friendly, this section only covers the steps to retrieve vendor specific information from the web page. For steps to retrieve your Vendor ID and Purposes in the user interface of each partner CMP, see the respective CMP documentation.
To retrieve the relevant information from the web page, follow these steps:
- Visit your website where the CMP is implemented.
- Accept all tracking.
- Open the Developer Tools JavaScript console.
- Paste the CMP-specific code from the code snippets below into the Developer Tools JavaScript console.
- Enter the displayed Vendor ID, Purpose Keys and Purpose Names into your Consent Integration.
After you update your consent decision, paste the code again to see the latest interpretation.
Integration-specific instructions and code snippets
Cookiebot
Test this snippet on cookiebot.com or on your website by following the instructions in the How it works section to check compatibility and get the information needed for integration.
Didomi
Test this snippet on didomi.io or on your website by following the instructions above to check compatibility and get the information needed for integration.
The Didomi integration uses Vendors as Purposes.
Didomi doesn’t return implicitly consented purposes or vendors, this is a known bug. As a workaround until this bug is fixed, this integration unconditionally adds an always_consented
purpose key to the outbound consent decision to allow implicit triggering.
Digital Control Room
Test this snippet on digitalcontrolroom.com or on your website by following the instructions in the How it works section to check compatibility and get the information needed for integration.
OneTrust
Test this snippet on https://onetrust.com or on your website by following the instructions above to check compatibility and get the information needed for integration.
OneTrust provides a test mode to preview settings, activated by adding -test
to your Vendor ID. To simplify integration, OneTrust Consent Integrations remove the -test
suffix from Vendor IDs. For seamless integration, enter your Vendor ID without -test
in the Tealium iQ Consent Integrations UI when setting up your integration, even if you use the -test
suffix on your pages. Mismatched Vendor IDs between the Tealium iQ UI and your active integrations prevent Tealium iQ Tag Management from setting cookies or triggering tags on the page.
OneTrust supports callback functions through cmpAddCallbackToTriggerRecheck
. This enables Tealium iQ to receive real-time updates on consent status changes without polling. For more information, see Monitor and trigger consent updates.
/*
// Debugging / development output - paste into the console, or uncomment and paste the whole template during development of a custom integration
function outputDebuggingInfo () {
var outputString = ${tealiumCmpIntegration.cmpCheckIfOptInModel() ? 'Opt-in' : 'Opt-out'} Model Checks: - id: ${tealiumCmpIntegration.cmpFetchCurrentLookupKey()} - well-formed: ${tealiumCmpIntegration.cmpCheckForWellFormedDecision(tealiumCmpIntegration.cmpFetchCurrentConsentDecision())} - explicit: ${tealiumCmpIntegration.cmpCheckForExplicitConsentDecision(tealiumCmpIntegration.cmpFetchCurrentConsentDecision())} - using callback: ${typeof tealiumCmpIntegration.cmpAddCallbackToTriggerRecheck === 'function'} - consented purposes: ${JSON.stringify(tealiumCmpIntegration.cmpConvertResponseToGroupList(tealiumCmpIntegration.cmpFetchCurrentConsentDecision()))}
console.log(outputString);
}
// use the callback function to avoid console posting while debugging and allow testing of the callback function itself
if (typeof tealiumCmpIntegration.cmpAddCallbackToTriggerRecheck === ‘function’) {
tealiumCmpIntegration.cmpAddCallbackToTriggerRecheck(outputDebuggingInfo)
}
outputDebuggingInfo();
*/
Opt-out Cookie + GPC
This integration intends to provide support for very simple opt-out models such as CCPA/CPRA. It interprets the Vendor ID field as the cookie name of an opt-out cookie, and is case sensitive. A user is considered to have opted out if this cookie is found with any value, or if the Global Privacy Control (GPC) opt-out signal is found.
The Purpose Keys used in the integration and included in the default Purpose Group are:
no-selling
- For tags to allow regardless of the user’s opt-out signal. These tags don’t sell/share data or are considered strictly necessary by your legal team, etc.yes-selling
- For tags to block for opt-out users because applicable regulations or policies prohibit tracking after a user has opted out.
TrustArc
Test this snippet on trustarc.com or on your website by following the instructions in the How it works section to check compatibility and get the information needed for integration.
Usercentrics
Test this snippet on your website by following the instructions in the How it works section to check compatibility and get the information needed for integration. The Usercentrics integration uses Vendors as Purposes.
Custom Integration template
For more information about the custom integration template and how to use it, see Custom integration.
This page was last updated: March 31, 2025