Mobile App Sensor Documentation (English Version)
Mobile App Sensor Documentation (English Version)
Version: | 2.1 |
|---|---|
Date: | 2015-09-25 |
Author: | Kantar Media Audiences (DE) |
eMail: |
Content
- 1 Mobile App Sensor Documentation (English Version)
- 1.1 Method
- 1.2 Information for Developers
- 1.3 Integration of Libraries
- 1.4 Release of the Application
- 1.5 Features on Platforms
- 1.6 Description of the Mobile App Library Interface
- 1.7 Predefined Variables
- 1.8 Supported Platforms
- 1.8.1 Implementation iOS
- 1.8.1.1 Example
- 1.8.1.2 Timeout
- 1.8.1.3 Debug
- 1.8.1.4 Implementation of the URL Scheme in iOS
- 1.8.1.5 How to use the different Files in the Library Package
- 1.8.2 Implementation Android
- 1.8.2.1 Example
- 1.8.2.2 Managing Lifecycle Events in Android Apps
- 1.8.2.3 Android Permissions
- 1.8.2.4 Timeout
- 1.8.2.5 Advise for Implementation when using Android 3.0 and higher Versions
- 1.8.2.6 Note: Starting from Android 3.0
- 1.8.2.7 ProGuard
- 1.8.3 Implementation Blackberry
- 1.8.4 Implementation Windows Phone
- 1.8.5 Implementation Titanium (not supported at the moment)
- 1.8.1 Implementation iOS
Method
Information for Developers
All spring sensors capture the events in the moment in which they arise. This concept is also implemented in the libraries for the apps, that means that all actions are sent immediately.
In case of any questions concerning this, please contact our support team under KA_DE_support@kantarmedia.com
Integration of Libraries
Release of the Application
Features on Platforms
Description of the Mobile App Library Interface
Properties of the Libraries
Predefined Variables
Out of the application, an HTTP request has to be sent to the measuring system.
Variable | Mandatory | Description |
|---|---|---|
ac | No | The action that has been executed. |
The variable: Action (ac)
By using this variable, the measuring system can be informed, which actions have been executed in the application.
Currently, the following actions are understood:
Variable | Description |
|---|---|
| The application has been started. |
| The application was brought to the foreground or has received the focus. |
| The application was brought into the background or does no longer have the focus. |
| The application has been stopped. |
Implementation of an app page request via the action variable (ac)
By using the variable ac, the execution of a content page within an application can be measured also.
Permitted characters are:
a-z
A-Z
0-9
Comma “,”
Point “.”
Dash “-” and Underscore “_”
Slash "/" is used as separator for hierarchy levels
The assignment of content and construction of booking units is in the responsibility of the supplier/marketer.
Example for this variable are
sport_football
mainpage
200_543
Information (optional)
The user can be informed at some point that the application monitors the user actions and transmits them to a measuring system. Furthermore, the user must be informed that he has the possibility to switch of the tracking in the application and can contradict this way. (see: Opt-Out)
For this purpose, you can include data privacy information in your language into an appropriate place of your app implementation:
....................................................................................................................................................................................................
....................................................................................................................................................................................................