Documentation > UCP Implementation Guide

UCP Implementation Guide

The Universal Consent Platform (UCP) supports several consent, opt-out and opt-in scenarios. Currently, this document provides guidance on how to implement and test on our platform. Check this space for regular additions and updates.

Prior Consent

Prior Consent is the act of gaining consent from website users before using any non-essential tracking or advertising technologies.  To enable Prior Consent, we need to be able to send a notification to the tag manager when user consent has been detected so the non-essential technologies can be deployed. 


Information on Description of Script, Script Deployment and Creating Notices

See More
Script Support

In general, when a script is written to a web page it automatically executes. However, this behavior should be avoided for non-essential scripts, due to prior consent. Instead, you need to write them out after consent is detected. All scripts need to be refactored and tested.

See More
Google Tag Manager Integration

Google Tag Manager (GTM) is a very popular mechanism for businesses to manage their advertising technologies in a single place. Using GTM can dramatically simplify deployment and changes of these technologies.

See More
Tealium Integration

To better support our customers using the Tealium iQ Tag Management solution we have built support into our UCP scripts. Specifically, this integration supports prior consent using the Tealium Tag Manager. This section provides the overview of that support.

See More

Cookie Consent

This section outlines the process of adding a cookie consent link either to your page or in other elements such as the banner translation text. 

Implementing Cookie Consent Tool Link

This section outlines the process of adding a cookie consent link either to your page or in other elements such as the banner translation text. 

See More

IAB Compliance

The IAB (Interactive Advertising Bureau) provides an open framework for vendors to verify consent from your site users. UCP embeds support for this framework to make it available to vendors.


This section outlines the different areas to test and how to overcome some of the challenges specific to testing different areas of the UCP.

General Functional Testing

It can be a challenge to test the UCP scripts in non-production environments. For example, if you configure a notice for “” and you are trying to test from “” the notice will not function as the domain won’t match. There are several strategies to overcome this.

See More
Country Testing

The UCP supports over 100 countries and allows you to set up specific experiences for as many countries as you need. The UCP scripts deliver a user experience based on country using IP routing provided by our content distribution network (Akamai). Naturally this makes it a little more difficult to test the different countries from a typical testing environment. The following mechanisms can be used to test the country experiences from a test environment.

See More
Language-Translation Testing

By default, the UCP scripts will pull the users configured language from their browser settings and use that to show to correct translations. There are several ways to test the different languages, so we’ll provide some context and start with an overview of how the translations on your notices function.

See More

Connect with Crownpeak