SpeedCurve RUM (LUX)
How to configure SpeedCurve RUM (LUX) 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 reflect SpeedCurve's real user monitoring (LUX) in the Consenter Manager. Synthetic monitoring is out of scope. LUX has no visitor-facing privacy settings, so this guide uses a single fixed-behaviour table.
- Implement the service as described below.
- Map the implementation in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.
At a glance
Scope. SpeedCurve RUM via lux.js.
What the service does in this scope. LUX measures load speed, responsiveness and session length and uses the lux_uid cookie to group a visitor's pages into a session. The cookie expires 30 minutes after the last page view. SpeedCurve documents loading lux.js only after consent from a cookie banner and offers a DPA.
Step 1 — Implement SpeedCurve
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Improve the service |
| Loading | Inject lux.js after Consenter consent |
| JavaScript errors | Captured by default; LUX.trackErrors = false to disable |
| Contract | SpeedCurve DPA |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Improve the service | — |
| Tracking method | First party tracking (single session) | lux_uid, 30 minutes |
| Identifier | Device identifiers | Session ID |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers | — |
| Legal role of data recipient | Processor | DPA |
| Personalisation model | No personalisation | — |
| Maximum storage duration | 30 minutes (cookie) | — |
| Processing location | Per SpeedCurve DPA | Check for US sub-processors; CLOUD Act |
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