Admo.tv Analyse
How to configure Admo.tv Analyse 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 Admo.TV Analyse 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. Admo.TV Analyse ("Drive to web") scripts measuring website audience generated by TV and radio advertising.
What the service does in this scope. Admo.TV reports direct and indirect visits, conversions and visits by device type, region and country, broken down by campaign, video and investment. Three scripts are added: a consent flag ADMO_userAdextendConsent (called first; controls whether Admo cookies are set), a global script and conversion scripts. Cookies: cikneeto (session, max. 30 minutes) and cikneeto_uuid (13 months, user identifier). A partial IP address (last byte truncated, immediately anonymised) is used for city-level location and bot detection. Admo.TV acts as processor.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (⚠ no-consent) | ADMO_userAdextendConsent = false: no Admo cookies; traffic data only. |
| Configuration B — Higher risk | ADMO_userAdextendConsent = true after consent: cikneeto and cikneeto_uuid cookies. |
⚠ 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 Admo.TV Analyse
| # | 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 | Consent flag | ADMO_userAdextendConsent before the global script | false | true after consent |
| 3 | Opt-out | Local opt-out in CMP/cookie page; global opt-out in Admo.TV privacy policy | Provide | Provide |
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 | No tracking | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, IP address anonymised, Non-precise location data | As A, plus Device identifiers, e-commerce Activity (if conversions are tracked) |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Not documented | 13 months (cookie) |
| Processing location | Not documented | Not documented |
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