INFOnline Measurement
How to configure INFOnline Measurement 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, Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for INFOnline Measurement (IVW reach measurement) and how to reflect them in the Consenter Manager. It covers both INFOnline index entries and the legacy entry "Ioam".
- 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. INFOnline Measurement for websites via the Measurement Manager. INFOnline GmbH is a German company; the legacy IOAM/IOMb tags are replaced by INFOnline Measurement.
What the service does in this scope. INFOnline offers two methods: Census Measurement (anonymous), which "operates entirely without identification features", and Pseudonymous Measurement, which uses client identifiers and requires valid user consent. INFOnline's own interpretation is that the pseudonymous measurement may only be loaded with active consent under § 25 TDDDG, while the census measurement "may continue to be played out without the user's consent". The Measurement Manager integrates with TCF CMPs (IAB vendor 730) or accepts a manual consent string.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk (no consent, per INFOnline) | Census Measurement only. |
| Configuration B — Medium risk | Census Measurement plus Pseudonymous Measurement after consent. |
Note on Configuration A. INFOnline designed the census measurement for use without consent. As a provider interpretation, document it in your own assessment; if your DPO disagrees, load A after consent as well.
Step 1 — Configure INFOnline Measurement
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service (reach measurement) | Improve the service; Support marketing analytics |
| 2 | Pseudonymous measurement | Measurement Manager | Disabled | Enabled |
| 3 | Consent transmission | INFOnline requires a consent string for pseudonymous measurement; not currently supported by Consenter (see note) | — | Load only after Consenter consent |
| 4 | Census measurement | Measurement Manager | Enabled | Enabled |
| 5 | Loading | Consenter / Measurement Manager | Census without consent | Pseudonymous only after consent |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service, 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 | Aggregated site statistics, Browsing and interaction data, Device identifiers, Device characteristics |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Not documented | Not documented |
| Processing location | Germany | Germany |
Privacy-policy follow-up
- INFOnline as processor for IVW reach measurement; census (no identifiers) and pseudonymous measurement (consent); consent transmission.
Verification checklist
- Pseudonymous measurement requests only after consent.
- Valid
ctvariable sent with each request.
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