Pingdom (with Performance Tracking)
How to configure Pingdom (with Performance Tracking) 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 Pingdom Real User Monitoring and how to reflect it in the Consenter Manager. Pingdom's synthetic uptime monitoring runs from Pingdom's servers and does not involve website visitors; it needs no entry.
- Configure the third-party service.
- Map the configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configuration is a comparative example, not a guarantee of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. SolarWinds Pingdom Real User Monitoring (RUM) script. SolarWinds is a US company.
What the service does in this scope. The RUM script sends performance data to Pingdom's servers. RUM uses local storage to track visitors, saving a random session ID (sid) and the session start time (sst). Pingdom states that it does not save user IP addresses, uses the IP address only to determine country of origin, and that the session ID is unique per domain, so users cannot be tracked across sites.
Simplified format. Pingdom documents no privacy settings to vary (such as storage choice or retention). The guide uses a single fixed-behaviour configuration.
Consent. RUM stores information in local storage on the visitor's device; load the script only after consent.
Step 1 — Configure Pingdom RUM
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Improve the service |
| Loading | Blocked by Consenter until consent |
| Storage on the device | Local storage: sid, sst |
| IP address | Not saved; used for country of origin |
| Cross-site tracking | Not possible (session ID unique per domain) |
| Retention | Not documented |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Improve the service | Page performance monitoring. |
| Tracking method | First party tracking (single session) | Random session ID in local storage. |
| Identifier | Device identifiers | Session ID. |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, Non-precise location data | Performance data, browser/platform; country derived from IP. |
| Legal role of data recipient | Processor | Verify against SolarWinds' DPA. |
| Personalisation model | No personalisation | — |
| Maximum storage duration | Not documented | — |
| Processing location | United States | SolarWinds is a US company subject to the US CLOUD Act. |
Privacy-policy follow-up
- SolarWinds Pingdom as processor; performance data; local storage; IP used only for country; US provider and potential access by US authorities.
Verification checklist
- No
rum-static.pingdom.netrequest and no RUM local-storage entries before consent.
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