Set up your bannerConfigure Your ToolsA/B Testing and Personalisation

trbo

How to configure trbo at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Personalise the website, Receive marketing offers

Overview

This guide explains how to implement different privacy configurations for trbo and how to reflect them in the Consenter Manager. It covers the index entries "trbo", "trbo (only Banner)" and "trbo (with Profiling)".

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. trbo onsite personalisation, optimisation and A/B/n testing (trbo GmbH, Munich).

What the service does in this scope. trbo delivers layers in the website design based on user behaviour data; it states that it does not collect personal user data and that cookie information is never shared with third parties. An opt-out button sets a cookie that stops trbo collecting information and deactivates the solution. The index distinguishes a banner-only use and a use with profiling.

Configurations included.

ConfigurationSummary
Configuration A — Medium risk ("only Banner")Static onsite banners/layers without behaviour-based targeting; after consent.
Configuration B — Higher risk ("with Profiling")Behaviour-based targeting and personalisation; after consent.

No configuration without prior consent. trbo sets cookies to record session information; no consent-free configuration is documented.

Step 1 — Configure trbo

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionReceive marketing offersPersonalise the website; Receive marketing offers
2Targetingtrbo campaign settingsNo behavioural targetingBehavioural targeting / profiling
3LoadingConsenter script blockingAfter consentAfter consent
4Opt-outtrbo opt-out linkProvideProvide

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesReceive marketing offersPersonalise the website, Receive marketing offers
Tracking methodFirst party tracking (single session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers
Data categoriesBrowsing and interaction data, Device characteristicsBrowsing and interaction data, Device characteristics, Device identifiers, Users' profiles, e-commerce Activity
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationGroup based (behaviour)
Maximum storage durationNot documentedNot documented
Processing locationPer DPA (trbo is German)Per DPA

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page