General notes on the app measurement¶
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.
When must the library be called?¶
Calling up the functions of the INFOnline Measurement Library within the app is tied to certain events. For this purpose, agof and IVW have formulated guidelines and recommendations for app providers regarding the points in the app (or the user actions) at which the INFOnline Measurement Library is to be called up and what information is to be transmitted.
Where can I find the Integration Guides for the corresponding operating systems?¶
The Integration Guide for the Libraries can be found on the left in the menu for the corresponding operating system. You will receive the link as well as the access to the libraries via email when you set up your apps.
Offline use¶
INFOnline Measurement census measurement no longer has offline measurement. Due to the requirements of the Telecommunications Telemedia Data Protection Act (TTDSG), no data can be stored on the device, making offline measurement impossible.
Transmission of measurement data¶
Since the library does not store any data, the data is sent directly per event to INFOnline.
The sending of the data itself takes place asynchronously. This means that the user's interaction with the app is not delayed or blocked.
Data protection¶
The INFOnline Measurement census library does not store or read out data on the device. Thus, consent is not required from the user, as this is anonymous data that is neither stored on the device nor read out.
note
The user of the app must be given an Opt-out function. The implementation of this is the responsibility of the developer of the respective app. Once the function has been integrated, the users of the app can activate as well as deactivate the Opt-out. If the Opt-out is activated, no counter pulse is triggered. Information on the integration of an opt-out and opt-in function of the consent-obligatory measuring components can be found here for iOS and here for Android.