Set up your bannerConfigure Your ToolsMarketing Automation and CRM

CleverPush

How to configure CleverPush 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, Receive personalised marketing offers

Overview

This guide explains how to implement different privacy configurations for CleverPush web push notifications and how to reflect them in the Consenter Manager.

  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. CleverPush web push notifications (CleverPush GmbH, Hamburg, Germany).

What the service does in this scope. To subscribe, the visitor confirms the browser's permission request; CleverPush documents the registration and stores the time of registration and a push token or device ID. CleverPush also statistically evaluates whether and when notifications were displayed and clicked, and stores the topic on which push notifications were activated; the legal basis it names is consent, Art. 6(1)(a) GDPR. Browser storage entries include cleverpush-subscription-status (which CleverPush classifies as technically necessary so that a declining user is not asked again) and cleverpush-subscription-id (subscribers only). Customer data is stored in Germany.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskPush subscription with topic selection only; no segmentation by behaviour; script after consent.
Configuration B — Higher riskPush subscription with behavioural segmentation/tags; script after consent.

⚠ Recommendation — status entry before consent. CleverPush classifies cleverpush-subscription-status as technically necessary. Whether this storage access qualifies under § 25(2) TDDDG before any subscription is not confirmed by the sources. Load the CleverPush script after Consenter consent unless your DPO or independent counsel confirms otherwise.

Step 1 — Configure CleverPush

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionReceive marketing offersReceive marketing offers; Receive personalised marketing offers
2LoadingConsenter script blockingAfter consentAfter consent
3Opt-inBrowser permission promptRequiredRequired
4SegmentationCleverPush channel settingsTopics onlyTags / behavioural segments

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesReceive marketing offersReceive marketing offers, Receive personalised marketing offers
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers
Data categoriesDevice identifiers, Browsing and interaction dataDevice identifiers, Browsing and interaction data, Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelGroup based (properties)Group based (behaviour)
Maximum storage durationFor the duration of the subscriptionFor the duration of the subscription
Processing locationGermanyGermany

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