Discover platforms/Usercentrics

GOVERNATLAS / PRODUCT DOSSIER

Cookiebot CMP

Cookiebot presents a consent management product and website scanning workflow.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate the difference between discovering website activity and controlling it. A scan report can identify a tracker, while your consent configuration and integrations determine what happens before and after a user's choice. Both need a controlled test on the website you actually operate.

What this record does not establish

A consent management product and scanning workflow do not establish complete tracker detection, legal compliance or correct behavior of scripts outside the tested implementation.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

On an authorized staging site, run a clean-browser visit, reject optional categories, then accept and withdraw a test choice. Inspect network activity and scanner results at each stage. Add a new synthetic tracker and check whether the next scan leads to a reviewed configuration change.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. Record the website build, consent configuration and observed requests for each stage of the test.
  2. Assign an owner and retest procedure for new scripts, regions and changes to the site's tagging setup.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

Cookiebot presents a consent management product and website scanning workflow. Scope: vendor documentation only; edition and availability boundaries require confirmation.

Source, dates & preserved provenanceCookiebot CMP — official product or documentation page ↗

Authority: vendor owned
Observed 2026-10-14 · Reviewed 2026-10-15 · current until 2026-11-13

Artifact SHA-256: eb6f02f20c57d3f3b04ce1b287f517cb1834852d3b153634e52316a9dd3d7ee4

The hash identifies the preserved capture. The live source may have changed.

Source register

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

What is the scanner's coverage and how are unclassified technologies handled before consent?

02

What deployment, retention and access-control evidence supports the intended use?

03

What underlying assurance documents are available, and which claims remain unverified?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗