A deliberately technical definition
From a strictly technical perspective, a CMP is a tag manager. Its role is not to collect data, but to condition the loading of third-party scripts.
The rule is simple: until the user gives consent, a script must not be executed.
An interface at the core
This technical logic is exposed through a user interface: banner, management panel, per-service activation.
Without a clear interface, consent is neither understandable nor usable.
Comparison with a tag manager
The comparison with a tag manager is useful, as long as it is not pushed too far. A tag manager deploys scripts.
A CMP does the opposite: it blocks by default and explicitly allows.
Inherent limits of any CMP
A CMP can only act on what it knows. Unsupported or undeclared services will not be blocked.
This explains why a CMP alone never guarantees compliance, as discussed in what tarteaucitron really does.
Without a precise inventory of scripts, compliance remains theoretical.
