Nosto
How to configure Nosto 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 personalised marketing offers
Overview
This guide explains how to implement different privacy configurations for Nosto and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- 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. Nosto commerce personalisation (recommendations, search, pop-ups) via its JavaScript. Nosto Solutions Ltd is a Finnish company.
What the service does in this scope. 2c.cId assigns a unique identifier to each browser for tracking visits and interactions; Nosto states that its cookies expire after four years. With api.visit.setDoNotTrack(true) (called before any request), Nosto runs without the 2c.cId cookie; this does not disable cookies entirely. In the Shopware integration, Nosto without marketing consent runs in doNotTrack mode, sets no session identifier and sends no customer data. Nosto's Data Processing Policy and Record of Processing Activities are available in the admin.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | doNotTrack mode: non-personalised recommendations; no 2c.cId; after consent. |
| Configuration B — Higher risk | Full tracking with 2c.cId and customer data; after consent. |
No configuration without prior consent. Even in doNotTrack mode, cookies are not disabled entirely; Nosto advises preventing its JavaScript from loading for users who opt out of all tracking.
Step 1 — Configure Nosto
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Personalise the website (non-personalised recommendations) | Personalise the website; Receive personalised marketing offers |
| 2 | Do-not-track | nostojs(api => api.visit.setDoNotTrack(true)) before any request | On | Off |
| 3 | Customer data | Customer tagging / integration | Not sent | Sent |
| 4 | Loading | Consenter script blocking | After consent | After consent |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Personalise the website | Personalise the website, Receive personalised marketing offers |
| Tracking method | First party tracking (single session) | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers, Direct identifier (if customer data is sent) |
| Data categories | Browsing and interaction data, Device characteristics | Browsing and interaction data, Device characteristics, Device identifiers, e-commerce Activity, Users' profiles, direct identifier (if customer data is sent) |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | Group based (properties) | Profile based |
| Maximum storage duration | Not documented | Cookies up to 4 years |
| Processing location | Per DPA | 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