Didomi

Didomi is a well-established CMP with robust native support for IAB TCF v2.2 and complex signal propagation.

14% of capability · What we check: The platform broadcasts valid TCF v2.2 strings to vendors and handles granular user consent signals accurately.

The platform offers advanced A/B testing and customization tools specifically designed to maximize user opt-in rates.

12% of capability · What we check: The consent notice layout is clear, accessible, and provides A/B testing or customization options to improve interaction.

Provides comprehensive integration for Google Consent Mode v2, ensuring necessary signals are passed correctly for ad-tech.

12% of capability · What we check: The platform correctly updates ad tags based on user consent signals to satisfy Google's specific technical requirements.

Strong multi-jurisdictional compliance framework covering major global privacy regulations out of the box.

12% of capability · What we check: The software offers geo-targeted consent logic and disclosure settings to meet specific regional legal requirements.

Preference center capabilities are a core strength, facilitating the collection of explicit first-party data.

12% of capability · What we check: The existence of a user dashboard allowing visitors to manage or update their data collection preferences at any time.

Offers solid integration capabilities with major tag management systems and CMS platforms via standard SDKs.

10% of capability · What we check: The platform provides native plugins or snippets for easy deployment via Google Tag Manager or common CMS platforms.

Capabilities exist for synchronization across devices and mobile applications, though implementation complexity varies.

8% of capability · What we check: Consent choices made on one device or app platform are persisted and recognized across other user sessions.

Includes standard vendor gating and consent-based ad recovery features relevant to media publishers.

8% of capability · What we check: The mechanism that blocks unauthorized third-party trackers until the user provides affirmative consent.

Performance is adequate, though heavy custom implementations can introduce noticeable page-load latency.

6% of capability · What we check: Measures the milliseconds added to page load time caused by the consent script execution during initial page rendering.

Documentation is thorough, but enterprise-grade support often requires navigating specialized service tiers.

6% of capability · What we check: Available technical manuals, API documentation, and response times for troubleshooting implementation issues.