Set up your bannerConfigure Your ToolsAnalytics

Retency Web Audience

How to configure Retency Web Audience 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 Retency Web Audience and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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. Retency Web Audience JavaScript tag. Retency is a French company; data is hosted on managed servers in France operated by Ecritel.

What the service does in this scope. Retency Web Audience is designed exclusively for exempt audience measurement. It sets _rwa_visitorid (random 16-character first-party ID, 13 months) and _rwa_optout (13 months). Only the first three bytes of the IP address are kept; geolocation is limited to city level. No individual browsing data is kept longer than 24 hours; deduplicated statistics are kept over 18 months, and statistics are produced only with at least 10 contributions. The publisher is controller and Retency is processor. With opt-out, measurement is reduced to a simple page-view count without visit continuity or tracers.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskoptout: true at initialisation for visitors who refuse: page-view count only, no tracers.
Configuration B — Medium risk (⚠ no-consent)Default exempt measurement with _rwa_visitorid.

⚠ Recommendation — exemption is self-assessed and France-specific. CNIL treats audience-measurement cookies as exempt from consent only where they serve solely the publisher's audience measurement, produce anonymous statistics, are not cross-referenced or passed on, and do not allow tracking across sites; it recommends a cookie lifetime of about 13 months without automatic extension and data retention of at most 25 months. CNIL now offers a self-evaluation tool rather than an approval programme, so describe the configuration as a self-assessed exemption. § 25 TDDDG in Germany contains no equivalent audience-measurement exemption. Run B without consent only after review by your DPO or independent counsel; otherwise use A for visitors without consent and B after consent.

Step 1 — Configure Retency Web Audience

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium risk (⚠ no-consent)
1Processing purposesOperator decisionImprove the serviceImprove the service
2Opt-out at initialisationTag constructor optout: truetruefalse
3User opt-outrwa.optout → _rwa_optout (13 months)—Provide link
4Personal data in tag fieldsDo not pass emails or customer numbersRequiredRequired

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium risk (⚠ no-consent)
Processing purposesImprove the serviceImprove the service
Tracking methodNo trackingFirst party tracking (cross-session)
IdentifierNo identifierDevice identifiers
Data categoriesAggregated site statistics, IP address anonymisedAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address anonymised, Non-precise location data
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage duration18 months (statistics)13 months (cookie); 24 hours (individual data); 18 months (statistics)
Processing locationFranceFrance

Privacy-policy follow-up

  • Retency as processor; exempt measurement or reduced count; cookies; IP truncation; hosting in France; opt-out link.

Verification checklist

  • A: no _rwa_visitorid cookie.
  • Opt-out sets _rwa_optout.

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

On this page