Didomi consent management
Didomi is a consent- and preference-management platform that collects user choices, manages preferences, and exposes consent signals to tags across web and mobile, with support for the IAB TCF. It emphasizes preference management beyond a single banner. This page describes its data model and privacy posture even-handedly, without ranking it against other CMPs.
What this means
Didomi presents consent interfaces and a preference center, stores choices, and signals consent to tags across web and mobile so they fire only for permitted purposes. Its preference-management focus extends beyond a one-time banner to ongoing choice management.
It supports the IAB Transparency and Consent Framework, emitting a consent string downstream vendors interpret.
Data model and posture
The records are consent and preference states — purposes accepted or rejected, timestamp, policy version — keyed to persist, plus the TCF consent string where applicable.
Because the signal governs whether tags may process data, posture depends on correct purpose mapping, enforcing the signal before tags fire, and honoring preference changes. The stored consent and preference data are themselves personal data.
- Consent plus a preference center
- Signals consent across web and apps
- IAB TCF consent string support
- Ongoing preference management
How it appears in analytics and logs
Didomi on a property means a consent and preference layer records choices and exposes a signal tags read before firing, so absent analytics data can reflect declined consent.
Diagnostic use case
Use Didomi to capture consent and broader preferences across web and apps, signaling them to analytics and marketing tags and giving users a place to review and change choices.
What WebmasterID can help detect
WebmasterID's cookie-free approach reduces consent-category complexity, but where Didomi is present its signal should still gate any cookie-based tags.
Common mistakes
- Mapping a purpose incorrectly so a tag fires without consent.
- Ignoring preference-center changes after initial consent.
- Letting tags run before the signal is read.
Privacy and accuracy notes
Consent and preference records are personal data, and the signal governs downstream processing. This is educational, not legal advice.
Related pages
- Usercentrics consent management
Usercentrics is a consent-management platform (CMP) that presents consent interfaces, records and documents choices, and signals consent to tags across web and mobile, with support for frameworks such as the IAB TCF. This page describes its data model and privacy posture even-handedly, without ranking it against other CMPs.
- OneTrust consent management
OneTrust is a privacy and consent-management platform (CMP) that presents consent banners, records choices, and exposes consent signals that tag managers and analytics scripts read before firing. It supports frameworks such as the IAB TCF. This page describes its data model and privacy posture even-handedly, without ranking it against other CMPs.
- GDPR and web analytics: the practical picture
The GDPR governs processing of personal data of people in the EU. For analytics that means: identifiers and IP addresses can be personal data, consent is often required for cookie-based tracking, and minimisation matters. Cookieless, first-party, anonymised measurement reduces the surface — but this is a factual overview, not legal advice.
- Privacy-first analytics
Cookie-free measurement that limits consent gating.
Sources and verification notes
- Didomi — Developer documentationVendor docs on consent, preferences, and TCF.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.