C cenaly.ru
Start free

Free banner · consent settings

Set up your cookie banner and tracker controls

Visitors choose categories and can change their decision. The banner passes choices to analytics and advertising tags; strict opt-in blocks known trackers until consent.

The banner is free; it needs the first synchronous tag before analytics. Automatic scanning and a consent log are unavailable here; region is estimated from the time zone.

  • Four categories and settings that can be reopened
  • Google Consent Mode v2 and vendor signals
  • Start modes configured by your rules
A bakery website with the cookie banner at the bottom: equally sized “Accept”, “Decline” and “Customize” buttons
View full size
Settings in your accountEnable the widgets you needTest on your own website

What the guest sees — and what appears on your side

Guest screen

A compact cookie banner on a phone: a short message and three choice buttons

In your dashboard

Where the data goes The visitor’s choice is remembered in their browser; banner settings and the cookie list stay in your account

categories: necessary, preferences, statistics and marketing
4
per-region modes, from strict opt-in to a simple notice
5
languages supported; a language pack is required, otherwise English is used
45
for the banner, known-tracker blocking in opt-in and Consent Mode v2
0 ₽

How it works — for the visitor and for you

  1. 1

    Your configured mode loads

    In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site. For blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.

  2. 2

    They see the banner of their region

    Region is estimated from the browser time zone, without IP country detection. The estimate is imprecise; choose a conservative mode and check your rules.

  3. 3

    They choose categories

    Opt-in offers acceptance, rejection or category selection. In opt-out, GPC/DNT automatically rejects marketing; not every mode requires a prior decision.

  4. 4

    The decision is applied and remembered

    Allowed scripts start, cookies of rejected categories are cleaned up, Google, Meta and Microsoft receive consent signals, and the choice is remembered in the visitor’s browser.

Set up in three steps

1

Create an account and add your site

Signup opens setup for the selected product. Have your domain and permission to insert code ready.

2

Configure and install

Follow your platform instructions. Blocking trackers before consent requires the early CMP script, not just the shared async tag.

3

Test your published site

Enable the widget and try the visitor action on the published page. Settings may appear after the cache refreshes.

The tag

<script src="https://cdn.cenaly.ru/site/v1.js" data-domain="your-site.com" async></script>

Shared widget tag. See the separate CMP instructions for blocking trackers before consent.

What the cookie banner takes off your hands

Block trackers instead of just warning about them

In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site. For blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.

Ask by the rules of the region

Region is estimated from the browser time zone, without IP country detection. The estimate is imprecise; choose a conservative mode and check your rules.

Pass the visitor’s choice to your analytics

Consent Mode v2, GTM dataLayer events and UET, Meta and Clarity signals are sent. Tags must be configured to handle them; sending a signal does not verify your advertising-account setup.

Show the cookie list in your policy

You list your site’s cookies in the dashboard — name, category, provider, purpose and expiry — and a live declaration table embeds into your policy with a single container and localises itself. Change the list and the table on your site updates without editing the page. Best if your declaration still sits in the policy as plain text.

Let visitors change their decision

Visitors can reopen settings and change their choice. A new prompt can appear after a policy-version change, choice expiry or browser-data clearing.

Where it pays off

Visitors from the EU and the UK

In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site.

A site with Google Analytics and ads

Consent Mode v2 passes the consent state to vendors — the visitor’s choice reaches your tags instead of staying inside the banner.

Embedded video and maps

In blocking mode, supported videos and maps can be replaced by a settings placeholder. Test each source your site uses.

A site on WordPress

The plugin installs the banner without touching your theme; linked to your account the site behaves like an ordinary location.

Alcohol and 18+ products

An age question can precede the banner. It is the visitor’s own answer, not identity or document-based age verification, and does not permit restricted-product sales.

What it looks like in the product

  • Choosing categories

    Cookie settings on a phone: necessary always on, preferences and statistics on, marketing off
    The visitor turns on only the categories they want

How it works in practice

  • A visitor in a café picks cookie categories on a bakery website on a phone
    Illustration. The visitor’s choice is applied and recorded in the consent log

How it looks on your site

Example interface. Customise colours, position and labels, then check your page on desktop and mobile.

On desktop

On mobile

On your side: Example of opt-in with correct installation before trackers. Other modes behave differently. For blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.

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 banner is free: known-tracker blocking in opt-in, four categories, per-region modes, Consent Mode v2 and the cookie declaration
  • On sites built with our website builder the banner is enabled from the start
  • We charge nothing per visitor, per domain or per banner view

What is included and what costs extra

Basic versions of 9 of the 13 widgets are free. Table booking, popups, help and legal pages on external sites are extensions. Connected services can cost extra.

Set up consent

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 ✓ In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site.
Visitor’s region ✕ The same banner is shown to the entire world ✓ Region is estimated from the browser time zone, without IP country detection. The estimate is imprecise; choose a conservative mode and check your rules.
Consent signals ✕ The visitor’s choice stays inside the strip: no tag or vendor is told about it ✓ Consent Mode v2, the dataLayer event for GTM, UET, Meta Pixel and Clarity all receive the consent state
Cookie list ✕ The cookie list in the policy was typed by hand a long time ago ✓ The cookie list is kept in your dashboard, and the live table in your policy updates itself

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 blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.
  • 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.
  • Your site is not scanned automatically: you compile the cookie list for the declaration yourself in the dashboard.
  • 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 (English, Russian, Georgian, Turkish) with your own wording per language; a refusal is deliberately not remembered, so a reload asks again.
  • In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site.
  • A scan reports what it found on scanned pages and in tested states. It does not prove that other trackers are absent; manually check dynamic elements, category settings and results.
  • Consent Mode v2 is a signal interface, not a claim of CMP certification or advertising-platform approval. Check the chosen platform’s requirements separately.
  • An age question can precede the banner. It is the visitor’s own answer, not identity or document-based age verification, and does not permit restricted-product sales.
  • There is no consent log: the visitor’s choice is remembered in their browser, and the dashboard neither shows nor exports a history of decisions.

Who it's for

  • Sites with visitors from the EU and the UK
  • Anyone running Google Analytics, Ads, Meta Pixel or Clarity
  • Sites on WordPress — installed with the plugin, without touching the theme

What the cookie banner does and how to check it

In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site.

The banner helps manage categories and pass choices to connected tags. The required legal mode depends on your site and visitors; settings do not replace a legal assessment.

The banner, categories, Consent Mode v2 and manual cookie declaration are free. Automatic scanning and a history log are not available here. In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site.

The public website check reads one page’s HTML, does not run JavaScript and does not prove correct blocking. After installation, test accept, reject, reopening and network requests in a browser.

Questions and answers

What does the free banner include?

A banner in 45 languages, known-tracker blocking in opt-in, four categories and a preference centre, per-region modes, Google Consent Mode v2 and a cookie declaration for your policy.

Does it really block trackers?

In strict opt-in, known trackers and manually marked scripts wait for consent. Opt-out and other modes apply different start rules. Configure and test the mode on your site. For blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.

Is it compatible with Google Tag Manager?

Consent Mode v2, GTM dataLayer events and UET, Meta and Clarity signals are sent. Tags must be configured to handle them; sending a signal does not verify your advertising-account setup.

Do I need a banner outside the EU?

The widget lets you configure modes and text for audiences, including Russia. It does not automatically determine whether data processing is lawful; check your site’s terms and selected mode.

How do I switch on the 18+ age gate?

In a separate section of the same widget’s panel: a threshold of 18 or 21, confirmation buttons or a birth-year field, memory from 1 to 365 days (30 by default). The birth year is never stored anywhere, and a refusal is deliberately not remembered. An age question can precede the banner. It is the visitor’s own answer, not identity or document-based age verification, and does not permit restricted-product sales.

How do I install it?

For blocking before consent, put the separate consent tag first in head, without async or defer, before analytics. It cannot stop scripts already executed, server Set-Cookie or service workers.A WordPress plugin is available. A consent log is not available here, whether standalone or dashboard-linked.

Will the banner slow my site down?

The synchronous tag enables early interception, so loading affects the first screen. Configuration, language packs and an enabled age gate need additional files. Test network use and speed on your site; neither a fixed size nor zero load after a decision is guaranteed.

What do I need to install it?

An account, your website domain and permission to insert code. Prepare the selected widget’s data and test your published page. Follow the separate cookie banner instructions for early tracker blocking.

Will it work on my page?

Style isolation reduces conflicts but does not replace testing. Check buttons, forms, mobile layout and other scripts on your site.

What about languages and data?

Set your own texts separately; built-in labels fall back to English where translations are missing. Core data is stored in the brand’s cloud. Connected AI, telephony and other services have separate processing terms.

Check your site for trackers and a cookie banner →

More — installation per platform, settings and troubleshooting — in the help center. Installation guide →

Set up the banner and test tracker behaviour

After signup, choose categories and mode, then install the tag before trackers. Test accept, reject and reopening on the published site.

Set up consent

No card required · free · Consent Mode v2 included