Choosing a Google Consent Management Platform

Choosing a Google Consent Management Platform

For client sites that run GA4 or Google Ads, pick ConsentLayer. Google Consent Mode v2 is on every plan, including Free, and one Studio plan covers 10 sites. For a site that shows AdSense, Ad Manager, or AdMob ads to visitors in the EEA or UK, pick a Google-certified CMP that integrates with IAB TCF, such as CookieYes or iubenda.

Google certification and Consent Mode v2 are two different jobs

Google asks two different things of a consent banner, and the one that applies depends on whether a site shows Google ads or buys them. Since 16 January 2024, publishers that use Google AdSense, Ad Manager, or AdMob to serve personalized ads to visitors in the EEA and UK must use a Google-certified CMP that integrates with the IAB Transparency and Consent Framework (TCF).

The same rule has covered visitors in Switzerland since 31 July 2024. Google points advertisers to a separate CMP Partner Program, which is a list of vendors it works with.

A site that only runs GA4 or Google Ads tags has a different job. Its banner must send correct Consent Mode v2 signals (ad_storage, analytics_storage, ad_user_data, and ad_personalization) so Google’s tags know what the visitor allowed. For the basics, read what a consent management platform does.

Before you compare vendors, open the client’s site and look for ad slots. That one check tells you which job the banner has. A vendor that is strong on one job can be missing the other, so pick for the job the site does.

What to look for in a Google consent management platform

Run the ad check first: it decides which vendors stay on your list at all.

Whether the site shows Google ads or buys them

A site that serves AdSense, Ad Manager, or AdMob ads to visitors in the EEA or UK needs a Google-certified CMP with IAB TCF, and ConsentLayer has no IAB TCF support. A recipe blog or a local news site with ad slots is a publisher, and for that site the TCF rule cuts the shortlist before price does. Shops and SaaS sites that run Google Ads campaigns and GA4 are advertisers.

Clients often forget AdSense Auto ads code that a previous developer pasted into the theme. Search the page source for adsbygoogle before you decide which kind of site you’re looking at.

Every signal set to denied before a Google tag loads

Check that every Consent Mode signal is denied before the first Google tag runs, or GA4 and Google Ads record visitors who never made a choice. Run this check on the live site:

  1. Open the site in a private window and leave the banner alone.
  2. In the browser console, type dataLayer and find the entry that holds consent and default.
  3. Confirm that ad_storage, analytics_storage, ad_user_data, and ad_personalization all read denied in that entry.
  4. Check that the default entry sits above the first js or config entry, because a default that arrives after the Google tag has fired changes nothing.

ConsentLayer’s banner installs a gtag stub that sets every signal to denied except security_storage, with a 500 ms wait_for_update, so a Google tag that loads early waits half a second for the visitor’s choice.

Trackers that wait for the click

Load the page and watch whether the pixels fire before the visitor clicks. A banner that only shows buttons leaves the client’s site sending data anyway. Take a dental clinic site with a Meta pixel and a Hotjar script in the theme header. The banner appears and the visitor starts reading it. By then both scripts have loaded and sent the first page view. Clicking reject at that point can’t recall what already left the browser.

ConsentLayer’s banner holds known trackers until the visitor consents, then runs the held scripts, so on that clinic site the pixel stays silent until someone accepts marketing. Test any vendor by filtering the Network tab for the tracker’s domain and loading the page without clicking. There’s more on how to stop trackers firing before a visitor chooses.

What ten client sites cost

Find out whether the price is per domain. With per-domain pricing, every new client site is a new subscription. CookieYes states that pricing is per domain, and its tiers are tied to pageview volume with overage charges beyond plan limits, so ten client sites mean ten plans and ten pageview caps to watch. Work out the cost of the roster you’ll have next year, not the one you have today:

  • Count the client sites you expect to run in twelve months, since the gap between per-site and multi-site plans widens with each one.
  • Mark the sites whose traffic spikes (a seasonal shop, a launch campaign); overage lands on that one site’s plan.

For the wider buying view, read choosing a consent management platform for client sites.

Consent records included in the plan

Ask whether consent records come with the plan or are billed per 1,000 consents. A consent record is what you show a client who asks for proof. iubenda sells consent proof storage as a separate metered add-on, priced per 1,000 consents, so a busy client site adds a second line to the bill that grows with its traffic.

The request usually arrives after a complaint or a letter from a regulator, when the client asks “can you show me that this visitor agreed?”, and a banner with no consent record leaves you with nothing to send.

Google consent management platforms compared

ConsentLayer

Ten client sites cost one Studio plan at $29 per month, with 500,000 pageviews a month pooled across them, so a busy shop and a quiet brochure site draw from the same allowance. Studio also includes 5 team members and a 1-year consent log. See ConsentLayer plans.

CookieYes

A client site that serves AdSense ads in the EEA gets a Google-certified CMP with IAB TCF from CookieYes, which lists itself as a Google Certified CMP and as an IAB TCF Certified CMP on all plans. The tier you need depends on the client, so read the plan grid before you buy:

  • The IAB TCF v2.4 Framework feature is on Pro and Ultimate only.
  • Global Privacy Control is on Pro and Ultimate, not on Free or Basic.
  • Google Consent Mode v2 is on all plans, so an advertiser client can stay on a lower tier.

If you run several publisher clients, budget for Pro on each one, since that’s where the framework feature lives.

Cookiebot

Picture a client with a small brochure site who adds a large blog: Cookiebot prices Premium by subpages, not by page views or usage, so the plan moves up because the site grew, even when traffic stays flat.

That client keeps a Google Consent Mode integration that adjusts Google tags based on consent choices, and Global Privacy Control on both Free and Premium. If that client later adds AdSense, the IAB TCF 2.4 Framework is on Premium, not on Free.

iubenda

A publisher client gets a Google-certified CMP Partner from iubenda, with IAB-validated TCF 2.2 support. Against CookieYes, the deciding factor for that client is how many pageviews the site serves, because iubenda prices per site, per month, with pageview quotas and overage charged per 1,000 pageviews. Google Consent Mode v2 support is on every iubenda plan, free included, which lets an advertiser client start without paying.

Termly

The free plan stops at one site and 10,000 banner views a month, which fits a test site more than a client roster. It also allows one user, runs cookie scans quarterly, and keeps the Termly logo on the banner. Run these checks before you move a client onto a paid Termly plan:

  1. Count the sites: Termly sells a subscription per website in tiers, and the bulk licensing or custom Agency plans are the route for a roster.
  2. Confirm the tier for a publisher client. Termly’s IAB TCF 2.3 support is on Pro+ and Agency.
  3. Look for the Google CMP Partner Badge that Termly shows if the client’s ad partner asks for a Google partner.

Google consent platforms side by side

Compare the five on how the price grows with your roster, what they do with Google Consent Mode, and where IAB TCF sits.

PlatformPrice modelGoogle Consent ModeIAB TCF
ConsentLayerStudio: $29 a month for 10 sites and 500,000 pooled pageviewsConsent Mode v2 on all plansNo IAB TCF support
CookieYesPer domain, tiers tied to pageviews, overage beyond limitsConsent Mode v2 on all plansIAB TCF Certified CMP on all plans; TCF v2.4 Framework on Pro and Ultimate
CookiebotPremium priced by domains and subpages per domainIntegrates with Google Consent Mode to adjust Google tagsIAB TCF 2.4 Framework on Premium, not on Free
iubendaPer site, per month, overage per 1,000 pageviewsConsent Mode v2 support on all plans, including freeIAB-validated CMP with TCF 2.2 support
TermlyPer website in tiers, plus bulk and Agency plansConsent Mode v2 with Basic and Advanced modes by tierIAB TCF 2.3 on Pro+ and Agency

Questions builders ask about Google consent platforms

Can I use a free CMP for Google Consent Mode?

You can on a small site, though free limits run out fast on client work. CookieYes Free allows 5,000 pageviews a month, 100 pages per scan, 5 scans a month, and one free plan per account. Cookiebot Free covers one domain, up to 50 subpages, one language, and manual blocking, which means you mark scripts yourself.

What is the difference between basic and advanced Consent Mode?

In basic mode, Google tags wait until the visitor consents, so nothing reaches Google from someone who declines. Advanced mode loads tags in a denied state, and they send cookieless pings that Google uses to model lost conversions. Termly lists Basic and Advanced modes by plan tier, so a lower tier may give you only one.

Does Google Tag Manager need its own consent setup?

Yes, for any tag in the container that isn’t a Google tag. ConsentLayer pushes a consentlayer_consent_update dataLayer event after each choice, so you can build a GTM trigger on it and fire a LinkedIn Insight or TikTok tag only after the visitor agrees. Google’s own tags read the Consent Mode state directly.

My site does not use cookies. Does it still need a CMP?

Probably, because embedded YouTube videos, reCAPTCHA, and Google Fonts send visitor data to third parties without a cookie of your own. ConsentLayer’s scanner checks up to 10 URLs per scan and matches what it finds against its service library, so you see what the site loads before you decide.

Set up Google Consent Mode v2 on a client site with ConsentLayer

1. Run setup from your agent or the dashboard

Setup works in two ways: by one prompt in the AI you already use, or from the dashboard at app.consentlayer.com. Connect ConsentLayer to your agent (you sign in through your browser), then send this prompt, with the placeholder replaced by the domain of the site you’re setting up, your own or a client’s:

Set up ConsentLayer on <your-domain> with Google Consent Mode v2

Your agent calls setup_site. That one tool call creates the site and scans it. It also configures consent categories and returns the ConsentLayer tag with a real project key. Without an agent, sign in at app.consentlayer.com and add the site from the dashboard. The dashboard then gives you the tag to copy.

2. Put the tag first in the head

Paste the tag into <head> on every page, above Google Tag Manager, gtag.js, and every other script. It must load synchronously, with no defer and no async. On WordPress, watch for a performance plugin that adds defer to every script or moves scripts to the footer. Exclude the ConsentLayer tag from that setting.

3. Check the tag on the live site

After you deploy, send your agent this prompt, again with your own domain in place of the placeholder:

Check the ConsentLayer installation on <your-domain>

The check_installation tool fetches the live homepage and confirms the tag is in <head> without defer or async. The compliance score rates the site from 0 to 100 and names the open items. Run it against the real domain rather than staging, because a site is protected only when the tag is live in <head> there, blocking is on, and decisions are recorded.

4. See what Google receives after a choice

Accept only statistics on the banner, then type dataLayer in the console and read the latest entry that holds consent and update. ConsentLayer maps its categories to Consent Mode signals like this:

ConsentLayer categoryConsent Mode signals
Essentialfunctionality_storage, security_storage
Statisticsanalytics_storage
Marketingad_storage, ad_user_data, ad_personalization

After that choice, analytics_storage should read granted while the three ad signals stay denied, which is the state GA4 and Google Ads act on. For more detail, read about Google Consent Mode v2 on client sites.

Set up Google Consent Mode v2 on your first client site free, with no credit card: create your ConsentLayer account.