View message reports
You can view message reports for in-app and push messages.
- Click in the Report column for a message.
- ( Optional ) Create a sticky filter for the report or change the time period by clicking the Calendar icon.For more information about creating a sticky filter, see Add a sticky filter .
Depending on the type of message you are viewing, the report might vary.
If you are viewing reports for an in-app message, the report looks similar to the following illustration:
In-app message metrics
Here is a list of the metrics that are available for in-app messages:
- Impression , when a message is triggered.
- Click through , when a user presses the Click Through button on an alert or full-screen message, and when a user opens the app from a local notification.
- Cancel , when a user presses the Cancel button on an alert or a full-screen message.
- Engagement Rate , a calculated metric from Adobe Analytics and is the result of the number of click throughs divided by the number of impressions.
If you are viewing reports for a push message, the report looks similar to the following illustration:
The chart at the top displays the number of users who opened the message.
Push message metrics
Here is a list of the metrics that are available for push messages:
- TimeThe time the message was pushed to devices from Mobile Services.
- StatusThe status of the message, and the available statuses are:
- PublishedThe number of device tokens successfully sent to Apple Push Notification Service/Firebase Cloud Messaging (APNS/FCM) for sending the message to the users devices.
- FailedThe number of device tokens not successfully sent to APNS/FCM. Some possible reasons for failures:
If you have an unusually large number of failures, check your push services configuration. If push services appears to be configured correctly, contact Adobe Customer Care.
- An invalid pushID
- The push platform (APNS, FCM, and so on) that was given to push to does not exist for the job's application. For example, the platform might collect iOS push tokens but does not have APNS service configured.
- The message might have failed because the push service was not configured correctly or the Mobile Services system is down.
- BlocklistedThe number of device tokens that are no longer valid to be sent to APNS or FCM. This usually means the app has been uninstalled from the device or the user changed his or her opt-in settings to receive messages. Android and iOS differ about when tokens are counted as blocklisted. Android tokens are immediately shown in the blocklist count. iOS tokens are initially displayed as published, but based on feedback from APNS, are shown as blocklisted on subsequent messages.