Free · blocks trackers before consent
Collect cookie consent that actually means something
Not just a “we use cookies” strip: analytics and advertising scripts do not run until the visitor agrees. Categories, a preference centre, per-region modes, Google Consent Mode v2 and a consent log — all in the free tier. Built for sites with EU visitors and any analytics on board.
- Trackers and embedded videos are blocked until consent is given
- Per-region behaviour: opt-in, opt-out, soft, notice or hidden
- Google Consent Mode v2 out of the box — analytics keeps its signal
No card. A minute to sign up, another for the tag.
- categories: necessary, preferences, statistics and marketing
- 4
- per-region modes, from strict opt-in to a simple notice
- 5
- languages: the page language arrives as a language pack
- 45
- for the base tier: banner, blocking, Consent Mode and the log
- $0
How it works — for the visitor and for you
- 1
A visitor opens the site and trackers stay quiet
Scripts on the block list are neutralised, cookie writes are buffered, and embedded videos and maps are replaced with a localised placeholder that opens the settings.
- 2
They see the banner of their region
In the EU everything is denied until consent by default; elsewhere your rule applies — opt-out, soft, notice, or a hidden banner with a settings link.
- 3
They choose categories
“Accept all”, “Reject” or the preference centre with four categories. GPC and Do Not Track signals are honoured automatically, and toggles are never pre-ticked.
- 4
The decision is applied and logged
Allowed scripts start, rejected cookies are cleaned up, Google, Meta and Microsoft receive consent signals, and the decision goes into an anonymous log.
Set up in three steps
Sign up and add your site
A free Cenaly.ru account and your site domain in the "My website" section.
Paste one tag
One line before </body> — in your theme, in a Tilda or Wix HTML block, in Shopify's theme.liquid. It serves every widget.
Switch widgets on in the admin
Each widget is a toggle and a settings form. Changes reach your site without touching code; CDN cache is five minutes.
The tag
<script src="https://cdn.cenaly.ru/site/v1.js" data-domain="your-site.com" async></script>One tag for all widgets. `data-domain` is your site; everything else lives in the admin.
What the cookie banner does
Block trackers instead of just warning about them
The engine installs before the config loads: it intercepts cookie writes, neutralises scripts from the block list, replaces embedded videos and maps with placeholders and supports manual `type="text/plain"` markup. After consent the scripts are re-injected. Best for anyone required to ask first, not after.
Ask by the rules of the region
The country is resolved by IP, then your rule applies: opt-in for the EU, opt-out where that is the norm, a soft mode, a notice, or a hidden banner. GPC and Do Not Track are handled automatically. Best for sites with visitors from several countries.
Keep your analytics data
Google Consent Mode v2 with proper wait-for-update, a named dataLayer event for GTM, Microsoft UET, Meta Pixel and Clarity — vendors receive signals instead of silence. Best for anyone measuring conversions.
Show the real cookie list
A monthly scan finds which cookies and trackers your site actually loads, and a live declaration table embeds into your policy with a single container and localises itself. Best if your declaration was written by hand a year ago.
Keep the evidence
An anonymous consent log: what the visitor chose and when, without IP or full user agent. A floating button and a `#cenaly-consent` link let them change their mind at any time. Best for the day someone asks.
Add an 18+ age gate where it belongs
A separate section: a threshold of 18 or 21, confirmation buttons or a birth-year field, memory for up to 365 days. The birth year is never stored, a refusal is never remembered, and the gate stands before the banner. Best for alcohol, tobacco and adult products.
Where it pays off
Visitors from the EU and the UK
Strict opt-in: analytics and advertising wait for consent instead of starting with the page.
A site with Google Analytics and ads
Consent Mode v2 preserves conversion modelling where the visitor said no, instead of losing the data entirely.
Several markets, one site
A visitor from the EU sees a question; a visitor from an opt-out region sees a notice and a “do not sell my data” link.
Embedded video and maps
Before consent their place is taken by a clear placeholder with a settings button, not an empty rectangle.
A cookie declaration in your policy
The live table inside the policy updates from the scan results instead of being rewritten by hand.
Alcohol and 18+ products
The age gate asks first, and only after it does the cookie question appear.
How it looks on your site
Colour, position and labels adapt to your site. The widget lives in a Shadow DOM — your styles don't break it, and it doesn't break yours.
On desktop
On mobile
Where it goes
Exact menu names and plan requirements, taken from each platform’s own help center.
Sites built with our website builder ship with the widgets already wired — nothing to paste.
Step-by-step guides per platform — in the help center →Pricing
Free
Free on sites built with our website builder
- The base tier is free: banner, auto-blocking, Consent Mode v2 and the log
- Free tier includes a monthly scan of 10 pages and a 3-month consent log
- The Pro add-on lifts the limits: weekly scans of up to 30 pages and a 12-month log
- On sites built with our website builder the banner is enabled from the start
Why free
Widgets are the door into the Cenaly.ru platform: requests, chats and orders from your site land in the same admin as everything else, and some owners later buy extensions. We charge nothing per visitor, request or site; only products with our own running costs stay paid.
With and without
| Without the widget | With the widget | |
|---|---|---|
| When trackers start | ✕ The strip is there, but analytics and ads start along with the page | ✓ Scripts on the block list don’t run until the visitor agrees |
| Visitor’s region | ✕ The same banner is shown to the entire world | ✓ The mode follows the country: opt-in, opt-out, soft, notice or hidden |
| Analytics data | ✕ A refusal means losing the data in analytics completely | ✓ Google Consent Mode v2 passes the consent state instead of staying silent |
| Cookie list | ✕ The cookie list in the policy was typed by hand a long time ago | ✓ A monthly scan shows which cookies your site really loads |
| Evidence | ✕ There is nothing to show that consent was ever collected | ✓ An anonymous consent log keeps the decision and its timestamp |
Honest about the limits
- Not intercepted: cookies set by your server via Set-Cookie, scripts that already ran before our tag, and service workers.
- For strict prior consent the tag goes first in `<head>`: the shared loader starts the banner first, but it cannot outrun analytics hard-coded above it.
- If the config is unreachable, the page is excluded or the banner is off, blocking is lifted entirely: we will not keep your site blocked because of a failure on our side.
- Free tier: a monthly scan of 10 pages and a 3-month consent log. Beyond that it is the Pro add-on.
- This is not legal advice: the regional mode and the wording are your decisions, and edge cases are worth discussing with a lawyer.
- The age gate speaks four languages (en, ru, ka, tr) with your own wording per language; a refusal is deliberately not remembered, so a reload asks again.
Who it's for
- Sites with visitors from the EU and the UK
- Anyone running Google Analytics, Ads, Meta Pixel or Clarity
- Sites built with our website builder — the banner is on there already
What a cookie banner is and when it is mandatory
A cookie banner is not a “we use cookies” strip but a consent mechanism: it has to ask before analytics and advertising start counting the visitor, and to remember the answer. Legally the order is what matters — question first, trackers second.
You need one if you have visitors from the EU or the UK and your site loads anything beyond strictly necessary cookies: counters, pixels, embedded videos and maps. Other regions work differently — in some, a notice and a way to opt out is enough.
Our banner is free in its base tier and does the real work: it blocks scripts and cookies until the visitor decides, passes consent to Google Consent Mode v2 and other vendors, shows the actual cookie list from a scan and keeps an anonymous log of decisions. The 18+ age gate lives in the same widget and stands in front of the banner.
Questions and answers
What is included in the free tier?
A banner in 45 languages, tracker auto-blocking, four categories and a preference centre, per-region modes, Google Consent Mode v2, a monthly scan of 10 pages and a 3-month consent log. The Pro add-on lifts the limits: weekly scans of up to 30 pages and a 12-month log.
Does it really block trackers?
Yes: the engine installs before the config loads, prevents scripts on the block list from executing, buffers cookie writes and swaps embedded videos and maps for a placeholder. After consent the scripts are started again.
Is it compatible with Google Tag Manager?
Yes, through Consent Mode v2: tags in GTM react to the consent signals, and a named event is pushed into the dataLayer. Microsoft UET, Meta Pixel and Clarity are supported separately.
Will I lose analytics data because of refusals?
Less than with simply switching tags off: Consent Mode v2 passes the consent state and Google keeps receiving cookieless signals. Rejected categories genuinely write nothing.
Do I need a banner outside the EU?
It depends on the region: some require consent, others accept a notice with a way to opt out. The mode is chosen per region in the settings, and borderline cases are worth discussing with a lawyer.
What does the consent log contain?
The categories the visitor chose and the time of the decision — anonymously, without IP or full user agent. That is enough to show that consent was collected and how it worked.
How do I switch on the 18+ age gate?
In a separate section of the same widget panel: a threshold of 18 or 21, confirmation buttons or a birth-year field, memory for up to 365 days. The birth year is never stored and a refusal is deliberately not remembered.
How do I install it?
With the shared “My website” tag the banner loads first. For strict prior consent, place the consent tag itself as the first line in `<head>`, above any third-party analytics. WordPress has its own plugin with one-click connection.
Will it slow my site down?
The loader is one small `async` script; widgets load as separate bundles and only the ones you switched on. Nothing blocks page rendering.
Will it break my layout?
No. Widgets render inside a Shadow DOM: your site's CSS doesn't affect them and theirs doesn't leak out.
Which language will the widget speak?
It reads your page's `<html lang>` or a `data-lang` attribute on the tag. Built-in labels are translated into 45 languages; your own texts you write in the admin in the languages you need.
Where is the data stored?
In the cloud your account lives in: cenaly.com — AWS, cenaly.ru — Yandex Cloud in Russia. Requests, conversations and bookings stay within the brand's contour.
More — installation per platform, settings and troubleshooting — in the help center. Installation guide →
Works together with
All 12 widgets →Legal pages
Privacy, terms, returns, cookies, delivery — generated and embedded
Add-on, price in the catalogue
Help centre
A “?” button → a side panel with your articles, search and feedback
Add-on, price in the catalogue
Popups and forms
Modals, slide-ins, bars and lead forms with triggers and A/B testing
Add-on, price in the catalogue
Put up a banner that does the work, not the look
Free. One tag, the “Consent” toggle — and trackers wait for the visitor’s decision while you keep the log.
Start for freeNo card required · base tier is free · Consent Mode v2 included