Usercentrics

Usercentrics, headquartered in Munich, models consent around data processing services rather than raw cookies: each vendor on your site maps to a maintained legal template describing what it processes and on what basis, and the banner, preference layer, and consent records are generated from that inventory. That inventory-first design is what you’re really configuring — the docs walk through configuring vendors, TCF framework settings, and geolocation rules, and the banner is an output of those choices rather than something you hand-build.

The platform surface is broad for a CMP. The Web CMP ships as a script tag plus a Browser SDK for programmatic control; the Apps CMP for iOS and Android exposes a Core API and an Event API, with a dedicated mobile-games track; a separate CTV CMP covers television platforms. Regime coverage includes IAB TCF 2.x and GPP (including the MSPA US National section) alongside its own consent model, and cross-device consent sharing plus consent-choice persistence handle users who move between properties. On the enforcement side, auto-blocking and the “Smart Data Protector” suppress third-party scripts and embeds pre-consent, which reduces (but does not eliminate) the need to manually gate every tag.

Wiring into a measurement stack is well-trodden: documented Google Tag Manager configuration, Google Consent Mode support with implementation examples, interaction analytics with CSV export, and A/B testing of banner variants via third-party tools. Beyond the browser, Usercentrics documents server-side signal integrations for Google Ads, Meta, TikTok, LinkedIn, Reddit, Snapchat, and AWIN, plus a Meta Signals Gateway product and a GraphQL Partner API for programmatic account management.

Practical notes from the pricing structure: the free web plan is genuinely usable but constrained — one domain, one privacy regulation, two banner languages, and an automated scan only at setup. Geolocation rules require the Plus tier, cross-domain consent sharing requires Pro, and A/B testing and SSO sit in the custom-priced Corporate tier, so a multi-regime or multi-domain rollout lands you several tiers up regardless of traffic. Web and app are licensed separately: web plans meter monthly sessions, the App CMP meters daily active users.

Within its own portfolio the split is deliberate: Cookiebot is the scanner-driven self-serve tool, Usercentrics the configurable product for teams that want to curate the service inventory and legal texts themselves — which means someone has to actually do that curation. Migrating from Cookiebot or another scanner-first CMP is therefore less a technical lift than an editorial one: expect to spend the time mapping your tag inventory onto data processing services and reviewing the generated legal texts.

Use it when you run a mixed web-and-app estate and want granular, per-service consent with EU-centric legal maintenance built in. Look past it when you want set-and-forget automation for a simple site, or a full privacy-operations suite beyond consent.