Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This document will also cover some of the main AdConsent features. However, for a complete list of the available features and functions, as well as working examples, please check the AdConsent API Reference document.

Brief summary

Why should you use a CMP? A CMP is the linking tool between GDPR, which is the primary regulation in EU law on data protection and privacy, and the IAB Europe’s Transparency and Consent Framework (TCF). IAB TCF is the GDPR consent solution built by the digital advertising industry, being the standard used by the majority of vendors in the advertising business.

...

The General Data Protection Regulation (GDPR) is an European law regulation about data protection and privacy in the European Union (EU) and the European Economic Area (EEA), which also addresses the transfer of personal data to outside the EU and EEA areas.
Its primary aim is to give an individual control over his personal data and to simplify the regulatory environment for international business by unifying the regulation within the EU. It has replaced the Data Protection Directive 95/46/EC and entered live on the 25th May of 2018.
This regulation contains provisions and requirements related to the processing of personal data of individuals who are located in the EEA, and applies to any company, regardless of its location, as long as it is processing the personal information of individuals inside the EEA.
The full text of the regulation can be found here.

To implement this consent law, AdConsent uses the IAB Transparency and Consent Framework (TCF) version 2.0, which is standard for most of the big players in the internet market. You can find more details about the TCF 2.0 specification in the IAB TCF 2.0 official page.
AdConsent is an IAB Certified CMP, figuring in their official TCF 2.0 Certified CMPs list.

The resulting IAB TCF 2.0 built upon the GDPR regulation led to the need of following a set of policies and directives from the CMPs that wanted to be TCF 2.0 compliant. Some of these policies and directives include minimum acceptable dimensions for the banner or popup to be shown to the user, opt-in and opt-out buttons with equal prominence, and the obligation to show specific data and options at specific points in the consent screen navigation. It even goes to the point of having most of the popup labels either coming from the framework itself or being pre-approved texts. This means that the publisher has little freedom to personalize the GDPR banner other than changing some color styles and other CSS that may not disrupt the TCF policies, and three or four very specific labels in the banner that act as a personalized welcome message from the publisher, not carrying legal implications regarding the CMP compliance to the policies.
AdConsent tries to give the publisher the greatest possible freedom to customize the GDPR consent interface according to his needs while being within the GDPR and TCF policies. To know more about what can be done in terms of customization and configuration please refer to the AdConsent API Reference document or contact your account manager.

...

CCPA applies to all businesses that deal with Californian users with small exceptions, which you can find by checking the CCPA law here.
AdConsent implements this consent law through the IAB's CCPA Compliance Framework.

CCPA is a privacy regulation with a little bit more loose criteria than GDPR, which means that along with the IAB's CCPA Compliance Framework, the level of simplicity of use and available customization options are higher than in GDPR. In this case, for example, you don't need to show the consent banner upfront to force the user to choose. It can be brought into view by the click of a link in the publisher's page. The banner itself also doesn't need to comply with any particular styles, directives or even labels, as long as it is visible in the page and correctly informs the user about the actions that can be taken. This means that a greater deal of freedom is granted to the publisher in order to completely integrate this solution into his page look and feel.

...

In order to have a full overview of the possibilities, available functions and usage examples, please check the AdConsent API Reference document.
You can also verify a full working example in our demo page.

Integrate AdConsent

If AdConsent is used together with AdEngine there are no code changes required. You only need to add some privacy information to your page, please follow the Consent Management Page Integration Guide.

AdConsent and Cookies

AdConsent uses cookies to store user consent locally in the device. These are functional and fundamental cookies, not storing any other information other than the user given consent regarding the first-party and third-party vendors, thus being legal under any of the current privacy regulations.
Depending on the consent zone, the following cookies may be deployed by AdConsent:

...