M masamenu.tr

Comparison · cookie banner and consent

Cookiebot or Masamenu.tr: a cookie banner for your website

Compare consent settings, installation and costs. The Masamenu.tr base banner is free; blocking before consent requires strict opt-in and correct installation. We do not claim certified CMP status.

The base banner is free. Scanner and log extension: $9/mo; AI classification costs extra.

Cookiebot page snapshots: 5 and 12 September 2026. These are not a current offer; check linked terms and certifications before choosing. www.cookiebot.com/en

  • Free base: banner, categories and Consent Mode v2
  • Scanner: 10 pages monthly; log: 3 months
  • Strict mode requires installation before trackers

One job, two paths

A guest from the EU opens your site for the first time, and the site runs analytics, a pixel and an embedded video. Here is what happens on each side — first through the guest's eyes, then through the owner's.

Through the guest's eyes

What the guest sees, and what has already happened to the trackers by then.

Vendor · Cookiebot

  • The homepage states 2.4M websites and apps, 8.8B monthly user consents and support for 47+ languages. source · 2026-09-12
  • The site scanner sits in the first screen: next to "Start free" there is "Scan website", and further down a separate "Is your website compliant?" block. source · 2026-09-05
  • Trust is built on stated ISO 27001 and ISO 27701, HIPAA readiness and Google-certified CMP status. source · 2026-09-12
  • Cookiebot is owned by Usercentrics, and the same 2.4M and 8.8B appear on its site as its own numbers. Worth remembering when reading any counter on a consent vendor's homepage. source · 2026-09-12

Us · Masamenu.tr

  • In strict opt-in, the engine delays known cookies, scripts and embeds matched by the block list or manual markup. Its tag must run first; unknown trackers may need a separate rule. This does not guarantee blocking all website code.
  • Five modes: opt-in, opt-out, soft, notice and hidden. Opt-out permits categories until refusal, so a before-consent promise does not apply to it. Country comes from IP with a time-zone estimate as fallback; check rules for your visitors.
  • There are four categories: necessary, preferences, statistics, marketing. In strict mode the toggles are not pre-selected, and GPC and Do Not Track signals are honoured automatically.
  • Labels speak the language of the page — 45 languages arrive as a pack rather than baked into the bundle.
  • With the optional notice setting enabled, a report containing only necessary cookies can change the first layer to a notice. A scan sees a limited set of pages and states; it does not prove other trackers are absent. Known trackers remain subject to the selected blocking mode.

Through the owner's eyes

What you configure it with, what you can evidence, and what stays in your hands.

Vendor · Cookiebot

  • The page is built as: first screen with "Start free" and the scanner → tier choice → three reasons (setup, automation, security) → G2 reviews → the "Is your website compliant?" scanner → three blocks on compliance, UX and control → three steps → a Consent Mode v2 course → articles. source · 2026-09-05
  • The price is not shown on the homepage: it lives on a separate pricing page, and free access is framed as a 14-day trial. source · 2026-09-05
  • On 12 September 2026 the tiers gained names — Solopreneur, Emerging Business, Advanced Business Enterprise — and a separate Cookie Banner Cost Calculator appeared in the footer. source · 2026-09-12

Us · Masamenu.tr

  • Settings are kept per location in the Cookies section: texts with per-language overrides, the policy link, the declaration, regional rules, appearance, button set and the categories shown in the first layer.
  • Consent travels to vendors instead of staying inside the banner: Google Consent Mode v2 with wait-for-update, a named dataLayer event for GTM, Microsoft UET, the Meta Pixel with grant/revoke and LDU, Microsoft Clarity. Cookies of refused categories are cleaned up after the decision.
  • The log records decisions without IP or an exact User-Agent. It stays in your account; an event record does not guarantee legally sufficient consent.
  • The cookie declaration table goes onto your policy page as a single container and is built from scan results — live, localised, with properly declined durations.
  • Free: scan up to 10 pages monthly, log for 3 months. The extension raises limits to 30 pages weekly and 12 months; it is not unlimited. AI classification is a separate paid step.
  • The WordPress plugin works standalone without an account or connects to a location by token. Standalone mode has no consent log or age gate.

How the banner connects to the rest of your work

Use the banner on its own for a website. Its settings and other widgets share an admin; assign someone to install it and check it after website changes.

A lost tag arrives as a card in the work chat

A weekly check looks for the loader in HTML. If a previously found tag disappears, work chat gets a card. It cannot see a tag added through GTM; tag presence does not prove trackers are blocked.

One tag for the banner and for everything else

The shared loader connects the widget family. Strict consent blocking needs a separate synchronous tag first in head, before analytics; the loader’s widget order is not sufficient.

The age gate lives in the same widget

An optional 18/21 screen accepts confirmation or a birth year. It appears before the banner but does not verify identity or documents; a loading failure skips it. It is absent in standalone WordPress mode.

On a site built with our builder the banner is already on

A new site from our builder enables consent, legal links and chat by default. Still check texts, mode and analytics order on the published page.

Checking someone's site needs no account

The public tool checks a specified page without registration. Its result helps with setup; it is not a whole-site audit or a legal compliance opinion.

Installation limits — on both sides

For a consent banner installation matters more than for any other widget: put it in the wrong place and "blocking before consent" stops being blocking.

What we compare Cookiebot Masamenu.tr
Where the tag goes Installation is presented as three steps plus a Consent Mode v2 course; no precise requirement for the tag's position in the markup appears on the captured pages. source · 2026-09-05 First script in the head, with no async and no defer. Through the shared loader consent is raised first among our widgets, but it will not outrun third-party analytics nailed higher in the head — for strict "before consent" the tag goes in separately and first.
Installing through Google Tag Manager Integration with Consent Mode v2 and tags is stated; a separate walkthrough of installing the banner itself through GTM does not appear on the captured pages. source · 2026-09-05 Technically it works, but there is little point: GTM loads asynchronously while the banner has to execute before third-party analytics. On top of that our install check never sees a GTM tag — it reads the markup rather than executing the page.
A single-page app Behaviour during navigation without a reload is not described on the captured pages. (not stated on the pages we captured) The banner is redrawn when changes — that is watched by an observer. The guest's decision is kept in the browser and survives transitions; excluded pages are set by path masks.
A site with Content-Security-Policy The captured pages carry no CSP requirements and no host list. (not stated on the pages we captured) The loader copies its nonce onto both the banner and the lazy age gate. Banner styles live in a Shadow DOM and need style-src 'unsafe-inline'. If the lazy gate does not arrive, there is no gate: keeping someone's site closed because of our own hiccup is not acceptable.
Limits of our blocking The limits of interception are not named on the captured pages. (not stated on the pages we captured) Server Set-Cookie, code executed before our tag and service workers are not intercepted. Check unknown trackers and loading order after theme or analytics changes.

An empty cell on the left describes our snapshot of the vendor's marketing pages: its documentation almost certainly says more. For a banner this is especially worth checking before you choose.

What gets metered: billing units

The Masamenu.tr banner is configured per account location. The extension raises scanner and log limits; AI costs are not included. Cookiebot terms below refer to the dated snapshot.

What we compare Cookiebot Masamenu.tr
The banner itself The price is not shown on the homepage and leads to a pricing page; free access is framed as a 14-day trial, and on 12 September 2026 the tiers gained names — Solopreneur, Emerging Business, Advanced Business Enterprise. source · 2026-09-12 The base banner is free on every plan: categories, modes, Consent Mode v2 and a log. Blocking before consent requires strict opt-in and correct installation.
Scanning volume The scanner is presented as the first-screen magnet; its limits are not named on the homepage and live on the pricing page. source · 2026-09-05 Free — 10 pages once a month. The extension — up to 30 pages weekly, $9/mo.
Consent log retention The log retention period is not named on the captured pages. (not stated on the pages we captured) Free — 3 months; with the extension — 12 months. The log is anonymous: no IP and no precise User-Agent.
Number of domains A separate Cookie Banner Cost Calculator appeared in the homepage footer on 12 September 2026 — the cost is computed from site parameters. source · 2026-09-12 The banner is configured per location of the account. Several locations mean several sets of settings in one dashboard; there is no separate "per domain" charge.

What we never charge for

  • Not for banner impressions and not for site visitors
  • Not for collected consents — neither per one nor per thousand
  • Not for language: all 45 banner languages are in the base tier
  • Not for Consent Mode v2 and vendor signals — they are part of the free tier
  • The public tool checks a specified page without registration. Its result helps with setup; it is not a whole-site audit or a legal compliance opinion.

When Cookiebot is the better fit

Check requirements from your website and advertising partners. Dated vendor claims do not replace checking current terms.

  • You need certifications for a tender or an audit

    The vendor states ISO 27001 and ISO 27701, HIPAA readiness and Google-certified CMP status (captured 2026-09-12). We hold no such certifications and will not claim them. If the client's security team asks for a certificate, that settles it — not in our favour.

    source · 2026-09-12
  • You need IAB TCF

    If your advertising partners require the IAB Transparency and Consent Framework, our banner will not do: we do not support it. Check the vendor's current TCF status with them.

  • You serve dozens of other people's domains

    An agency needs a dashboard organised around domains and clients. Ours is organised around a location of an account — convenient for an owner with several venues, inconvenient for a contractor with a hundred sites.

  • You need a stated list of covered countries and laws

    Consent vendors list their regional and legal coverage explicitly. We give five region modes and a per-country rule, but we publish no "these laws are covered" list — and we will not pass modes off as a legal opinion.

  • You only need a banner

    Our banner can be used on its own. If your team already uses another CMP, assess moving settings and the testing workflow; a free base alone is not a reason to replace a working system.

What we do not promise

  • This is not legal advice. You choose the region mode and the texts, and the log itself guarantees nothing — take contested cases to a lawyer.
  • We hold no ISO 27001 or 27701 certification, no HIPAA readiness and no Google-certified CMP status.
  • The banner does not support IAB TCF.
  • Server Set-Cookie, code executed before our tag and service workers are not intercepted. Check unknown trackers and loading order after theme or analytics changes.
  • If the config is unavailable, the page is excluded or the banner is off, blocking is lifted entirely: keeping your site blocked because of our failure is not acceptable.
  • The age gate speaks four languages — English, Russian, Georgian and Turkish — while your own wording is set per language by you.
  • Scanning does not cover every page, action and website state; repeat checks on real pages after installation.

Where the vendor facts come from

Every claim above was captured from these pages on the date shown. The vendor may have changed since — the links go to the original, check for yourself.

We do not quote third-party reviews, logos or screenshots, and we never present a vendor's numbers as our own. Found a discrepancy with the vendor's page? Tell us and this page gets corrected.

Questions and answers

Does your banner really block trackers before consent?

In strict opt-in, the engine delays known cookies, scripts and embeds matched by the block list or manual markup. Its tag must run first; unknown trackers may need a separate rule. This does not guarantee blocking all website code. Five modes: opt-in, opt-out, soft, notice and hidden. Opt-out permits categories until refusal, so a before-consent promise does not apply to it. Country comes from IP with a time-zone estimate as fallback; check rules for your visitors.

Where do I put your tag so that "before consent" really means before?

First script in the head, without async or defer, above your analytics. Through the shared loader the banner is raised first among our widgets, but a third-party counter nailed higher in the head will not be outrun — and cannot be stopped retroactively.

What exactly is free and what is paid?

The base banner is free. Scanner and log extension: $9/mo; AI classification costs extra. Free: scan up to 10 pages monthly, log for 3 months. The extension raises limits to 30 pages weekly and 12 months; it is not unlimited. AI classification is a separate paid step.

I run WordPress. Do I have to edit the theme?

The WordPress plugin works standalone without an account or connects to a location by token. Standalone mode has no consent log or age gate.

What language will the banner speak?

The page's language: it reads or the tag attribute, and the labels arrive as a pack from the CDN — 45 of them. Your own texts are set per language. The age gate, however, speaks only four languages, and you write its wording yourself.

How do I check what is running on my site right now?

The public tool checks a specified page without registration. Its result helps with setup; it is not a whole-site audit or a legal compliance opinion.

When will the banner ask the visitor again?

When the stored decision expires, the policy version changes or browser storage is cleared. Visitors can also reopen settings through a link and change their choice.

Check your site for trackers and a cookie banner

More detail — per-platform installation, settings and troubleshooting — in the docs. Installation guide →

What to read next

All 12 widgets →

The widget page explains how it works on our side, the docs cover installation and setup, the hub lists the other eleven.

Configure the banner and test rejecting trackers

Create an account, choose a mode and put the synchronous tag before analytics. Test the page before a choice, after rejection and after acceptance.

Configure the widget

The base banner is free. Scanner and log extension: $9/mo; AI classification costs extra.