ConsentLab features: everything a 2026 CMP needs

1. Native Google Consent Mode v2

Since March 2024, Google Ads and Analytics 4 require ad_storage, analytics_storage, ad_user_data and ad_personalization signals via the gtag('consent', …) function. Without Consent Mode v2, your Google Ads campaigns lose up to 60% of their conversion attribution capability for users who refused cookies.

ConsentLab implements Consent Mode v2 natively: as soon as a visitor clicks Accept, Refuse, or Customize, the right signals fire to Google without you having to touch a single line in your Tag Manager. The Advanced mode is enabled by default — Google can model the conversions of refusing users and recover most of the lost tracking.

For the full deep dive: our complete guide to Google Consent Mode v2.

2. Third-party script auto-blocking

The CNIL rule is unambiguous: no script that may drop a non-essential cookie can run before the visitor's active consent. Concretely, Google Analytics, Meta Pixel, TikTok, LinkedIn Insight Tag, Hotjar and 200+ other services must be blocked until the user makes their choice — and unblocked individually based on the accepted purposes.

ConsentLab automatically intercepts <script>, <iframe> and <img>tags identified as tracking in an internally maintained database. Each resource is mapped to a purpose (analytics, marketing, functional) and only loads if the visitor consented to that specific purpose. You literally don't change a line of source code.

3. Customizable branding

A cookie banner isn't a necessary evil: it's a direct touchpoint with your visitor, literally appearing on every page. Visual coherence with your brand sends a signal of seriousness and trust — whereas a generic "Powered by Cookiebot" banner actively hurts your credibility.

With ConsentLab, you customize primary and secondary colors, typography (system or Google Fonts), corner radius, button copy, position (bottom, top, centered modal, floating button), dark mode, and even your logo. Everything is editable from your dashboard with zero code.

4. Exportable consent proof (CNIL audit trail)

In case of a CNIL audit or a GDPR request from a visitor (article 7.1 GDPR), you must be able to prove consent: who consented, to what, when, and with which version of your policy. Without an audit trail, you are non-compliant — CNIL has already fined companies on that single motive.

Every interaction on the ConsentLab banner generates a signed record (SHA-256 hash) with: timestamp, anonymized IP, user-agent, accepted and refused purposes, policy version, session ID. You export everything in CSV on demand, filtered by period or by domain. 13-month retention, exactly as the CNIL requires.