AdPerformance (Realytics)
How to configure AdPerformance (Realytics) at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for Realytics AdPerformance 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. Realytics AdPerformance v3 tracker, used by advertisers on TV and radio to analyse the resulting website audience. Realytics SAS is a French company; data is processed in the EEA (Paris and Dublin).
What the service does in this scope. AdPerformance produces anonymous, aggregated statistics (visits, device type, advertiser events, geography, creative names, investment). It uses only first-party, pseudonymised statistical cookies tied to the publisher's domain, with the anonymous identifier mu.uid; the IP address is truncated to its first three octets on receipt; raw data is kept for at most 13 months and then deleted. Realytics is processor. Exempt mode excludes cohorts, external imports, non-aggregated exports (groups of 10 or fewer hidden) and individual journeys. The product is TCF v2 compatible; without TCF, RY.optout / RY.optin can be called.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (⚠ no-consent) | Exempt mode: aggregated statistics, truncated IP, no exports beyond aggregates. |
| Configuration B — Higher risk | After consent: additional tracked keys, non-aggregated exports, external imports, finer location. |
⚠ Recommendation — exemption is self-assessed and France-specific. CNIL treats audience-measurement tracers as exempt only under strict conditions. Describe A as a self-assessed exemption. § 25 TDDDG in Germany contains no equivalent exemption. Run A without consent only after review by your DPO or independent counsel.
Step 1 — Configure AdPerformance
| # | Configuration area | Where to configure it | Configuration A — Lower risk (⚠ no-consent) | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Support marketing analytics | Support marketing analytics |
| 2 | Exempt settings | "Data Collect" menu | Exempt configuration | Consent-based configuration |
| 3 | Personal data in tracker parameters | Must not be sent (emails, user IDs) | Required | Required |
| 4 | Consent / opt-out | RY.optout / RY.optin; global opt-out link | Opt-out provided | Consent required |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk (⚠ no-consent) | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Support marketing analytics | Support marketing analytics |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers, IP address |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised, Non-precise location data | As A, plus IP address, User-provided data (if external imports) |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | 13 months | 13 months |
| Processing location | EEA (Paris, Dublin) | EEA (Paris, Dublin) |
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