What a CMP Actually Does for Advertising

A Consent Management Platform is the software layer that sits between your users and your ad stack. When a visitor arrives on your site, the CMP presents a consent dialog, collects the user’s privacy preferences, and then signals those preferences to every downstream system — your ad server, SSPs, DSPs, analytics tools, and attribution platforms.

A CMP is not just a cookie banner. In the advertising context, it performs several critical functions:

• Generates IAB TCF consent strings that tell every participant in the programmatic chain what data processing the user has authorized.
• Fires Google Consent Mode signals allowing Google tags to adjust behavior based on consent status.
• Stores and retrieves consent state on return visits, avoiding repeated prompts.
• Provides audit logs with timestamped records of every consent interaction.

Why Google Now Requires a Certified CMP

Since March 2024, Google enforces a strict requirement: any publisher serving ads in the EEA, UK, or Switzerland must use a Google-certified CMP with IAB TCF integration. Without one:

• Ad serving is restricted to non-personalized ads, reducing CPMs dramatically
• Programmatic demand drops as bidders cannot access consent strings
• Conversion data disappears without Consent Mode V2
• Account flags and policy violations accumulate

Microsoft now requires consent signals for UET tags. Meta, Amazon, and other major ad buyers are following the same trajectory.

How TCF 2.3 Works With Your Demand Partners

When a user grants consent through a TCF-compliant CMP, the platform generates a TC String — an encoded payload specifying which purposes and vendors the user has accepted. This string is shared via a standardized JavaScript API that any vendor tag can query.

When demand partners receive a valid TC String indicating consent, they can bid with full user-level targeting (30-60% higher CPMs), apply frequency capping and retargeting, and use cross-site measurement. Without a valid TC String, partners bid blind at lower CPMs or stop bidding entirely.

Consent Mode V2 and Conversion Modelling

Google Consent Mode V2 controls how Google tags behave based on consent. When a user declines, tags switch to cookieless mode, sending anonymized pings. Google uses these pings to build conversion models, recovering an estimated 50-70% of otherwise-lost conversions. Without Consent Mode V2, non-consenting users vanish from your data entirely.

Publishers who implemented Consent Mode V2 alongside a certified CMP reported recovery of 40-65% of conversion volume that had been lost after initial consent enforcement.

How the Absence of a CMP Kills Ad Revenue

• Global advertiser policies now apply consent requirements globally, not just in regulated markets
• Google’s expanding enforcement will extend beyond the EEA
• Header bidding wrappers pass TCF consent data by default — without a CMP, bid requests lack consent signals
• iOS ATT has conditioned advertisers to expect consent signals from all platforms

Why Publishers in Emerging Markets Also Need a CMP

Local regulations are catching up (Brazil LGPD, India DPDP, Thailand PDPA). Your highest-CPM demand comes from US and European advertisers whose DSPs require consent signals. In markets where most publishers lack a CMP, having one makes your inventory stand out to compliance-conscious buyers.

FlexyConsent: Built for Publishers

FlexyConsent is a Google-certified CMP with full IAB TCF 2.3 support, Google Consent Mode V2, and Microsoft UET Consent Mode. It supports 43+ languages and includes geo-targeting.

• Free plan (EUR 0/month): 5,000 pageviews
• Basic (EUR 2/month): 100,000 pageviews
• Plus (EUR 4/month): Unlimited pageviews

Get started at panel.flexyconsent.com — configure your banner and add a single JavaScript snippet to your site.