INFOnline Library Android 2.3.0/iOS 2.4.0
3 reasons to use this version¶
- you are a new customer
- you use a TCF 2.x compliant CMP and want your users
consent decision to be processed automatically. - you want to benefit from optimal privacy compliance by design.
app-measurement: Important to note
With the use of the pseudonymous INFOnline Library Android 2.3.0/iOS 2.4.0 (published 11 January 2022), transmission of the user's consent decision is mandatory. This can be realized by a TCF 2.x-compliant Consent Management Platform (CMP) or a manual consent transmission (OptIn). The user's consent decision is processed directly in the sensor of the INFOnline Library. This means that measurement pulses are transmitted to the INFOnline measuring system only when a positive consent decision has been made by the user.
Checklist for using the INFOnline Library Android 2.3.0/iOS 2.4.0.¶
Prerequisite for using the pseudonymous INFOnline Library as of version Android 2.3.0/iOS 2.4.0¶
- Integration and initialization of the Census (IOMbase) Library as of version 1.0.1
- TCF 2.x-confomre Consent Management Platform (CMP) or a manual consent submission (with each request).
- Check in advance if you have a hybrid app in use.
- Implement the pseudonymous library according to the Integration Guide.
- Quality assure your app - test the update extensively in debug mode and/or SZM-Checker.
Please note and good to know
Frequently Asked Questions.¶
Is it possible to use the new pseudonymous INFOnline Libraries without Consent?
No. Data is only collected and processed as soon as a positive Consent is transmitted to the library. This can be done with a TCF 2.x-compliant CMP or the manual OptIn.
We have a poor OptIn rate for our library, what can we do about it?
To achieve the best possible data quality for your site, we recommend adding census measurement in addition to the existing pseudonymous measurement.
Why do we need to include the Census Library?
In order to achieve the best possible data quality for your site, we recommend that you add the census measurement in addition to the existing pseudonymous measurement.
Census measurement is a new method of collecting Page Impressions. With this method, neither personal data is determined nor is there any intermediate storage of session data with the user. Therefore, the legal restrictions imposed by the EU-DSGVO and the TTDSG do not apply here, which means that data can be collected without the user's consent.
The census measurement provides the calculation basis for the market-relevant performance indicators (media) Visit. This makes it possible to compensate for the losses caused by the consent-based reach survey due to declining consent rates as well as browser restrictions (in the web area).
We don't want to use automatic consent handling. What do we need to do?
Currently the Android 2.3.0 / iOS 2.4.0 libraries do not provide a function to disable automatic consent handling. Therefore, we recommend you to use the latest published version (Android 2.2.1 or iOS 2.3.1 or higher). Please always observe the current legal requirements.
Is it possible to pass automatic and manual consent in the library?
No. It is only possible to submit the consent via the CMP or manually. Both will not work.
How do we handle non-EU reaches?
This function is only available to publishers who have a CMP in use. Reaches that are determined via the parameter "gdpr_applies=false" automatically receive full consent for INFOnline and IVW.
What happens with negative or incorrect Consent?
No measurement impulse is triggered in the case of negative Consent or incorrect Consent notation. No reach data can be collected for INFOnline and IVW.
Is it possible to subsequently create a request without positive consent?
No. Measurement impulses are only triggered if positive consent is available.
What effects does it have on apps that also have the ÖWA measurement integrated?
No, it does not affect the ÖWA measurement. The ÖWA measurement is separate from the pseudonymous consent processing and therefore remains unaffected.