Comparison · cookie banner and consent
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
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.
What the guest sees, and what has already happened to the trackers by then.
Vendor · Cookiebot
Us · Masamenu.tr
What you configure it with, what you can evidence, and what stays in your hands.
Vendor · Cookiebot
Us · Masamenu.tr
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 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.
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.
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.
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.
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.
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.
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. |
Check requirements from your website and advertising partners. Dated vendor claims do not replace checking current terms.
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-12If 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.
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.
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.
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.
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.
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.
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.
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.
The WordPress plugin works standalone without an account or connects to a location by token. Standalone mode has no consent log or age gate.
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.
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 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 →
The widget page explains how it works on our side, the docs cover installation and setup, the hub lists the other eleven.
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 widgetThe base banner is free. Scanner and log extension: $9/mo; AI classification costs extra.