GOVERNATLAS / PRODUCT DOSSIER

consentmanager CMP

consentmanager describes consent banners, tag blocking, cookie scanning and consent tools for web, mobile apps and connected TV. The captured page identifies consentmanager as part of iubenda; its revenue, latency and legal-compliance claims are not independent findings.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Assess consent consistency across the specific brands and surfaces you need to operate. A website, mobile application and connected-TV application may have different identifiers, SDKs and release cycles. Define where a choice should be shared and where it should remain separate, then make the migration and rollback plan part of the evaluation.

What this record does not establish

The captured page identifies consentmanager as part of iubenda and describes multiple product capabilities. That does not establish shared subscriptions, automatic compatibility or equivalent SDK behavior. Revenue, speed, adoption and compliance statements remain vendor marketing; request current plan terms and measured behavior for the surfaces in your actual rollout.

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 test worth running

For a proposed pilot, run one web property and one second surface with a documented consent policy. Change a purpose or vendor configuration, withdraw a previously accepted purpose and inspect both the local state and the receiving tags or SDKs. If migration compatibility is proposed, compare the old and new implementations in an authorized test environment and preserve the original configuration before switching.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A per-surface consent and identifier map with observed update and withdrawal behavior and explicit unsupported cases.
A versioned migration record with compatibility assumptions, a rollback demonstration and named responsibility for each property.

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.

vendor asserted

Source, dates & preserved provenance

consentmanager CMP — official product documentation ↗

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

Artifact SHA-256: 0f379520c21ef1b8c8ea94645d270904f4809e0bc0e2a33209fcac2a59d5e150

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

Source register

consentmanager CMP — official product documentation ↗vendor owned · captured 2026-10-15

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.

Which SDKs and surfaces honor the same consent choice, and how are stale or conflicting choices reconciled?

Which exact release, deployment and service responsibilities are included in the proposed configuration?

What evidence records the actual outcome, unresolved exceptions and accountable owner?

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 ↗