Didomi

What Stevin gets out of Didomi

Didomi aims at the user experience: a tidy banner, a real Preference Center where people can set their choices per category, and as a result a better opt-in. We choose it where the privacy choice has to be visible and well presented, not tucked away in a gray pop-up. The flip side is that a nice Preference Center easily draws the attention and the connection to your tracking gets shortchanged. A detailed choice your tags do not pick up is still data loss. That is where teams get stuck: the banner looks good, but the passthrough to Consent Mode is just slightly off. Stevin runs on top of the consent status from Didomi and your tag data, and raises a signal when a choice does not come through or measurement drops out. That way the gap between what the visitor chose and what your tags do becomes visible, before it pollutes your data.

What you pair it with

Didomi delivers the banner and the Preference Center, but you need a tag manager and a correct Consent Mode connection to make the detailed choices actually work. The finer your consent categories, the more can go wrong in the passthrough. In practice: set up the Preference Center and your tags together and test whether each category actually lands in the measurement. Otherwise you offer visitors choices your system quietly ignores, and that only shows up when your report has odd gaps.

Common mistakes

• →Making the Preference Center nice but not testing the connection to your tags.
• →Offering many consent categories without checking whether each choice comes through.
• →Confusing a high opt-in with measurement that really works.
• →Adding tags that do not follow the fine-grained consent logic.