How the consent preferences manager works
The Consent Preferences Manager makes it easy to deploy a tracking preferences option to your website. Customers are able to specify which categories of tags they want to allow. This tools offers full access to customize the code that generates the preferences pop-up and the ability to translate content for your global customers.
How it works
The Consent Preferences Manager works together with the Consent Prompt Manager to present tracking options to your customers and replaces the functionality previously offered by the Privacy Manager extension.
The consent preferences manager groups tags in categories based on their function and purpose, such as
Display Ads, or
Email Marketing. These categories are presented to the customer and displayed as toggle buttons to allow or disallow that tracking to occur. For example, if a user opts out of the
Marketing category, tags categorized in the marketing category are suppressed. If needed, customers can still access their preference selections about the types of tracking they allow by using the consent preferences popup.
The Consent Preferences Manager automatically suppresses tags in opted-out categories from loading.
Preferences popup example:
EventStream consent categories
Changes in consent preferences are also honored by Tealium EventStream connectors. The consent category of a connector action is displayed on the Action configuration screen:
When a customer sets consent category preferences, they are included in subsequent server-side requests. Only connector actions in the categories that the customer has opted into are triggered.
You have two connectors configured, one for
Analytics and one for
Personalization. A customer grants partial consent in the preference form by allowing
Analytics tracking but not allowing
Only connector actions in the
Analytics category are triggered. Any connector action categorized as
Personalization is suppressed.
AudienceStream consent category
Tealium AudienceStream is categorized in the
CDP consent category. In order for attributes and connectors to be processed in AudienceStream, the visitor must be opted into the
DataAccess consent category
EventDB is categorized in the
Big Data consent category. In order for event data to be stored in EventDB, the visitor must be opted into the
Big Data category.
AudienceDB is categorized in the
CDP consent category. In order for audience data to be stored in AudienceDB, the visitor must be opted into the
The Consent Preferences Manager offers the following features:
- Display Templates
- Customizable Style and Layout
- Multi-Language Support
- Tag Categories
After you activate and configure the preferences prompt, the changes are released in your next publish.
The Consent Preferences Manager is configurable for multiple profiles simultaneously when using global settings. This allows you to configure the preferences pop-up at the account level and have each profile inherit the global configuration. Learn more about global consent content.
Thank you for your feedback!
This page was last updated: February 21, 2023