CleverReach
How to configure CleverReach at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Receive marketing offers, Support marketing analytics
Overview
This guide explains how to reflect CleverReach in the Consenter Manager. On the website, CleverReach is used for sign-up forms; open, click and conversion tracking takes place in emails or in the website's own analytics tool. This guide therefore uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. CleverReach sign-up forms on the website (CleverReach GmbH & Co. KG, Rastede, Germany).
What the service does in this scope. CleverReach offers open, click and unsubscribe rates and conversion tracking via Google Analytics or intelliAd. Website operators must obtain the users' consent (double opt-in) and conclude a data processing agreement with CleverReach.
Step 1 — Implement CleverReach
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Receive marketing offers; Support marketing analytics (email performance) |
| Sign-up form | Double opt-in; inform about email tracking in the consent text |
| Conversion tracking | Runs via Google Analytics / intelliAd; those tools need their own Consenter entries |
| Contract | Data processing agreement |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Entry needed | Optional — only to disclose form data processing | Website footprint limited to forms |
| Processing purposes | Receive marketing offers | Newsletter |
| Tracking method | No tracking | No website tracking cookie in scope; verify in the browser |
| Identifier | Direct identifier | Email address on sign-up |
| Data categories | User-provided data, direct identifier | Form data |
| Legal role of data recipient | Processor | — |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Until unsubscribe | — |
| Processing location | Germany | German company; no CLOUD Act flag unless the DPA lists US sub-processors |
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