Advanced Statistics - Push Notifications

In this article, you'll find all the information regarding the information for advanced statistics for push notifications.

 

Statistics of your Push Notifications can be displayed per campaign or messages.

 

The example above shows you the view and information displayed by default.

  • Creation date: is the date your message/campaign has been created 

  • Last send date: is the date your message/campaign has been sent for the last time

  • Recurrence (by messages): schedule type of your Push Notification

 

KPI

Definitions

 

Sent 

 

Number of user to whom the message was sent: 

  • token different from “ “ 

  • feedback less than 3

 

This includes the opt-in and the opt-out profiles, if the criteria system opt-in is not in the segment linked to the message. 

 

Test messages are taken into account. 

For recurrent messages, there is no notion of unique users. 

 

 

Bounces 

 

Number of users who did not receive the sent notification (number of feedbacks sent by distributors, which indicates that they were unable to deliver the message).

 

A bounce is a feedback from Google or APNS, mainly when the user has “uninstalled” the app. 

 

This includes only the opt-in profiles. 

 

 

Bounce Rate

 

Number of bounces, compared to the number of sent. (bounce/sent)

 

 

Opt-out

 

Number of devices targeted which are system opt-in different than Y and system opt-in different than “ ” . 

 

The same profile can get an opt-out and has a bounce. As a matter of fact, a profile can be opt-out and uninstall the app. 

 

 

Opt-out Rate

 

Number of opt-out, compared to number of sent. (bounce/sent)

 

 

Reached

 

Number of successful messages, therefore received by the system. The way we calculate is sent- bounce - opt-out. 

 

Test messages are taken into account. 

For recurrent messages, there is no notion of unique users. 

 

 

Reached Rate

 

Number of messages received by the system (therefore not bounced or opt-out), compared to the number of targets. (reached/sent)

 

 

Reactions 

 

The number of clicks that generates an app opening. 

Reactions can increase up to three days after the message is sent.

On interactive buttons, we count clicks only on action buttons.

 

Test messages are taken into account. 

 

It may also contain clicks from some opt-out profiles, who were considered as an opt-in by the device when the message was sent. However, at this time, we didn’t have the information that they were opt-in as the application hasn’t been opened since. Then, they are not included in the target and reached session, as we only take into account the opt-in profiles. 

These profiles can become opt-in after the click.

 

For unique sending, this is the number of clicks.

For recurrent sending, this is the total of clicks for the time period selected. Then, you can have clicks for the message sent before the time period selected. 

 

 

Reaction Rate

 

Number of users who clicked on the message, compared to  successful  messages (reactions/reached).

 

 

Visits

 

Number of times your application was opened within the 24 hours following a user’s reaction (reaction is not counted in this total). 

 

Post-click statistics, as visits, are incremented for the message which has generated the last reaction. As a matter of fact, during the day, you send a message A and then a message B.

  • The user reacts only to the message A. The visits counters will be incremented for message A.

  • The user reacts to the message A and then to message B. The visits counters will be incremented for the message B and not A (as the last click was done for the message B). 

 

Events

Number of times your application generated an event (including purchase, cart, and lead) within the 24 hours following a user’s reaction.

 

Post-click statistics, as events, are incremented for the message which has generated the last reaction. As a matter of fact, during the day, you send a message A and then a message B.

  • The user reacts only to the message A. The events counters will be incremented for message A.

  • The user reacts to the message A and then to message B. The events counters will be incremented for the message B and not A (as the last click was done for the message B). 

 

 

 

Concrete example

 

The understanding for “Message 03” is:

  • The message has been created on October 29, 2019, and has been sent for the last time on this same date.

  • 13 devices were targeted for the sending time, 13 devices received it and 11 users clicked on the message.

  • After sending and for the selected period, the message has generated 7 openings within the 24 hours after the user's reaction.

 

Warning: On the "total" line, deleted messages are taken into account. They are not visible on the details, however they will still be present of the total calculation. 

 

 

You can look at statistics for a specific push notification message by using the toolbar available in the top right corner of the statistic board. 

 

Custom board

The statistics displayed when accessing the page are the default ones.  

However, you can create your own board with your indicators by clicking on the icon . When clicking, a pop-up appears with the list of the available indicators.

 

You can select up to 13 indicators on your push notification board. If you reach this limit, you will have to remove one indicator to add a new one. As for visual statistics, you can save your board as a custom one. To do so, please: 

  • select the indicators you want and click on the icon

 

  • Indicate the name you want for this board and validate

 

Your custom board is now available in the dropdown menu:

 

The iconallows you to export your statistics through a CSV file. 

On the export file, the data are calculated the same way as described previously. The selected time format (hours, days, weeks, months) will be the one for the export file. They contain all the reactions of the day for messages sent the same day, and the reactions of the day for messages sent days before. 

If you have any other questions on this topic, feel free to reach out to our support via this form.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Submit a request