New Relic Browser
How to configure New Relic Browser 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 the New Relic browser agent (real user monitoring) in the Consenter Manager. Server-side APM is out of scope. The current agent offers no visitor-facing privacy switches beyond those noted, 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. New Relic browser agent v1220 and later.
What the service does in this scope. For agent v1220 and later, the session cookies (JSESSIONID, NREUM) are deprecated. New Relic briefly collects the end user's IP address to look up country, region, city and ASN details, and no longer retains it once mapping is complete (typically minutes, up to 24 hours). New Relic notes that a consent manager with a conditional script loader can load the agent only after consent.
⚠ Recommendation. Check the agent version and any session features you enable (such as session replay or traces) in your browser app settings, and inspect browser storage before finalising this mapping.
Step 1 — Implement New Relic Browser
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Improve the service (performance monitoring) |
| Agent version | v1220 or later |
| Loading | After Consenter consent via conditional loading |
| Contract | New Relic 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) | Verify session features in use |
| Identifier | IP address | Briefly, for geo lookup |
| Data categories | Aggregated site statistics, Device characteristics, Browsing and interaction data, Non-precise location data, IP address | — |
| Legal role of data recipient | Processor | New Relic DPA |
| Personalisation model | No personalisation | — |
| Maximum storage duration | IP: up to 24 hours; other data per retention settings | — |
| Processing location | United States / EU region per account | US enterprise; 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