Here you will find information about available events that can be collected in a Prenly Reader application, and the event attributes that contains information describing the interaction in-depth.
Note that when using a statistics integration to export statistical data, also contextual data will be exported as a complement to the event attributes described below.
If you are using Matomo, all event parameters have to be defined as custom dimensions and be numbered according to our dimension id list.
If you are using Google Analytics, most event parameters have to be defined as custom dimensions and a few as custom metrics.
For the moment, the following Prenly events are supported.
| Event name | Web | Native | Triggered when user… |
|---|---|---|---|
| article_audio_start | √ | √ | starts playing an article audio file |
| article_audio_stop | √ | √ | stops or pauses an article audio file, or when the file reaches its end |
| article_open | √ | √ | opens an article in article reading mode. |
| article_view | √ | √ | leaves an article page, reporting the time spent on the article |
| banner_click | √ | √ | clicks a banner on the start page |
| external_audio_start | ⛔ | √ | starts playing an audio file loaded from an external source such as a custom tab web view |
| external_audio_stop | ⛔ | √ | stops playing an audio file loaded from an external source such as a custom tab web view |
| favorite_title_add | √ | √ | adds a specific title to personal favorites |
| favorite_title_remove | √ | √ | removes a specific title from personal favorites |
| podcast_episode_start | √ | √ | starts playing a podcast episode |
| podcast_episode_stop | √ | √ | stops or pauses an episode, or when the episode reaches its end |
| prenly_app_open | ⛔ | √ | opens the application |
| prenly_push_notification_open | ⛔ | √ | clicks on a push notification |
| publication_open | √ | √ | opens a publication |
| replica_box_link_click | √ | √ | clicks a box on a replica page |
| replica_box_link_view | √ | √ | opens a replica page where a clickable box with an external url is displayed |
| replica_page_open | √ | √ | opens a replica page in replica reading mode. |
| replica_pages_view | √ | √ | leaves a replica spread or page, reporting the time spent |
| titles_overview_open | √ | √ | opens the overview page presenting titles within the application |
| title_open | √ | √ | opens the page presenting one title |
Note that all events might not yet have been implemented in all statistics integrations.
We are continuously extending the list of Prenly events triggered in Prenly applications. Please contact our helpdesk if you have feedback regarding this.
Events decided upon, but not yet implemented, will be listed here.
| Event name | Web | Native | Triggered when user… |
|---|---|---|---|
The applications still trigger some deprecated events that were part of an early specification. These events should normally not be used anymore, in favor for new current and upcoming events according to the new standard.
More information will come when these events will be removed from the applications.
| Event name | Web | Native | Triggered when user… |
|---|---|---|---|
| external_url_clicked | 🚧 | √ | opens a link to a web page outside the Prenly application |
| issue_open | ⛔ | ⛔ | opens a Prenly publication |
Prenly native apps that uses a Google Firebase/Analytics integration, will automatically collect and export events regarding basic interactions. Note that these events are triggered by the Firebase software and will only be sent to Firebase and no other integrations.
Some examples that may be of interest for Prenly applications:
| Event name | Triggered when user… |
|---|---|
| app_remove | removes the app from the device. |
| app_update | updates the app to a new version. |
| first_open | opens the app the first time after installation. |
| session_start | engages the app. |
| notification_send | receives a push notification. |
| in_app_purchase | purchases content within the native app. |
A complete list of these events is found here.