Contextual data

Art. no. 216207833

Introduction

Contextual data summary

The Prenly Reader application collects contextual data that typically remain constant over multiple interactions. This data is essential for analyzing end-users, since it provides key context to the recorded events. It offers valuable insights to:

Identify the types of devices and technical environments their users operate in.
Analyze user behavior and preferences to enhance content relevance and engagement.
User consent settings, to know how collected data can be used, ensuring privacy regulations compliance.

Collected data

The contextual data collected is exported differently based on the chosen analytics integration. Below, you will find a detailed list of the data properties we collect, presented using our internal naming conventions.

The format and naming of this data may vary when exported, depending on the specific analytics integration used. For detailed information on how each integration processes and sends this data, please visit the page describing exporting data.

Technical environment

The environment data collected, encompasses technical details and includes information about the device, operating system, and the application version, among others.

Overview

Internal name	Type	Web	Native	Description
platform	string	√	√	Platform of the Prenly reader client.
screen_width	int	√	√	Total width of the screen in pixels.
screen_height	int	√	√	Total height of the screen in pixels.
os_name	string	√	√	Name of the operating system.
os_version	string	√	√	Version of the operating system.
app_name	string	√	√	Public name of the Prenly reader application.
app_version	string?	⛔	√	Version number of the Prenly reader application.
device_manufacturer	string?	⛔	√	Manufacturer of a native device.
device_model	string?	⛔	√	Technical model code of the native device.
user_agent	string?	√	⛔	User agent string of the web browser.

The attributes with the suffix ? are not always available.

Properties

Platform (string)

Platform of the Prenly reader client.

Examples:

"web"
"android"
"ios"

Screen width (integer)

Total width of the screen in pixels. Note that this differs from the width of the actual window, if the application is consumed in a web browser.

Example: 1440

Screen height (integer)

Total height of the screen in pixels. Note that this differs from the height of the actual window, if the application is consumed in a web browser.

Example: 2960

OS name (string)

The name of the operating system.

Examples:

"Android"
"iOS"
"Windows"
"macOS"
"Linux"

OS version (string)

The version of the operating system.

Examples:

"12"
"14.2"

Application name (string)

The public name of the Prenly reader application.

Example: "World News"

Application version (string)

The version number of the Prenly reader application (native reader apps only).

Example: "12.1.0"

Device manufacturer (string)

The manufacturer of the device (native reader apps only).

Examples:

"Samsung"
"Apple"

Device model (string)

The technical model code of the device (native reader apps only).

Examples:

"SM-G991B"
"iPhone13,2"

User agent (string)

User agent string of the web browser (web reader apps only).

Example: "Mozilla/5.0 (X11; Linux i686 on x86_64; rv:52.0) Gecko/20100101 Firefox/52.0"

User information

The user information can be provided disregarding if the user is logged-in or not.

Overview

Internal name	Type	Web	Native	Description
visit_id?	string	√	√	An identifier for the current session/visit.
user_id?	string	√	√	A unique user id for a logged-in user.
customer_number?	string	√	√	A unique customer number for a logged-in user.

The attributes with the suffix ? are not always available.

Properties

The user_id and customer_number properties can only be provided if the user is logged-in. They originate from the login system (that we denote authority) that was used to authenticate and authorize the user, so the format of the values may differ.

The configuration of the authority set up for the application decides:

Whether Prenly handles these properties at all.
If handled, whether Prenly handles only one of them or both.
If handled, whether they are included as contextual data.

Visit id (string)

A unique identifier on UUID format, representing an visit/active session for a specific user, regardless of being logged-in or not. A new session/visit is started if a user is inactive for some time. The visit is not changed if a user logs in or logs out.

Example: "f47ac10b-58cc-4372-a567-0e02b2c3d479"

User id (string)

A unique user id for a logged-in user, derived from the login process.

Examples:

"1558"
"mdh://u358002"

Customer number (string)

A unique customer number for a logged-in user, if available, derived from the login process.

Examples:

"19030"
"cx920034-XYZ"

Consent related info

For some integrations, the contextual data may include information about the consent that the user granted in the consent dialog provided by a CMP (consent management provider).

Consent by purpose

Most CMP:s supported by Prenly allows the user to grant consent by purpose. Some of these CMP:s support defining a number of purposes, but Prenly only support three purposes, namely the analytical, functional and marketing purposes. The choices that the user makes in the CMP dialog are transformed to the Prenly supported purposes and each purpose will be either granted, or not granted, by the user.

A value of true means that the purpose was granted. A value of false means that the purpose was not granted.

consent_analytical
Data type	boolean
Example	true
Description	Whether the user granted processing personal data for the analytical purpose

consent_functional
Data type	boolean
Example	true
Description	Whether the user granted processing personal data for the functional purpose

consent_marketing
Data type	boolean
Example	false
Description	Whether the user granted processing personal data for the marketing purpose

consent_services
Data type	object (sent as JSON)
Example	`{` `"google": false,` `"meta": true,` `"c:6719980": false` `}`
Description	The user's consent for individual services/vendors being used. Each key represents a service identifier, as defined by the CMP module, with a value of `true` or `false` reflecting consent status.

Consent by service/vendor

In some CMP:s supported by Prenly, the user can do more granular selections and grant consent to specific third-party companies, that we denote services . If so, a purpose is considered granted only if all services within the purpose have been granted.

No specific information regarding consent given per service is currently included in statistics.

Consent as a TC string

The TCF (Transparency and Consent Framework) and the TC String (sometimes referred to as TCF String), are concepts developed by IAB Europe to help the digital advertising industry comply with the requirements of the GDPR and ePrivacy Directive. The TC String represents the end-user's consent as given in a CMP dialog. This format is supported by some of the CMP:s supported in Prenly.

If the Prenly reader application is using a CMP that supports the TC String concept, the TC String can be exported as contextual data:

tc_string_v2
Data type	string
Example	CPokAsAPokAsABEACBENC7CgAP_AAH_AAAwIAAAAAAAA
Description	A representation of the user's given consent according to the version 2 of the TCF standard.