CF Consent, the cookie banner done properly.
A lightweight consent manager, installed on your site, built on the Italian data protection authority's guidelines and integrated with Google Consent Mode v2. Before installing it, though, we check whether you really need a banner.
Having a banner is not the same as having one that works.
Many banners show the right buttons but let scripts run before the choice, hide the reject option behind a second panel or stop nothing when users change their mind. Others are external services that load scripts from third-party servers themselves. And often the banner would not even be needed: what makes it necessary is a video, a map or a font loaded from elsewhere.
The site first, then the banner.
- 01
Site review
We list what the site installs, who loads it and why: first-party cookies, embedded services, pixels, tags.
- 02
Remove what isn't needed
If the site can do without a banner, we tell you and show you how: minimised analytics, self-hosted fonts, videos and maps loaded on click.
- 03
Configuration
If a banner is needed, we tie every script and iframe to its category and adapt texts and look to the site.
- 04
Testing
We check on desktop and phone that nothing runs before consent, that rejecting really blocks and that withdrawal stops scripts already running.
The authority's rules, built into the code.
A single JavaScript file of about 8 KB compressed, with no external libraries, served from your site and not from third-party servers.
Sites that must ask for consent.
Sites running Google Ads or Meta
Pixels run only after consent. For returning visitors the consent already given applies straight away, before Google Tag Manager starts, so Analytics and Ads do not count it as a refusal.
Sites leaving Cookiebot
CF Consent recognises Cookiebot's markup and exposes the same JavaScript functions and events: in most cases the pages do not need to change.
WordPress sites and page builders
It also blocks elements added after the page loads, such as those from Divi and Elementor, and keeps scripts in order.
Sites that could do without
If your site does not need a banner we tell you, and help you remove it.
We use it on the sites we manage.
CF Consent comes from our work on clients' sites, where we needed a compliant, lightweight banner under our own control. Every version passes 67 automated checks in Chromium before it is installed. Whoever configures it also manages the site and the server, and answers if something goes wrong.
Before installing it.
Does my site need a banner?
Only if it uses non-essential cookies or tracking tools. We check before installing anything: on many brochure sites the banner can be removed.
Does it follow the Italian authority's guidelines?
Yes: the X closes without accepting, rejecting and accepting carry equal weight, the banner returns after 6 months or when the cookie policy changes, and choices can be changed at any time.
Does it work with Google Consent Mode v2?
Yes. It sets the defaults before any Google tag and updates them with every user choice.
Can we move from Cookiebot without rebuilding the site?
In most cases, yes. Only sites that block scripts through Cookiebot's GTM template or WordPress plugin need reconfiguring. Visitors will see the banner once more, because Cookiebot consent is not imported.