Choosing a Consent Management Solution for Client Sites

Choosing a Consent Management Solution for Client Sites

A builder who runs client sites should pick ConsentLayer. Its Studio plan covers 10 sites for $29 a month with pageviews pooled across them, and the banner holds known trackers until the visitor chooses. An owner of one site can start on ConsentLayer’s Free plan when the visitors fall under GDPR, CCPA/CPRA, or LGPD. ConsentLayer has no IAB TCF support, so one ad-funded site that needs TCF is better on CookieYes Pro or Ultimate, or Cookiebot Premium.

What a consent management solution does on a client site

On a client site, a consent management solution sits between the visitor and every analytics, ad, and chat script that you or the client’s marketer added. It decides which of them may run before the visitor answers the banner. The solution shows the banner in the visitor’s language and stores the answer in a first-party cookie. Then it passes that answer to tags that read it, such as Google Analytics 4 and Google Ads through Google Consent Mode v2.

A good solution also listens to the browser for a Global Privacy Control signal. When a visitor’s browser sends one, the solution can treat the visit as an opt-out of sale and sharing without waiting for a click, and that matters for visitors from US states that recognize the signal.

The third job is the record, a log of each decision with enough detail that the client can show a regulator or a customer what that visitor agreed to and when.

A builder with many brochure and small shop sites needs one bill that covers many domains and an install that drops into each stack, while a publisher who sells programmatic ads needs IAB TCF so ad partners can read the visitor’s choice.

What to look for in a consent management solution

Test each candidate on a real client site, whether you’re choosing a consent management platform for client sites or replacing one a client already pays for.

Trackers that wait for the visitor’s choice

A banner that appears while Google Analytics and the Meta pixel already load protects nobody. Run this check before you trust any demo:

  1. Open the client site in a private window, because your own stored consent cookie hides the banner and skews the result.
  2. Open DevTools on the Network tab and tick “Preserve log” so redirects don’t clear the list.
  3. Load the page and leave the banner alone, without scrolling or clicking anywhere on it.
  4. Filter the requests for collect, facebook, doubleclick, and hotjar, then look in Application, Cookies for _ga or _fbp.
  5. Click “Reject all”. Reload and repeat the filter.

A held tracker sends nothing and sets no cookie until step 5 says yes. With ConsentLayer, the list stays empty in step 4, and the held scripts run only after the visitor consents. One result confuses people the first time they see it. With Consent Mode in advanced mode, GA4 still sends a collect request before consent, but that request is a cookieless ping that carries gcs=G100 and sets no cookie.

The price at your full roster of sites

Picture the day you add the tenth client site. With CookieYes, pricing is per domain and each additional domain needs its own paid plan, so ten clients means ten plans.

On ConsentLayer Studio, the same ten sites sit on one plan for $29 a month, with 500,000 pageviews a month pooled across them, 5 team members, and a 1-year consent log. Pooling matters more than the site count, since one busy shop and nine quiet brochure sites share the allowance and the quiet sites never waste theirs. Check the numbers for your own roster on ConsentLayer pricing before you quote a client a monthly fee.

The laws your clients’ visitors bring with them

Write down where each client’s visitors come from instead of where the client is based. A Texas bakery with a busy Instagram following still gets visitors from Germany and Brazil. GDPR and Brazil’s LGPD need opt-in, where nothing non-essential runs until the visitor agrees. CCPA/CPRA allows opt-out, where tracking may start but the visitor must be able to refuse the sale or sharing of their data.

Then check that the solution has a template for each of those laws and shows the right one by the visitor’s location. ConsentLayer covers GDPR, CCPA/CPRA, and LGPD. CookieYes includes a GDPR template (opt-in) and a US State Laws template (opt-out) on all plans.

Google Consent Mode v2 and Global Privacy Control

When a visitor declines, Google Ads and GA4 should receive ad_storage, analytics_storage, ad_user_data, and ad_personalization set to denied. If they receive nothing, a client running Google Ads loses remarketing audiences and conversion modeling. A browser that sends Global Privacy Control (the Sec-GPC: 1 header, also readable as navigator.globalPrivacyControl) should count as an opt-out before the visitor clicks anything.

  • ConsentLayer sends Google Consent Mode v2 and honors Global Privacy Control by default, on Free and on each paid plan.
  • CookieYes has Global Privacy Control on Pro and Ultimate only, so a client on Free or Basic gets no GPC handling.
  • To test GPC, turn on the setting in Brave or install a GPC browser extension. Then load the site and confirm that the “sale or sharing” category starts off.

Setup steps for both signals are in set up Google Consent Mode v2 on client sites and the guide to Global Privacy Control.

An install that fits the stacks you build on

Before you commit, know what you’ll paste on each kind of site you build. A WordPress site takes the snippet in a different place from a Webflow site or a hand-built Next.js app.

ProductWhat you install and where
ConsentLayerOne snippet in <head>, before other scripts, with no defer or async
CookiebotBanner code pasted into the site header, or its WordPress plugin, Google Tag Manager, or a CMS integration
TermlyA WordPress plugin that installs and manages consent on WordPress sites

A caching or minify plugin that adds defer to every script also rewrites the consent snippet. Exclude the snippet by name in that plugin’s settings, or trackers load before the banner does.

Proof you can show the client

Sooner or later a client forwards an email that asks, “What did this visitor agree to, and when?”, and the answer has to come from the log rather than a screenshot of today’s banner.

In ConsentLayer, each consent log record holds the visitor ID, country, jurisdiction, categories, per-service decisions, GPC and Do Not Sell flags, consent version, anonymized IP, user agent, locale, template, geo group, and a link to a snapshot of the banner version the visitor saw. Banner text changes over time, so clients value the snapshot link most: it shows the exact wording the visitor answered.

The consent management solutions worth comparing

ConsentLayer

You set up each client site with one prompt to the AI you already use, or from the dashboard at app.consentlayer.com, and both routes end at the same configured site. It fits a roster of many small sites, where setup takes one prompt per site and nothing is configured twice.

Cookiebot

Your bill grows with each domain and with the number of subpages on each one, since Cookiebot’s plans “are based on the number of domains you have and the number of subpages within each domain.”

  • A client blog that publishes weekly keeps adding subpages, so the price can climb a tier without a single new site.
  • GDPR, CCPA/CPRA, VCDPA, LGPD, and POPIA appear in its supported legislation frameworks on both Free and Premium.
  • Choose it for one large site with ad-tech partners, where the subpage pricing is a known cost and the law list is wide.

CookieYes

Say you put a new client on the free plan to start. It gives 5,000 pageviews a month, 100 pages per scan, and 5 cookie scans a month. Only one free plan is allowed per account, so the second client already needs a paid plan. That limit makes the free plan useful for your own portfolio site or a test site, while client work moves to per-domain paid plans from the start.

Termly

Each Termly plan includes one website, so every extra client website needs its own license. Additional sites are pay per license, with a bulk discount from 5 licenses and a custom-priced Agency plan.

  • Termly says its products “are designed to cover 28 different data privacy laws”, including GDPR, UK GDPR, PIPEDA, CCPA, and CalOPPA, which suits a client with Canadian visitors.
  • Consent Mode v2 comes as a basic version on Free and Starter and an advanced version on Pro+ and Agency, so a client who runs Google Ads should be on Pro+.

OneTrust

You get a price through a demo or a sales call. The consent management product page shows no price, only “Request Demo”, “Contact Sales”, and “Talk to Sales”. Its consent receipts support GDPR, CCPA, and CPRA. A sales cycle per client site is slow for a builder, so OneTrust makes sense when the client’s legal team already runs it across the company and asks you to install it.

Consent management solutions side by side

For a client on a free plan who needs both signals, ConsentLayer and Cookiebot send both, while CookieYes sends only Consent Mode v2.

ProductGoogle Consent Mode v2Global Privacy Control
ConsentLayerEvery plan, including FreeHonored by default on every plan
CookiebotFree and PremiumSupported integration on Free and Premium
CookieYesAll plansPro and Ultimate only
ProductIAB TCF
ConsentLayerNo support on any plan
CookiebotTCF 2.4 on Premium only
CookieYesTCF v2.4 on Pro and Ultimate
TermlyTCF 2.3 on Pro+ and Agency

Questions builders ask about consent management solutions

Is there a free consent management solution?

Several do, Cookiebot and Termly among them. Cookiebot’s free plan covers one domain, up to 50 subpages, one language, and consent record keeping for up to 12 months. Termly’s free plan includes 1 basic legal policy, 10,000 banner views per month, quarterly cookie scans, and 1 user.

How long does a visitor’s consent last before the banner asks again?

Each solution sets its own expiry, and Cookiebot’s free plan sets user consent expiration of up to 1 month. A returning visitor there sees the banner again within a month of answering it.

Can a consent management solution block every tracker on a site?

It blocks only the scripts it recognizes, and in ConsentLayer a script the library does not recognize goes to a review queue, where you approve it with a category and a blocking rule, or dismiss it. Check that queue after a client’s marketer adds a new pixel.

Will a consent management solution make a client’s site compliant?

A solution checks only the technical setup. ConsentLayer’s compliance score measures only that setup, so the client’s privacy policy and legal advice still decide whether the site meets the law.

Setting up ConsentLayer on a client site

Set up the site with one prompt

Send your agent this prompt, and replace the placeholder with the domain of the site you are setting up, your own or a client’s:

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

Your agent calls setup_site, one tool call that creates and scans the site. It also configures consent categories and returns the snippet with a real project key. Paste that snippet into <head> on every page, before other scripts, and deploy.

The dashboard gives you the same snippet to copy.

Check that the tag is live

After the deploy reaches the live domain, send your agent a second prompt:

Check the ConsentLayer installation on <your-domain>.

check_installation fetches the live homepage and confirms the snippet is in <head> without defer or async. It then reports a score out of 100 and names the open items. Last, rerun the private-window Network test: the client site is protected once the snippet is live on the real domain with blocking on and decisions recorded.

Set up your first client site free and see trackers wait for consent.