consentmanager

What Stevin gets out of consentmanager

consentmanager is the choice when you genuinely need IAB TCF: a European platform with a lot of knobs, built for publishers and advertisers who have to demonstrate strict, standardized consent. We use it where the advertising ecosystem expects those TCF signals and a simple banner falls short. At the same time, that depth is also the risk: a lot of configuration means a lot that can sit wrong, and TCF makes the chain between banner, tags and advertising platform a good deal more sensitive. Teams get stuck when the TCF string is built up neatly but the measurement does not connect to it. consentmanager handles the consent, not whether your tracking is correct afterward. Stevin runs on top, reads the consent status with your tag data and flags when measurement drops out or a tag ignores consent, so a misconfiguration surfaces before your advertising and reporting suffer underneath.

What you pair it with

Choosing consentmanager means stepping into the TCF world, with all the connections that come with it: tag manager, Consent Mode and the advertising platforms that expect the string. That is exactly why you take it, but also where it can break. In practice: set up the whole chain in one go and verify that the TCF signals come through correctly everywhere. The question that remains is not whether you are TCF compliant, but whether your measurement and advertising actually respond to what is in that consent.

Common mistakes

• →Building the TCF string correctly but not connecting the measurement to it.
• →Choosing consentmanager without genuinely needing TCF.
• →Setting the many configuration options and then not testing whether everything comes through.
• →Connecting advertising platforms that interpret the TCF signals differently.