CookieConsent + Tealium iQ Consent Integration

This integration is available without a feature flag, unlike most Early Access programs. We recommend thorough testing, as with any custom implementation. For further assistance, contact your Tealium Support representative.

CookieConsent is a flexible, open-source CMP integrated with Tealium’s Consent Integrations. This guide outlines how to configure CookieConsent using Consent Integration in Tealium iQ. Combined with Consent Integrations, CookieConsent offers a better experience and additional features not found in the Consent Manager, including:

• A/B testing for consent banners.
• Robust enforcement and queue system to ensure no unconsented data is tracked.
• Better accessibility support.
• A block-by-default framework to help prevent issues caused by user errors. For more information, see Handling conflicts in enforcement conditions.
• Collect (and similar tags) can be set to refire, triggering both “necessary” and “targeting” tracking on the server-side with clearly marked events to avoid duplicate tracking.

Like the current Consent Manager, IAB Framework - TCF is not supported by CookieConsent. Customers requiring an IAB TCF CMP or a Google-certified CMP will need to use an alternative solution. For more details, see CookieConsent: Is CookieConsent the right tool for you?.

Why use it?

CookieConsent is set to replace Tealium’s Consent Manager for customers who seek a robust, non-commercial CMP. It delivers a dependable consent capture layer with flexible and robust enforcement, tailored to meet complex compliance needs.

How it will be released

• The integration template will eventually be pre-built into Tealium iQ.
• Extensions will appear pre-filled in the privacy tab for easier customization.
• Default purpose groups may include sample logic from the templates.

Categories, services, and purposes explained

CookieConsent V3 supports both categories and service-level consent options:

• Categories: Broad groups like necessary or functional.
• Services: Specific vendors or sub-purposes within categories such as necessary-necessary_vendor1.

To simplify, categories and service names are merged with a hyphen prefix for transparency. For example:

• A necessary category contains services necessary_vendor1 and necessary_vendor2.
• In GDPR mode, both the category and its services are allowed.
• In California mode, all except “targeting” are allowed.

Requirements

Before proceeding, ensure you have the following:

• Tealium iQ Tag Management
• Tealium Consent Integrations

Integration steps

Complete the following steps to set up the CookieConsent integration in Tealium iQ:

1. Download the required files
2. Create a custom consent integration and enforcement rule
3. Create purpose group
4. Set up the template
5. Set up the injection extension
6. Configure the consent logging extension
7. Save and publish Tealium iQ profile
8. Test and troubleshoot
9. Customize configuration

Download the required files

Download the following integration template and extensions:

• CookieConsent v3 template
• Injection extension
• Consent logging extension

Tealium hosts the CMP files for stability and convenience:

• https://tags.tiqcdn.com/libs/cookieconsent/v3.0.1/cookieconsent.umd.js
• https://tags.tiqcdn.com/libs/cookieconsent/v3.0.1/cookieconsent.css

Configure CookieConsent with Consent Integration in Tealium iQ

Step 1: Create a custom consent integration and enforcement rule

1. Go to the iQ Tag Management > Consent Integrations section.
2. Click Add Integration.
3. Enter a name for the integration that clearly identifies its purpose.
4. Select Custom from the vendor drop-down list.
5. Enter a placeholder value for Vendor ID such as disabled.
6. Define an appropriate enforcement rule. Include exceptions as needed for specific use cases.
7. Click Next.
8. Select a publish location and click Next.

Step 2: Create purpose group

Create a Purpose Group if one does not already exist:

1. Select **+ New Purpose Group **from the purpose group drop-down list.
2. Click Create Purpose Group.
3. Enter a name and description.
4. Click Next.
5. Create purposes:
   1. For each of your cmpConfig.categories (from the injection extension code), add a purpose.
   2. For each purpose, use either the category key (such as necessary) or a specific service key within the category (such as necessary-necessary_vendor1) to map consent decisions in the purpose group.
6. Click the Tealium iQ Purpose tab.
7. To ensure Tealium iQ always loads, assign Tealium iQ to a purpose that users cannot opt out such as Strictly Necessary.
8. Click the Map Tags tab.
9. Assign each tag to an appropriate purpose.
10. Enable tag refiring if you want tags, such as the Tealium Collect tag, to refire when consent is updated in the same event.
11. Click Save to save the purpose group.
12. Click Save to save your consent integration.
13. Save and publish the Tealium iQ profile to generate the template for your new integration.

Step 3: Set up the template

1. In the admin menu, click Manage Templates.
2. Select the template for your consent integration from the drop-down list
3. Paste the CookieConsent v3 template code into the template editor.
4. Apply the changes and save.

Step 4: Set up the injection extension

1. Click + Add Extension > Advanced.
2. Add a Javascript Code extension.
3. Enter a Title to identify the extension.
4. Under Scope, select Pre Loader.
5. Name the extension and paste the injection extension code into the editor.
6. Click Apply.

Step 5: Configure the consent logging extension

1. Repeat the steps for adding a new Javascript Code extension.
2. Set the scope to Preloader.
3. Paste the consent logging extension code into the editor.
4. Click Apply.

Step 6: Save and publish Tealium iQ profile

Save and publish the Tealium iQ profile to the Dev environment and test before publishing to the Prod environment. You have now successfully configured CookieConsent with Tealium iQ Consent Integration.

Test and troubleshoot

Demo sites

Use the following demo sites to verify implementation:

• Opt-in Mode (GDPR-style): https://solutions.tealium.net/hosted/cjaquith/tiq-from-querystring.html?account=services-caleb&profile=consent-integration-open-source&env=prod&opt_out_mode=false
• Opt-out Mode (California-style): https://solutions.tealium.net/hosted/cjaquith/tiq-from-querystring.html?account=services-caleb&profile=consent-integration-open-source&env=prod&opt_out_mode=true

Verify your consent integration setup

1. Visit the demo sites above and accept tracking.
2. Open the Developer Tools JavaScript console.
3. Use the following commands in your browser’s Developer Tools to test functionality:
   1. CookieConsent.show(true) to display the banner.
   2. CookieConsent.showPreferences(true) to show the preferences dialog.
4. Validate the following: 3. Check for the correct display of banners and dialogs. 4. Verify the consent decision is logged in the cc_cookie cookie. 5. Use the Consent Register in Developer Tools to monitor consent activity.

Clear cookies (such as cc_cookie) between decisions to reset consent status.

Tests

For a suite of end-to-end integration tests for CookieConsent and Tealium Consent Integration, see CookieConsent + Tealium iQ - End-to-end integration tests.

Customize configuration

Modify the JSON configuration in the injection extension to match your specific needs (such as categories, services, styles). For more details on all the available CookieConsent configuration options, see CookieConsent: Configuration Reference.

Additional Resources

• Consent Integration: Reference for Consent Integration setup.
• CookieConsent v3.0.1 Playground: Explore configurations and styles.
• CookieConsent: UI Customization: Guide for UI customization.