Set up your bannerConfigure Your ToolsLive Chat and Messaging

Userlike

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

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement different privacy configurations for the Userlike Messenger 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. The Userlike website Messenger (Userlike UG, Cologne, Germany; developed and hosted in Germany).

What the service does in this scope. The Messenger creates the cookie uslk_umm_{organization-id}_s, which holds widget and messenger status and the IDs of existing contacts so that they are recognised on later visits; Userlike states the cookie is on the customer's domain and cannot be used by Userlike to track visitors. Userlike advises loading its JavaScript after consent if you do not consider the cookie technically essential. Userlike offers a privacy mode and an integrated cookie consent management for the chat.

Configurations included.

ConfigurationSummary
Configuration A — Medium riskMessenger loaded after Consenter consent; privacy mode with privacy notice before the chat.
Configuration B — Higher riskMessenger loaded after consent; contacts recognised across visits; contact data (name, email) collected.

⚠ Recommendation — loading without consent. Userlike leaves the classification of its cookie to you. Because it stores contact IDs for recognition on later visits, load the Messenger after consent unless your DPO or independent counsel confirms it is strictly necessary.

Step 1 — Configure Userlike

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features
2LoadingConsenter script blockingAfter consentAfter consent
3Privacy mode / privacy noticeWidget settingsOnOptional
4Contact dataWidget data fieldsNot requiredName, email

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesUnlock additional website featuresUnlock additional website features
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers, Direct identifier
Data categoriesBrowsing and interaction data, Device identifiers, User-provided dataAs A, plus direct identifier
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer cookie inspectionPer cookie inspection
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