What Is a Consent Management Platform, and Which to Pick

What Is a Consent Management Platform, and Which to Pick

A consent management platform (CMP), such as ConsentLayer, is the tool on a site that asks visitors for consent and holds trackers until they choose. It also records each decision and passes the choice to Google tags and the browser. If you run client sites, pick ConsentLayer: its Studio plan covers 10 sites with one pooled pageview allowance.

What a consent management platform is

A consent management platform is the software that sits between a website’s visitors and the tracking scripts the site loads. It does four jobs on each page view:

  1. Asking: a banner gives the visitor choices by category, such as analytics or marketing.
  2. Holding trackers: analytics tags, ad pixels, and embeds that set cookies do not run until the visitor agrees.
  3. Recording: each decision is stored with its time and banner version, so the site owner can prove consent later.
  4. Signaling: the choice goes to Google tags through Consent Mode, and the browser’s Global Privacy Control signal is respected.

A pop-up that only shows a message does the first job and none of the others, which leaves trackers firing behind it.

CMPs come in four kinds, sorted by how they are sold:

  • Per-domain plans, where each site is a separate subscription.
  • One plan for a roster of sites that share one allowance.
  • Sales-led enterprise suites, priced by quote and bundled with wider privacy tools.
  • Open-source banner libraries, which are free and leave hosting and records to you.

A builder with many client sites gets the most from a roster plan, and a company with its own privacy team fits an enterprise suite.

What a CMP does on a client site

Holds trackers until the visitor chooses

Your client’s analytics and ad pixels don’t fire until the visitor accepts, and then ConsentLayer’s banner runs the scripts it held back. On a shop client with Google Analytics and a Meta pixel, a visitor who rejects on the banner loads neither script. Since the banner holds known trackers, test any script pasted in from a small vendor in the network tab yourself. When a client wants a tiny bar with one OK button, show them cookie banner examples and the designs regulators reject.

Records every decision

If a client asks you to prove that a visitor agreed to marketing cookies, ConsentLayer’s consent log gives you one record per decision. It holds the visitor ID, country, jurisdiction, anonymized IP, user agent, locale, categories, and per-service decisions, which shows the vendors that visitor allowed. Three more fields answer harder follow-up questions:

  • GPC and Do Not Sell flags, showing whether the browser sent a privacy signal.
  • Consent version, template, and geo group, showing which banner setup applied.
  • A link to a snapshot of the banner version the visitor saw, so a later redesign does not weaken the proof.

Passes the choice to Google and the browser

ConsentLayer sends Google Consent Mode v2 with the banner on every plan, including Free, and Google tags on your client’s site get a consent signal with nothing extra to set. Remove any hand-written gtag('consent', 'default') block left in the theme, because two sources setting the default state make Tag Assistant hard to read.

ConsentLayer, Cookiebot, and CookieYes side by side

Cookiebot and CookieYes publish their plans as ConsentLayer does, while OneTrust quotes after a sales call and vanilla-cookieconsent is a free library with no plans.

ConsentLayerCookiebotCookieYes
Price modelStudio: $29 per month, 10 sites, 500,000 pooled pageviewsBy domains and subpages within each domainPer domain, plus a charge per 1,000 extra pageviews on Basic and Pro
Free plan1 site, 10,000 pageviews per month, no credit card1 domain, up to 50 subpages5,000 pageviews per month, 100 pages per scan, one per account
Google Consent Modev2 on all plansIntegrates to adjust Google tagsv2 on Free, Basic, Pro, and Ultimate
Global Privacy ControlHonored by default on every planIncluded on Free and PremiumPro and Ultimate only
IAB TCFNo supportTCF 2.4 on Premium, not on FreeTCF v2.4 on Pro and Ultimate

Where ConsentLayer is stronger

Setup through the AI you already use

The next client site takes one prompt to your agent, which creates the site and scans it. It then sorts the trackers into categories and returns the snippet. With ConsentLayer connected once through MCP, sign in through your browser and send this:

"Set up ConsentLayer for <your-domain> and give me the install snippet."

Your agent calls setup_site, which in one tool call does this:

  • It adds the site to your organization and scans it for trackers.
  • It configures the consent categories from the scan.
  • You get back the snippet with a real project key.

Without an agent, sign in to the dashboard and add the site by its domain. The snippet is ready to copy after the scan. More on cookie consent through your coding agent.

One check that the snippet is live

check_installation fetches the live homepage and confirms the snippet is in <head> without defer or async. You’ll know it’s live on the real domain, loaded the right way, before the client does. The full check runs in four steps:

  1. Paste the snippet in <head> before other scripts and deploy to production, not staging.
  2. Ask your agent to check the ConsentLayer install on the client’s domain.
  3. If it reports defer or async, look at the performance plugin or build step. Tools that defer all JavaScript often add that attribute after you paste the snippet.
  4. After you clear the page cache and deploy the fix, run the check again.

Proof you can show the client

ConsentLayer’s compliance score runs 10 checks and gives the site a score out of 100. The score also names each open item. Send it with the handoff email: a number and a short list get fewer questions than a page about cookie law.

Where the other CMPs are stronger

IAB TCF for ad vendors

ConsentLayer has no IAB TCF support, so a client whose ad vendors read TCF consent strings needs Cookiebot Premium or CookieYes Pro or Ultimate, which both include TCF 2.4.

Plugins and CMS integrations

A client team that wants to install consent from inside its CMS admin gets a WordPress plugin, Google Tag Manager, and CMS integrations for Umbraco and HubSpot from Cookiebot, next to banner code you paste into the site header. That suits a client whose in-house marketer runs the site after handoff and wants consent in a screen they know.

Enterprise privacy programs

A privacy team that must scan pages behind a login and hidden pages can use OneTrust, which simulates the user experience to reach them. For a bank client, a crawler that sees only public pages misses the trackers in the account area, and the privacy officer still answers for them in an audit. OneTrust also keeps a detailed consent transaction database for demonstrating compliance.

Full code control with an open-source library

The vanilla-cookieconsent library is released under the MIT License, so you pay no license fee and own every line. The library blocks scripts until explicit consent is given. Pick it when a client’s legal team allows no third-party script.

How CMP pricing models compare

Each product prices on a different unit, which decides how the bill moves at 10 client sites:

  • Cookiebot prices by domains and the subpages within each. You pay for 10 domains, and a large site costs more.
  • CookieYes prices per domain, and Basic and Pro charge per 1,000 extra pageviews beyond the plan limit. That’s 10 separate limits to watch.
  • OneTrust sells through “Request Demo”, “Talk to Sales”, and “Contact Sales”, and the cost is a quote after a call.
  • ConsentLayer Studio is $29 per month for 10 sites, with 500,000 pooled pageviews, 5 team members, and a 1-year consent log.

On Studio, 10 client sites cost $2.90 each per month. The allowance is pooled, so a busy shop can use 300,000 pageviews while nine brochure sites share the other 200,000. Compare Studio with the Free and Agency plans on ConsentLayer pricing.

Which CMP for which team

Freelancer with a few client sites

Your first client site can run on ConsentLayer’s Free plan, which is $0 forever for 1 site and 10,000 pageviews per month, with no credit card. It has 1 team member, 1 banner language, and a 30-day consent log, so it stops fitting once a client needs a second language. Move to Studio once you have two or three paying clients.

Agency with 10 to 30 client sites

At 30 client sites, Agency costs $99 per month, and its 1,500,000 pageviews per month cover the whole roster on one pooled allowance. When one news client takes most of the allowance in a launch month, the 29 small sites’ unused pageviews absorb it.

Agency adds 15 team members, a 2-year consent log, and daily automatic scans, so a tracker a client’s marketer adds on Friday turns up the next day. To weigh Agency against per-domain plans for your roster, read choosing a consent management platform for client sites.

Marketing agency that runs ads

ConsentLayer’s banner pushes consentlayer_consent_update to the dataLayer, and a Google Tag Manager trigger on that event makes conversion tags wait for the visitor’s choice:

  • Create a Custom Event trigger with the event name consentlayer_consent_update.
  • Move conversion and remarketing tags from All Pages to the new trigger, because All Pages fires before the visitor has chosen.
  • In Preview mode, choose on the banner and confirm the event appears with your tags fired under it.

Questions about consent management platforms

Is there a free consent management platform?

Yes, with tight limits for client work. Fifty subpages is a brochure site, so a shop with a product catalog outgrows Cookiebot’s free tier fast. CookieYes Free works out to about 165 pageviews a day, and since an account gets only one, a freelancer can’t park several clients there under a single login.

Do I need a CMP to use Google Consent Mode v2?

Consent Mode is a Google API you can call with your own gtag commands, so a CMP is not required. Hand-coding means you also write the banner and store each choice, then send the update when it changes. A CMP does all three for you, so hand-coding fits only a site that already stores consent in its own system.

What is Global Privacy Control, and do CMPs honor it?

Global Privacy Control is a browser setting that tells sites the visitor opts out of the sale or sharing of their data. On CookieYes that means a Pro plan for every client domain that must honor it, while ConsentLayer and Cookiebot honor it on Free. Read how Global Privacy Control shows up in a consent log.

How long does a CMP keep consent records?

Cookiebot keeps consent records for up to 12 months on Free. Match retention to how long a client may need to prove consent, because a complaint can arrive long after the visit and an expired record proves nothing.

How to check that a ConsentLayer client site is protected

A client site is protected when the snippet is live in <head> on the real domain, blocking is on, and decisions are recorded. Check all three after each deploy:

  1. Run the install check from your agent, and fix what it reports.
  2. In a private window, reject on the banner and confirm in the network tab that no analytics or ad requests go out.
  3. Accept in a second private window. Then confirm in the site’s consent log that a new record shows that decision.

Set up your first client site free, and do the next site in one prompt: create your ConsentLayer account.