TapCub is live — analytics, insights and live chat, free on one platform
Glossary

Consent Management Platform (CMP): Definition, Example and Limits

A CMP records who consented to which purpose and when, handles withdrawal, and signals your analytics and ad tags. Installing one is not compliance — the configuration and the records are. Includes a recomputable example of how consent rates change your numbers.

Ethan Brooks Reviewed by Lucas Hayes Also called CMP Last updated Nov 16, 2026 Glossary

Quick answer

A consent management platform (CMP) is software that asks visitors for permission to use cookies and tracking, records who consented to which purpose and when, lets them withdraw consent, and passes the consent state to analytics and advertising tags.

What is a consent management platform (CMP)?

A consent management platform (CMP) is software that asks visitors for permission to use cookies and tracking, records who consented to which purpose and when, lets them withdraw that consent, and passes the resulting consent state to analytics and advertising tags.

The useful way to think about a CMP is as a proof system, not a banner. Under GDPR Article 7(1), the controller must be able to demonstrate that a visitor consented; Article 7(3) says withdrawing consent must be as easy as giving it. A CMP exists to answer four questions on demand: who consented, when, to what, and how do they withdraw? Installing one does not make a site compliant — the configuration and the records do.

A minimal consent record has four fields (sample data):

FieldExample valueWhy it matters
User identifier (pseudonymous)cmp-user-8f3a21Ties the choice to a visitor without storing a name
Purposes and choicesanalytics: granted; ads: deniedConsent is per purpose, not one global yes
Timestamp2026-11-15T09:24:31ZProves when the choice was made
Withdrawal path"Cookie settings" link in the footerShows the choice can be changed as easily as it was given

If your setup cannot produce a record like this for an arbitrary visitor, you have a banner, not a consent management system. Whether you need consent at all depends on what you collect and where visitors are — see cookieless analytics for the tracking side.

What does a CMP do — and what does it not do?

A CMP sits between your visitors and every script that tracks them. The split between what it handles and what stays your job:

CapabilityWhat it meansBoundary
Show the consent noticePresents a banner or modal listing purposes, with accept, reject and manage optionsThe notice is UX, not a legal basis; you still decide which purposes you run
Capture granular choicesRecords a separate grant or deny per purpose (analytics, ads, functional)It cannot invent your purpose list; you must inventory every cookie and tag first
Store the consent recordKeeps who / when / what / how-to-withdraw in an auditable logCovers choices made through its own interface, not processing outside it
Handle withdrawalReopens the settings UI and updates the stored choiceDownstream tools must act on the update; a CMP cannot erase data already sent elsewhere
Signal vendors and tagsPasses consent via a TCF string or Google Consent Mode statesOnly integrated tags listen; an unmanaged script keeps firing unless you block it
Apply regional rulesShows different behavior by region, e.g. opt-in for EEA/UK visitorsRegion rules are configuration; confirming your legal basis per region remains your task

Read the boundary column as the thesis of this page: every capability captures, proves or transports a choice, but none of them by itself makes the underlying processing lawful. That is decided by your configuration and your records.

How does consent change your analytics numbers?

Sample data: a site gets 10,000 visitors from the EEA in one month. Its CMP asks for analytics consent; 62% grant it and 38% deny. Each visitor views 3 pages, and the site records 300 conversion events, spread proportionally across both groups. The analytics tool uses two collection tiers: tier 2 separates visitors with a cookie-free pseudonymous ID that links their visits; tier 1 is anonymous aggregate only, with no persistent ID.

MetricCalculationResult
Visitors who grant10,000 × 62%6,200
Visitors who deny10,000 − 6,2003,800
Pageviews recorded10,000 × 330,000 — all recorded, both groups
Visitors linkable across visitstier 2 (granted)6,200
Aggregate-only visitorstier 1 (denied)3,800
Matchable conversions300 × 0.62186 (62%)
Unmatchable conversions300 − 186114

Two things follow. One, deny does not mean zero data: the 30,000 pageviews and all 300 conversion events are still recorded — what the 3,800 denying visitors lose is the ID that ties one person's events together across visits (see collection tiers). Two, the consent rate scales your attributable data linearly: raise it from 62% to 80% and matchable conversions go from 300 × 0.62 = 186 to 300 × 0.80 = 240 — 54 more (+18 percentage points) with no extra traffic. The consent record is not paperwork; it decides how much of your funnel you can actually analyze.

How do TCF and Google Consent Mode fit in?

Two standards carry consent from the banner to the rest of your stack:

StandardWhat it isWhat the CMP does with it
IAB Europe TCFA standardized consent string encoding purpose and vendor choices for ad techA TCF-registered CMP encodes each visitor's choices into the string that ad vendors read
Google Consent ModeAn API that adjusts Google tag behavior based on consent states such as analytics_storage and ad_storageThe CMP maps banner choices to consent states and updates Google tags accordingly

Decision rule: if you run personalized ads for EU/UK visitors, choose a CMP registered in the IAB Europe TCF; if you use Google tags for analytics or ads, enable the CMP's Consent Mode integration. If you do neither, you still need consent signaling your analytics tool understands — a stored record alone does not change what your tags collect. Personalized ads usually rely on cross-site tracking, which is why ad vendors read the TCF string before they act.

What should you look for when choosing a CMP?

  • Auditable records with export. If a regulator, auditor or partner asks for proof, can you export who consented to what and when? If not, cross that CMP off your list.
  • Per-purpose granularity. If you run both analytics and ads, a visitor must be able to grant one and deny the other; a single accept-all switch is not granular consent.
  • Withdrawal as easy as giving. GDPR Article 7(3) sets this bar. If granting takes one click but withdrawing takes an email to support, the design fails; look for a persistent "cookie settings" link.
  • Regional behavior. If your traffic spans the EEA/UK and the US, you need per-region rules rather than one global banner. Start with do I need a consent banner.
  • Integrations you actually use. If your stack includes Google tags or programmatic ads, check TCF and Consent Mode support; otherwise check that the CMP can pass consent state to your analytics tool.

What are the most common consent management mistakes?

  1. Treating "banner installed" as "compliant". Fix: audit the configuration and pull one consent record end to end; the install is the start, not the proof.
  2. No withdrawal path. Fix: add a persistent footer link that reopens the consent settings, and test that a changed choice actually reaches your tags.
  3. No records kept or exportable. Fix: turn on consent logging and run a test export before you need it; "the banner asked" is not demonstrable consent.
  4. One bucket for all purposes. Fix: split analytics, ads and functional purposes, so a deny on ads does not silently kill analytics — or the reverse.
  5. Assuming deny means zero data. Fix: check what your analytics still records without consent; in the example above, all 30,000 pageviews survived. Plan reports around matchable vs aggregate-only data instead of guessing.

Every fix here is configuration or record-keeping, not another install. That is the point: a CMP solves the proof problem, and the proof lives in your settings and logs.

How does TapCub work with a CMP?

Take the same 10,000 EEA visitors, with a CMP in front and TapCub behind it. The boundary first: TapCub is not a CMP. It shows no banner and does not design your consent notice; the CMP owns the notice and the record of what each visitor was shown. TapCub receives the visitor's choice, keeps a receipt of it, and adjusts what it collects. Whether you need a banner at all depends on your configuration and local law, not on the tool (do I need a consent banner).

  1. Pass the choice to the script. When the visitor answers, have the CMP pass the granted purposes (analytics, functional, marketing) to the TapCub script; the help page above links to the consent API. Until consent arrives, the script queues events in memory by default, or drops them if you set it to.
  2. Check the region rule in Configuration › Privacy center. The project default is tier 2, and the default rule for EEA and UK visitors is tier 2 with consent required. The 6,200 visitors whose hits carry the analytics purpose stay at tier 2, which is where the 186 linkable conversions come from. If you also serve mainland China, China mode adds a stricter gate on top: collection waits until consent is given.
  3. See what the 3,800 still give you. Without the analytics purpose, a hit falls to tier 1: daily-rotating salt, no persistent ID, no autocapture, no identity. Pageviews and custom events are still stored, so the 30,000 pageviews and all 300 conversion events survive in aggregate. One exception to plan for: by default the website script does not load at all in browsers that send Global Privacy Control or Do Not Track, so those visitors are in neither group.
  4. Keep the proof exportable. Consent receipts are kept for 730 days by default, capped by your plan's retention, and All-platform analytics › Data › Data export can export them as consent_log (Pro plan or above). Data-subject requests (access, erasure, restrict, portability) are created in the same Privacy center, so a withdrawal that turns into a deletion request has one place to land. More on the setup: compliance center and GDPR-compliant analytics.

See also: What does opt-in mean? Opt-in vs opt-out and what counts as consent.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Ethan Brooks

Solutions Engineer

Covers SDKs, API integrations, and data implementation, with an emphasis on validation, system interoperability, and troubleshooting.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What is a consent management platform?

A consent management platform (CMP) is software that shows a consent notice, captures per-purpose choices for cookies and tracking, stores an auditable record of who consented to what and when, lets visitors withdraw, and passes the consent state to analytics and advertising tags.

Do I need a consent management platform?

If any of your visitors are covered by rules that require consent for cookies or tracking — such as EU ePrivacy rules for analytics and advertising cookies — you need a way to collect, record and honor those choices. Whether consent applies depends on what you collect and where visitors are.

What is the difference between a CMP and a cookie banner?

A cookie banner is only the visible notice. A CMP is the system behind it: per-purpose choices, an auditable consent record, a withdrawal path that reopens settings, and signaling to analytics and ad tags. A banner without records and signaling is interface, not consent management.

Does GDPR require a CMP?

GDPR does not name any specific tool. Article 7 requires that you can demonstrate consent and that withdrawing is as easy as giving it; the ePrivacy Directive covers cookies. A CMP is the practical way to meet those requirements at scale, but installing one alone does not make a site compliant.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics