The push deliverability reporting feature now provides you the ability to view push received, push dropped, and push failed metrics for Apple Push Notification Services (APNS) and Firebase Cloud Messaging (FCM) push messages. In the  Reports > Reports (classic) > Report center, open the Mobile reports push notifications and filter for these events to view the metrics.

Prerequisites and caveats

• The user's app must include the Acoustic Campaign SDK version 3.8.2 or higher. Versions below 3.8.2 will not report feedback on pushes received, although they may be receiving the pushes. Currently, only native SDKs are supported.
• You must also integrate our notification extension framework for push received to function on iOS. 
• This feature relies on the app having a chance to run in order to report the number of pushes received. Especially in the case of spotty networks, it could be that pushes are received but not reported back to the Acoustic Campaign server until network connectivity can be reestablished. You may therefore see the number of pushes received for a particular campaign grow over time as more devices are able to report in.

Push received reports

In addition to the messages sent metrics, you can now set the events filter to push received to see the push messages for which delivery can be confirmed.

Although the push providers never guarantee push delivery, some geographies have further challenges that make push delivery more difficult:

• Widespread use of phones with over-aggressive power management disrupts background tasks to advertise longer battery life.
• Data networks are sometimes configured to drop push notification messages silently rather than passing them on.
• Push infrastructure issues such as spotty or poor networks prevent the delivery of push messages.
• Mobile networks in China that block FCM and Apple Push notifications.
• Phone manufacturers disable the FCM push notification on Android. For example, Xiaomi and Huawei.

The push reporting feature does not overcome geography issues but allows marketers to quantify them. In addition, marketers may use queries about these pushes in order to send alternate types of messages. For example, marketers may choose to send inbox or in-app messages to allow their customers to stay informed.

Push dropped reports

When mobile push messages are not sent to the provider, they are considered dropped messages. Dropped messages can indicate configuration, application, or service issues such as registration errors resulting in no provider token or invalid application credentials. In such cases, the push messages are not even attempted to be sent to the provider.

Push failed reports

When mobile push messages are sent to the provider but fail to send on the server and are returned by the provider as a failed error, they are considered failed messages. Failed messages can indicate that the application was uninstalled on a mobile device or an invalid provider token was provided.

For more information, see Mobile reports.