Piwik PRO
How to configure Piwik PRO 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 Piwik PRO Analytics 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. Piwik PRO Analytics (cloud), with Consenter as the consent tool. Piwik PRO's own Consent Manager is no longer offered to new accounts.
What the service does in this scope. Piwik PRO can be configured to "ask visitors for consent" and to "collect anonymous data from non-consenting visitors", with optional session hash and optional visitor cookies; IP masking can be added. The basic cookies are _pk_id.* (13 months for non-anonymous visitors, changeable) and _pk_ses.* (30 minutes); in cookie-free mode they are not set. Hosting location can be chosen.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (⚠ no-consent) | Anonymous data from non-consenting visitors: no visitor cookies, no session hash, IP masked. |
| Configuration B — Medium risk | Consenting visitors only: _pk_id (shortened to 6 months, illustrative), IP masked. |
| Configuration C — Higher risk | Consenting visitors: _pk_id 13 months, full IP, User ID and Data Activation (CDP) audiences. |
⚠ Recommendation — Configuration A without consent is legally uncertain. With cookies and session hash off, Piwik PRO sets no identifier, but the script still runs on the device and transmits data. Piwik PRO publishes a separate article on TDDDG compliance. Document your assessment and have it reviewed by your DPO or independent counsel before running A without consent.
Step 1 — Configure Piwik PRO
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service | Improve the service; Support marketing analytics |
| 2 | Ask visitors for consent | Administration > Sites & apps > Privacy | On | On | On |
| 3 | Collect anonymous data from non-consenting visitors | Same | On | Off | Off |
| 4 | Session hash / visitor cookies for anonymous visitors | Same | Both off | — | — |
| 5 | Visitor cookie lifetime | UI or JS API | — | 6 months (illustrative) | 13 months (default) |
| 6 | IP masking | Privacy settings | On | On | Off |
| 7 | User ID / Data Activation | Tracking code; Data Activation module | Off | Off | On |
| 8 | Hosting | Account hosting choice | EU | EU | EU |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Piwik PRO is a European company with selectable EU hosting. Check the sub-processor list; where a US cloud provider hosts the data, list the United States as a potential access location.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk |
|---|---|---|---|
| Processing purposes | Improve the service | Improve the service | Improve the service, Support marketing analytics |
| Tracking method | No tracking | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers | Device identifiers, IP address, Authentication-derived identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, IP address anonymised | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised, Non-precise location data | As B with IP address instead of anonymised, plus Authentication-derived identifiers, Users' profiles |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | Group based (behaviour) |
| Maximum storage duration | Per plan retention | 6 months (cookie, illustrative) | 13 months (cookie) |
| Processing location | EU; US if US sub-processors | Same | Same |
Privacy-policy follow-up
- Piwik PRO as processor; anonymous tracking (A) and its legal basis; cookies and lifetimes; IP masking; hosting.
Verification checklist
- A: no
_pk_*cookies for non-consenting visitors. - B/C: cookies only after consent.
- IP masking setting matches the mapping.
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