Statshop (Web2Roi)
How to configure Statshop (Web2Roi) at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for Statshop 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. Statshop audience measurement tag, published by Web2Roi. Servers are in France, maintained by OVH.
What the service does in this scope. By default, Statshop is configured for the consent exemption: one first-party cookie; anonymised IPs; page audience aggregated hourly; device, browser and screen size, referrer domain, time on page, bounce rate and scroll depth aggregated daily. Exempt mode disables third-party ad-platform imports, non-aggregated exports, individual visitor paths and the usid user identifier. A "with consent" version lifts these restrictions. Web2Roi acts as processor and does not share data with third parties.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (⚠ no-consent) | Default exempt mode. |
| Configuration B — Higher risk | "With consent" version: usid, ad-platform imports, individual paths; after consent. |
⚠ Recommendation — exemption is self-assessed and France-specific. CNIL treats audience-measurement cookies as exempt only under strict conditions. Describe A as a self-assessed exemption. § 25 TDDDG in Germany contains no equivalent exemption. Run A without consent only after review by your DPO or independent counsel.
Step 1 — Configure Statshop
| # | Configuration area | Where to configure it | Configuration A — Lower risk (⚠ no-consent) | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Support marketing analytics |
| 2 | Version | Statshop Manager | Exempt (default) | With consent |
| 3 | usid | Tag parameter, only with consent | Not set | Set after consent |
| 4 | Opt-out | CMP or page calling window._optimusConsent.statshop = consent | Provide | Consent withdrawal |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk (⚠ no-consent) | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service, Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, Authentication-derived identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised | As A, plus Authentication-derived identifiers, Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Not documented | Not documented |
| Processing location | France (OVH) | France (OVH) |
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