Anyone using tracking tools, advertising networks, or analytics tools on their website today needs more than a simple cookie notice. A Consent Management Platform is not optional, but a legal requirement. Regulatory authorities now conduct technically precise reviews to verify whether users have given their consent before tracking, whether the company has documented it, and whether users can revoke it at any time. Ignoring this risks substantial fines and simultaneously loses valuable marketing data.

A CMP controls which cookies and tracking technologies are allowed to become active and when. It captures user consent granularly, i.e., separated by purpose, stores it in an audit-proof manner, and makes it available at any time. At the same time, it blocks all non-consented technologies before they load. Legally, no specific software is required: what matters is a reliable, documented consent solution, whether self-developed or purchased.

Specifically, a CMP does three things. It collects and stores consent with timestamp, user ID, and selected preferences. It controls the loading of tags, pixels, and scripts based on this decision. It provides a consent log that serves as evidence in case of dispute.

Without this technical foundation, a cookie banner remains an empty promise to regulatory authorities.

What has become stricter under GDPR and ePrivacy?

The legal situation has significantly tightened in recent years. Although the General Data Protection Regulation has existed since 2018, its interpretation by national regulatory authorities has become considerably stricter since then. Two developments in particular are relevant for website operators.

First, the burden of proof has tightened. It's not the user who must prove they didn't consent. The company must prove that valid consent existed. Anyone who doesn't maintain a clean consent log is on the wrong side in case of doubt.

Second, the ePrivacy Directive 2002/58/EC requires that website operators only set cookies and similar tracking technologies after active, voluntary, and informed consent. Opt-out, scrolling as consent, or pre-filled checkboxes are therefore inadmissible. In its current interpretation, this is already binding today, even without the long-awaited ePrivacy Regulation.

For German website operators, one detail is crucial: it's not the EU Directive itself that's directly applicable, but its national implementation. This has been found since May 2024 in the Telecommunications-Digital Services-Data Protection Act (TDDDG), which merely renamed the predecessor TTDSG in the course of the Digital Services Act. Specifically, § 25 TDDDG is decisive: it requires informed consent before a website stores or reads information on a user's device, and only makes an exception for technically strictly necessary cookies. Violations are punished by the responsible supervisory authority under § 28 TDDDG with fines of up to 300,000 euros, as explained by the IHK Cologne.

Regulatory authorities such as the French CNIL, the Austrian DSB, or the Berlin Commissioner for Data Protection have initiated proceedings against companies in recent years for disregarding precisely these points.

What Companies Risk Without a CMP

The risks are divided into three categories that together create a serious threat scenario.

  1. Fines and Proceedings These are the most obvious risk. According to Art. 83 Para. 5 GDPR, fines of up to 20 million euros or four percent of a company's global annual turnover are possible. Authorities are increasingly making use of this, even with medium-sized companies. In addition, there are cease-and-desist letters from competitors or data protection organizations.

  2. Tracking Data Loss The less discussed but operationally more serious problem. When browsers or ad blockers block tracking technologies without valid consent, a data gap arises. Without a clean consent solution, the basis for first-party data is missing, which today forms the backbone of every data-driven campaign. Analytics, conversion tracking, and remarketing run into the void.

  3. Loss of Trust Users who see a non-transparent or manipulative cookie banner lose trust in the brand. A professionally designed consent management, on the other hand, signals seriousness and respect for user privacy. This demonstrably affects opt-in rates and thus data quality.

Especially in combination with analytics and SEO strategies, missing consent data creates blind spots that lead to decisions based on false premises.

What a Legally Compliant CMP Must Deliver

Not every CMP is the same. Anyone checking whether a solution meets current requirements should mandatorily tick off the following points.

IAB TCF 2.3 as Minimum Standard

IAB TCF 2.3 has been the binding industry standard for programmatic advertising and multi-vendor setups since February 28, 2026. IAB Europe published this version as early as June 2025 and has since obligated publishers, advertisers, and CMPs to include an additional "Disclosed Vendors" segment in the consent string, which proves which vendors were actually shown to users in the consent interface. If this segment is missing, newly generated consent strings are considered non-compliant according to Google Ad Manager Help, and advertising partners no longer bid on the corresponding requests. Details on the transition are provided by IAB Europe.

The predecessor TCF 2.2 from 2023 remains valid for previously generated consent strings, but is outdated for new implementations: although it already removed "legitimate interest" as a legal basis for advertising, it does not cover the now required technical proof obligation.

Important: TCF 2.3 alone does not automatically fulfill all GDPR requirements. It's a technical foundation, not a legal all-inclusive package.

How Do CMP and Tag Manager Interact?

A CMP only unfolds its full effect in combination with a properly configured tag management system. Google Tag Manager, for example, can be set up so that it only triggers tags when the corresponding consent exists. This requires technically correct transmission of the consent status to the Tag Manager and consistent implementation of the trigger logic.

Without this integration, a tag may load before the user even had the opportunity to make a decision. This is precisely the error regulatory authorities detect during technical audits. Google Consent Mode complements this interaction: it additionally sends anonymous signals when no consent exists, thus maintaining at least part of the modeling capability of Google services. How closely consent signals and advertising systems are interlinked is also shown by looking at Programmatic Advertising, where consent data directly decides on real-time bids.

How to Implement a CMP Step by Step

Introducing a CMP is not an IT project you do on the side. It requires coordination between marketing, legal, and technology. The following steps have proven effective in practice.

1. Define Requirements and Select Provider

First, clarify which technologies are active on your website. Create a complete list of all cookies, pixels, and scripts, ordered by purpose. Then check which of these require consent and which can be based on legitimate interest.

Then select a CMP that supports IAB TCF 2.3, includes a consent log function, and has been positively evaluated by a recognized regulatory authority. Pay attention to regular updates and a clear support channel, as legal requirements continue to evolve.

2. Integration into Existing Tech Stacks

You begin implementation by embedding the CMP code in the <head> of your page, before all other scripts. This is technically non-negotiable: the CMP must load first so that it can control all subsequent scripts.

In the next step, configure your Tag Manager so that all tags query the CMP's consent status as a trigger condition. For each tag category, define which consent must exist before the tag fires.

Then systematically test the interaction: without consent, with partial consent, and with full consent. Check in the browser developer tool which cookies the browser actually sets.

3. Ongoing Maintenance and Documentation

A CMP is not a one-time setup. Whenever you integrate a new service, you must capture its cookies, categorize them, and store them in the CMP. Maintain an internal cookie documentation that you update with each deployment.

Schedule regular audits, at least semi-annually. Check whether all active scripts are correctly categorized and whether the consent log is complete and technically correct. Ongoing maintenance is the part many companies underestimate. This is precisely where a compliance gap develops again over time.

Conclusion

A Consent Management Platform is no longer an optional addition today, but a technical and legal basic requirement for every website operator using tracking or advertising. Stricter interpretations by regulatory authorities, the burden of proof under GDPR, and ePrivacy requirements leave no room for half-baked solutions.

Anyone investing in professional consent management now not only protects themselves from fines, but also secures the data foundation for marketing decisions and strengthens user trust.

Do you want to check whether your current solution meets the requirements, or introduce a CMP from scratch? Contact us. We'll be happy to advise you in a free initial consultation.