INFOnline (IVW)
Available since PXP 3.8
INFOnline Measurement tracking (Required for IVW-Tracking)
Tracking with INFOnline supports App and Web, but must be configured with different properties per platform. It is recommended to do the event configuration as follows:
- App: /default/tracking_config.json
- Web: /web/default/tracking_config.json
Overview of the supported events and their configuration.
| Templates | Parameter |
---|---|---|
Views (Web) | code comment pixelType | not supported |
Views (Android/iOS) | eventType category comment | supported |
Tracking service key name in "tracking_config.json" is: "infonline"
INFOnline supports view events for Web.
Templates
Templatey key | Required | Template value |
---|---|---|
code | no | A code set by the provider for content identification, associated with the IVW Category System 2.0 in the INFOnline Customer Center. |
comment | no | An optional field used for adding comments or additional information about the event. |
pixelType | no | The values need to be one of:
|
INFOnline supports view events for Android and iOS.
Templates
Templatey key | Required | Template value |
---|---|---|
eventType | yes | Represents the state or type of event, such as: download started, cancelled, successfully completed, or ended with an error. |
category | yes | A code set up by the provider for content identification, associated with the IVW Category System 2.0 in the INFOnline Customer Center. |
comment | no | An optional field used for adding comments or additional information about the event. |
Details for the configuration in apps will be added soon.
INFOnline is not explicitly enabled. If a valid configuration of INFOnline is present in the "experience.config.json", the SDK is integrated into the HTML document.
Structure in experience.config.json
If you use one of the CMPs supported by Purple, you must specify the CMP-specific vendor ID for INFOnline, which you can get from your CMP frontend. Additionally, the IAB vendor ID for INFOnline can also be added.