Consent Change Record vs. Cookiebot
Different jobs: Cookiebot crawls a whole domain on a schedule, auto-detects trackers, and manages the banner that blocks them. This page compares two trace snapshots you already captured of one consent sequence and reports what actually changed — free, local, no account.
What each tool is for
Cookiebot, from Usercentrics, is a consent management platform (CMP). Its scanner crawls a site's pages on a recurring schedule, auto-detects and categorizes the cookies and trackers it finds against its own database, and generates a cookie declaration page. Its banner blocks third-party scripts from firing until a visitor consents, supports IAB TCF, and covers a whole domain as an ongoing subscription tier scaled to page count. It is sold as recurring software; its own pricing is not something this session can verify, so no figure for it is stated here.
This tool does none of that. It does not crawl a site, does not maintain a
tracker database, and does not render or manage a consent banner. It takes
exactly two inputs — a before and after JSON
trace you already captured around one consent choice (the requests fired
and the storage keys written in each state) — and reports what
changed between them: which requests appear only after consent, which fire
regardless, and which storage keys were added. Comparison runs in your
browser tab; nothing you paste is uploaded, and the tool never contacts the
site itself. There is no account, no scheduled crawl, and no per-domain
subscription.
| Question | Where to answer it |
|---|---|
| I need a consent banner built, scripts auto-blocked, and my whole site rescanned for new trackers on a schedule. | Cookiebot, or a comparable CMP — ongoing crawling and banner management is not something this tool does. |
| I have two dated traces of one consent sequence and want to know exactly what changed, right now, for free. | This tool — paste both, get a source-linked diff, nothing uploaded. |
| My site already runs Cookiebot — how do I check its banner is actually blocking what it claims to? | This tool. A CMP's own dashboard reports its configuration, not what a real before/after trace observed; the two can drift once a tag is added outside the CMP. |
| I want automatic tracker detection and categorization across every page of my domain. | Cookiebot or a comparable scanner — this tool has no crawler and no tracker database; it only diffs traces you supply. |
| Do I need to create an account, install a script tag, or pay per page scanned to use it? | This tool: no, ever. Cookiebot is used through a subscription tied to a site's page count. |
| How do I capture and compare a consent sequence myself? | See what did my cookie banner actually change. |
Most teams get different value from each: Cookiebot (or a comparable CMP) to build and run the banner and auto-block scripts across a whole site as a paid subscription, and a free tool like this one for a fast, private, source-linked answer to "what did this one consent sequence actually do" — useful on its own for a small agency, and useful as an independent spot check even for a site that already pays for a CMP.
This tool needs no account and no sign-in: it is a static page, the comparison runs in your browser, and once it has loaded it keeps working with the connection off.
Common questions
Should I use this tool or Cookiebot?
They do different jobs. Cookiebot (from Usercentrics) is a consent management platform: it crawls a site's pages on a recurring schedule, auto-detects and categorizes the cookies and trackers it finds, renders the consent banner itself, and blocks scripts from firing until a visitor consents, across a whole domain, sold as an ongoing subscription tier. This tool does not crawl anything, does not detect trackers on its own, and does not render or manage a banner. You paste two dated trace exports you already captured — one from before a consent choice, one from after — and it reports which requests and storage keys actually changed between them, entirely in your browser. A site that needs its consent banner built, its scripts auto-blocked, and its whole domain rescanned on a schedule is the case Cookiebot is built for. An agency or reviewer that already has two traces of one consent sequence and wants a fast, free, source-linked record of what that banner actually did is the case this tool is built for — including checking whether a Cookiebot-managed banner is blocking what it claims to.
Is this page affiliated with Cookiebot?
No. This site is not affiliated with, endorsed by, or sponsored by Cookiebot or its owner, Usercentrics. Cookiebot is a trademark of its owner, named here only to describe what this tool is and is not.
Open Consent Change Record to compare your own two traces.