Siteimprove Analytics
How to configure Siteimprove Analytics 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
Overview
This guide explains how to implement different privacy configurations for Siteimprove 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. The Siteimprove Analytics script (siteanalyze_[account_id].js) used for Marketing/Content Analytics or Traffic Analytics. Siteimprove A/S is a Danish company.
What the service does in this scope. By default, the script sets the nmstat cookie (persistent, 1,000 days) with a random ID to recognise the browser, and Siteimprove's web server collects the IP address. IP anonymisation can be enabled under Visitor Privacy; after a 72-hour delay, incoming and historical IPs are purged. Cookieless tracking collects data without setting a cookie and activates enhanced IP anonymisation, where IPs are immediately truncated and hashed. Siteimprove notes that its script is loaded via siteimproveanalytics.com, which is sometimes flagged as a US transfer.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (⚠ no-consent) | Cookieless tracking with enhanced IP anonymisation; Do Not Track respected. |
| Configuration B — Medium risk (default) | nmstat cookie (1,000 days) with IP anonymisation; after consent. |
⚠ Recommendation — Configuration A without consent is legally uncertain. Siteimprove designed cookieless tracking to comply with the GDPR and recommends a separate legal review of applicable consent laws. The script still runs on the device. Have your DPO or independent counsel confirm before running A without consent.
Step 1 — Configure Siteimprove Analytics
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk (default) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | Cookieless tracking | Analytics > Analytics Settings > Cookieless Tracking | On | Off |
| 3 | IP address anonymisation | Analytics > Analytics Settings > Privacy > Visitor Privacy | Enhanced (automatic with cookieless) | On (72-hour delay) |
| 4 | Do Not Track | Same page | Respect | Respect |
| 5 | Opt-out | _sz.push(['notrack']) | Provide opt-out | Use for consent withdrawal |
| 6 | Loading | Consenter script blocking | See ⚠ recommendation | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Siteimprove is EU-based; the script is delivered from siteimproveanalytics.com. Check the sub-processor list; where US CDN or hosting providers are used, list the United States as a potential access location.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk (default) |
|---|---|---|
| Processing purposes | Improve the service | Improve the service |
| Tracking method | No tracking | First party tracking (cross-session) |
| Identifier | No identifier | Device 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 |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per contract | 1,000 days (cookie) |
| Processing location | EU; US if US sub-processors | EU; US if US sub-processors |
Privacy-policy follow-up
- Siteimprove as processor; cookieless or cookie-based tracking;
nmstat(B); IP anonymisation; opt-out mechanism.
Verification checklist
- A: no
nmstatcookie set. - B: no Siteimprove requests before consent; IP anonymisation active.
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