Preview and Configuration Guide

Our Preview tool provides an interactive experience that allows for the customizing the behavior and style of the CMP UI along with viewing how the configurations are rendered in real-time. Once you are happy with the customizations, click Download Config at the bottom of the page to generate a file with the JSON configuration object. Then deploy that object on your site with the CMP implementation.

General

  • Organization ID - issued by Verizon Media. Contact your account manager to retrieve your organization ID. Any value can be used for testing/demo purposes, but only your validated organization ID should be deployed to your production web site or app.
  • GDPR Applies Globally - Use this setting to force the CMP into GDPR scope. If enabled, the CMP will consider the user to be under GDPR irrespective of the user’s IP-geo location. Find more information about the use of this configuration property in the initialization section of the Technical Implementation Guide Guide.
  • Cookie Domain - Use this setting to specify a domain to write cookies to in order to share users’ consent preferences across subdomains.

Features

Select the IAB standard features you wish to disclose to users in the consent UI. Per the IAB TCF policies, features used by you or your partners must be disclosed at the point of collection.

Layout

  • Display as - Specifies whether to prompt for consent using a modal dialog or a non-modal banner. When the UI is displayed as a modal, users cannot dismiss the consent UI, thereby blocking them from your content until they have made explicit consent choices. Default is true.
  • Banner position - When Display as is set to banner, this setting is used to specify whether the banner appears at the top or bottom of the page.
  • Show Disagree Button - Specifies whether to show a Disagree button on the consent Landing screen. This button offers a one-click withholding of all consents. Default is true.
  • Show Details Screen - Specifies whether to show a Learn More link within the Landing screen, which takes the user to a middle layer screen that allows you to provide a more detailed description of the activities and processing described on the first screen with specific references and examples. Default is true.

Working with Non-IAB Partners

If you work with partners who have not yet joined the IAB GVL, our configuration tool allows you to add them to your consent partner list. To add a new non-IAB partner, click Add and enter the partner’s name and a link to their privacy policy. Continue building out your non-IAB partner list by adding more partners.

To distinguish them from IAB GVL members, non-IAB partners will be displayed without a blue IAB label in the partner list. Furthermore, as non-IAB partners cannot be represented in the TCF consent string, the CMP cannot signal or maintain a record of users’ choices for them in an interoperable way and, thus, displays them without a toggle in the consent UI. To exercise their privacy choices, your users must visit a partner’s privacy policy or similar privacy controls to manage their options directly with the vendor.

When working with non-IAB partners, it is important that you clearly disclose this in the language you implement in your consent flow, for example in the Partner List Heading text field, along with a clear explanation of how a user can manage how your partners process their data. Check with each of your non-IAB partners to ensure the name and privacy link you configure complies with their policies.

Language

If your site is available in other languages, generate and download a config file for each language supported. The default language is English. To localize your consent UI:

  1. Do a final review of the copy to be used with your Privacy and Legal teams.
  2. Once the text is finalized in English, select “English” from the Language drop-down and paste the copy for each text field and export the config file.
  3. Send the English text config file to a translation vendor.
    1. Given the config file schema, your translation vendor may generate a language configuration pack that includes all desired languages.
    2. If not, use the configuration tool to generate a language configuration pack. For each supported language, select the language and paste in the translation for each text field and export the config file.

Once a full language configuration pack has been exported, work with your web development team to decide how to store the config files on your site so that when a user visits, the correct language configuration can be passed to the GDPR upon initialization. Verizon Media’s CMP supports the following 24 languages supported by the IAB TCF.

Bulgarian (Bulgaria)

French (France)

Norwegian (Norway)

Croatian (Croatia)

German (Germany)

Polish (Poland)

Czech (Czech Republic)

Greek (Greece)

Portuguese (Portugal)

Danish (Denmark)

Hungarian (Hungary)

Romanian (Romania)

Dutch (Netherlands)

Irish (Ireland)

Slovak (Slovakia)

English (United Kingdom)

Italian (Italy)

Slovenian (Slovenia)

Estonian (Estonia)

Latvian (Latvia)

Spanish (Spain)

Finnish (Finland)

Lithuanian (Lithuania)

Swedish (Sweden)

Markdown in Text Terms

Verizon Media’s CMP supports markdown within larger text fields+ which defines a special syntax that can be used to embed hyperlinks into your disclosure text within the consent flow that refer the user to essential external privacy resources. To demonstrate this, consider the following syntax.

[Privacy Center](https://policies.oath.com/in/en/oath/privacy/)

The UI creates a hyperlink to the specified URL; the link text will always be Privacy Center. If used within your configurable text, our UI will treat this differently than other text by interpreting the values specified.

 

Text Fields With Default Values

The following text fields have default values translated into all 24 supported languages. If no text is provided as a part of the CMP configuration, the default values will be displayed in the UI.

Learn More Link

Optional hyperlink exposed on the Landing screen which takes the user to the Details screen to find more detailed descriptions about how their data is used and about partners their data is shared with.

Default: Learn more about how we and our partners use your data

Agree Button Text

Text displayed for the Agree button on the Landing screen and Details screen, if enabled. When a user clicks the Agree button, all solicited consents are set to on, including all available purposes and all vendors specified by the pubvendors.json file, or else the GVL.

Default: Agree

Disagree Button Text

Text displayed for the Disagree button on the Landing screen and Details screen, if enabled. When a user clicks the Disagree button, all solicited consents are set to off, including all available purposes and all vendors specified by the pubvendors.json file, or else the GVL.

Default: Disagree

Manage Options Button Text

Text displayed for the Manage Options button on the Landing screen and Details screen, if enabled. When a user clicks the Manage Options button, the Manage Options screen opens allowing them to manage their privacy choices.

Default: Manage Options

Select All Button Text

Text display for the Select All button on the Manage Options screen, both for purposes and partners. When a user clicks the Select All button, all toggles within the screen are set to on.

Default: Select All

Deselect All Button Text

Text display for the Deselect All button on the Manage Options screen, both for purposes and partners. When a user clicks the Deselect All button, all toggles within the screen are set to off.

Default: Deselect All

Continue Button Text

Text display for the Continue button on the Manage Options screen, for both purposes and partners. When a user clicks the Continue button, all currently selected toggles are saved and the user is taken to the next step in the flow.

Default: Continue

General Disclosure Heading

Optional bold heading on the Landing screen used to introduce the General Disclosure text.

Default: Before you continue to our site...

Publisher Disclosure Heading

Optional bold heading on the Details screen, if enabled, used to introduce the Publisher Disclosure text.

Default: How data brings you better ad experiences

Partner Disclosure Heading

Optional bold heading on the Details screen, if enabled, used to introduce the Partner Disclosure text.

Default: Our Partners

Feature Disclosure Heading

Required text heading for IAB TCF features you wish to use and disclose to the user on the Manage Options screen under purposes selection.

Default: 'We also use your data for the following features...'

 

Text Fields Without Default Values

The following text fields have no default values and must be specified during the CMP configuration. If no text is provided, optional text fields will be omitted from the UI, while required text fields will generate an error message to the browser console.

Our Preview tool offers best practices and sample language to demonstrate Verizon Media’s interpretation of publishers’ legal requirements under the GDPR and IAB TCF.

Brand Heading

Optional title displayed at the top of all screens in the modal consent flow. Commonly used to display your company name or brand heading.

Sample: Company Name

Disagree Confirmation

Optional confirmation message displayed when the user deselects all purposes or partners on the Manage Options screen and attempts to continue. This message provides a “last call to action” to explain the value of consent and nudge the user to consider granting their consent. When enabled, the user’s first click does not take effect, but prompts them to review and reconsider their selection. Once the confirmation is displayed, if the user clicks continue again, all solicited consents are set to off and the user is taken to the next screen. If no text is provided, the confirmation is not displayed and the user’s choice to disagree becomes effective immediately.

Our sample text highlights the importance of the user's consent (providing free content) and services and make it clear that they can update their consent preferences by visiting a privacy policy. As a publisher, you must provide a way for users to update their existing consent preferences in your privacy policy or elsewhere and inform the user about this capability.

Sample: By clicking Continue, you are withholding consent for data processing. Use of your data allows us to continue providing the best possible experience with our products and services. When you provide consent, we and our partners will only process your data for the purposes you have allowed. Please consider revisiting the purposes below and granting consent. You can update your privacy choices any time by visiting our [privacy policy](https://yoursite.com/privacy.html).

General Disclosure

Required disclosure on the Landing screen describing how and for which purposes users' data is processed and with whom data is shared. In the layered design, this disclosure is meant to be all-encompassing and provides an opportunity to clearly describe data processing in layman's terms. If the user clicks the Agree button, all solicited consents are set to on, including all available purposes and all vendors specified by the pubvendors.json file, or else the GVL.

Language on this screen must call out all processing activities clearly and specifically. Best practices encourage providing a link to your privacy policy where all processing activities are explained in more detail. Furthermore, the language must clearly explain to the user any sharing of data with third parties for the defined purposes and provide a direct link to the full list of partners that are included in the scope of consents when the user agrees.

Sample: We and our partners need your consent to access your device, set cookies, and use your data to understand your interests, perform analytics, provide relevant ads and measure their effectiveness. To see examples of how we use your data, visit our [privacy policy](https://yoursite.com/privacy.html). Select Agree to provide your consent to allow us [and our partners](https://yoursite.com/partners.html) to use your data or Manage Options to review our partners and your choices. To withhold consent to use your data, select Disagree.

Publisher Disclosure

A required disclosure on the Details screen, if enabled, used to describe in more detail how and for which purposes users' data is processed, and provides an opportunity to explain the value proposition for the user or provide specific examples for illustration.

Sample: To provide you with the best possible experience on our products, sometimes we show you personalized ads by making educated guesses about your interests based on your activity on our site. In order to continue offering you the best possible content and services, we would like your consent to collect your data to understand your interests, perform analytics, provide relevant ads and measure their effectiveness. [Learn More](https://yoursite.com/privacy.html) about how we use your data.

Partner Disclosure

If the Details screen is enabled, his disclosure is required. Use it to describe in more detail why and with whom users' data is shared, and provides an opportunity to explain the value of consent or give specific examples.

Sample: We share your data with trusted partners to bring you more relevant ads and provide a better overall experience. For example, your location data helps us and our partners identify products and businesses near you, like a nearby car dealership if you are in the market for a new vehicle. Select Agree to provide your consent to allow us [and our partners](https://yoursite.com/partners.html) to use your data or Manage Options to review our partners and your choices. To withhold consent to use your data, select Disagree.

Purpose List Heading

Required language on the Manage Options screen to introduce the IAB TCF purposes list consent screen and explain critical details about the experience, user controls, or other information presented on the screen.

Sample: Select consent preferences from the listed purposes below to determine how you want your data to be used.

Partner List Heading

Required language on the Manage Options screen to introduce the IAB TCF vendors list consent screen and explain critical details about the experience, user controls, or other information presented on the screen. For any partners relying solely on legitimate interest for all processing purposes, our UI displays Requires opt out in place of a toggle to signify that it is the only available privacy choice for the user.

Because of the complexity introduced by legitimate interest processing, we believe it is essential to explain this type of processing to users as explicitly as possible and make clear what privacy choices are available to users and how those choices ultimately affect how their data is processed or not processed.

Sample: Preferences can be set for each individual third party partner listed below. Each row expands to show how that partner plans to utilize your data. Legitimate interest based purposes require opt out. When you see Requires opt out text below, it means that unless you visit the partner’s privacy policy to manage how they will use your data, the partner will use your data without consent.

Customizable Styling

The following preset styles are available to customize the look and feel of the consent UI to match your current brand and style guidelines.

Font Family - (String) CSS web safe font family for text fields.

Text Color - (Hex) Text color for text fields.

Text Light Color - (Hex) Light text color for text fields. Used in parts of the Manage Options screen to provide contrast for certain text fields.

Link Color - (Hex) Text color for hyperlinks.

Primary Color - (Hex) Primary button color.

Primary Text Color - (Hex) Primary button text color.

Secondary Color - (Hex) Secondary button color.

Secondary Text Color - (Hex) Secondary button text color.

Background Color - (Hex) Main background color for screens in the consent flow.

Heading Color - (Hex) Background color for brand heading situated at the top of all screens in the consent flow.

Heading Text Color - (Hex) Text color for bold headings throughout screens in the consent flow.

Toggle On Color - (Hex) Color used when a toggle is switched to the on position.

Toggle Off Color - (Hex) Color used when a toggle is switched to the off position.

Banner Color - (Hex) Background color for banner overlay view. This option is only relevant when modal is set to false.

Banner TextColor - (Hex) Text color for text fields in banner overlay view. This option is only relevant when modal is set to false.

 

See UI/UX and Other Guidance in the CMP FAQs