GOVERNATLAS / PRODUCT DOSSIER

Termly CMP

Termly's detailed CMP feature table describes scanning, a consent banner and preference center, and blocking of supported tracking scripts. It qualifies blocking by consent settings and supported scripts; broader FAQ promises are not treated as independently established behavior.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Start from the detailed feature table and the exact plan being proposed. A low-friction banner setup is useful, but the evaluation must also account for the records, language rules and operating controls your team will need later. Treat broad FAQ language as a prompt to clarify scope when the more specific table qualifies scripts or restricts a feature by plan.

What this record does not establish

The preserved feature table limits several controls and exports to named plans and describes blocking of supported scripts. It does not prove universal blocking, present-day commercial entitlements or legal compliance. Basic and advanced Google consent mode also imply different technical behavior; choose the intended mode explicitly and assess it against the organization's approved policy.

1 current source · 2 published assertions
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

In a proposed pilot using the intended plan, configure a banner, an optional tracking tag and a separate unsupported script. Run no-choice, reject, selective-accept and withdrawal cases. Inspect the requests and preference state, then attempt the consent-record export and regional configuration your organization requires. Record unavailable actions as plan gaps rather than silently demonstrating them in a different paid account.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A dated plan-to-requirement matrix showing which controls and exports were actually exercised in the pilot account.
Browser evidence and configuration versions for each consent state, with unsupported tags and uncompleted plan-dependent tests retained.

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

The preserved Termly feature table lists regional and multilingual controls and consent-record exports for Pro+ and Agency, with basic Google Consent Mode on Free and Starter and advanced mode on Pro+ and Agency. These are captured vendor plan descriptions, not a current quote, entitlement verification or legal-compliance finding.

Source, dates & preserved provenance

Termly CMP — official product documentation ↗

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

Artifact SHA-256: 97ac7f81af9d07d879970136f15ac08c26f41450ce11ac39e26c551ee7b94979

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

vendor asserted

Source, dates & preserved provenance

Termly CMP — official product documentation ↗

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

Artifact SHA-256: 97ac7f81af9d07d879970136f15ac08c26f41450ce11ac39e26c551ee7b94979

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

Source register

Termly CMP — official product documentation ↗vendor owned · captured 2026-11-03

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.

Can a banner configuration change be reviewed, versioned and connected to observed tag behavior?

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.

COMPLIANCE / CLAIMS, SCOPE & GAPS

Start with the requirement.
Inspect the support.

Prepare your vendor review ↗

These labels describe this dossier’s current evidence coverage. A published mention may be a framework mapping, a qualified assertion or a limitation; it is not a compliance finding.