Didomi Experts

A CMP is judged on two things. The first is collection: the design of the notice, its performance, its compliance with the framework in force. The second is passing the signal on to the tools, and this is where Didomi holds its value: Google Consent Mode, Microsoft mode, Amazon signal, the transparency framework for advertising vendors, and since May 2026 control over the tags of a server container. Proofs are kept for five years, with the notice version that goes with them.

A failing consent setup never announces itself: it looks exactly like one that works. Three traps come back in every audit. Didomi manages its own vendor categories, which do not map one-to-one onto Consent Mode signals, so control runs through per-vendor blocking. The Consent Mode integration only covers GDPR, which calls for another arrangement outside that framework. And a country with no regulation selected shows no notice at all, its visitors becoming opt-in by default. None of the three produces a visible error.

A CMP collects and broadcasts a signal; it does not decide what a tag does with it. That behaviour is set upstream, in the container: a tag is exempt, conditioned or degraded, and those are three decisions, not a sequence. Our work therefore starts before the notice, with an inventory of what you collect and for which purposes, and it continues in the container. A well-configured CMP on a container that ignores it protects no one.