This section provides an overview of how Prenly brings in-depth insights from the interactions end-users have when consuming publications. By collecting and analyzing this data, Prenly customers can gain valuable insights into user behavior, engagement patterns, and content performance.
A Prenly application can be set up to collect specific metric events that occur when an end-user interacts using the Prenly Reader. The event concept allows capturing detailed data that serves various analytical needs, providing an efficient and flexible approach to analyze application usage.
Read more about how we use metric events to collect statistical data.
Details about events and data collected is found in the event reference documentation.
A Prenly application can be set up to use one or more integrations that exports event data to various external tools. It is possible to enable different integrations for web, Android and iOS respectively.
Check how to export statistical data using analytics integrations.
Processing of personal data is regulated by the General Data Protection Regulation (GDPR). When using Prenly services, you are the responsible controller of personal data sent in Prenly events.
Your specific usage, market and technical setup may affect what is regarded to comply with the current regulations. Make sure to take caution when deciding on how to process this personal data.
Some - but not all - technical setups, adds personal data to event details, based on who is logged in. For some technical setups, it is configurable whether to send this data or not.
The event details will then contain:
This data would be considered personal data according to regulations.
Contact Prenly customer service if you are uncertain what personal data is used in your technical setup.
Using one of Prenly:s supported CMP:s (consent management platforms) is normally needed for European publishers to comply with both GDPR and the ePrivacy Directive, since Prenly software will process personal data on behalf of the customer. Depending on the consent the user chooses to grant or reject, statistics data can be affected.
For a logged-in user, the default logic is that the user must have granted consent for tracking purposes (or similar consent for specific third-party vendors that some CMP:s support) for the user id to be added to the contextual information. This means that if the user rejected, the user id would not be sent.
In Prenly Workspace, when configuring the CMP module, it is possible to setup this logic in other ways, for example if a customer has another legal basis to process user id, that implies that consent is not needed.