Push Notification Message Reports

OneSignal Push Notification delivery and statistics

When clicking a push notification report, you will see the high-level stats like how the message was created, when it started sending, how long it took to fully send and any throttling limits set.

You can find Push Notification Delivery Stats within Delivery > Sent Messages.

Image showing cards for push notification statisticsImage showing cards for push notification statistics

Image showing cards for push notification statistics

Delivery Status

Delivery Status



OneSignal has completed sending the message.


Messages are queued up in OneSignal and will be sent shortly.


Messages are currently sending.


Messages are scheduled to be delivered at the time based on Intelligent Delivery or Timezone option. They should be finished sending within 24 hours.


You or a team member with access to your app has cancelled the delivery of this message.

No Recipients

Recipients are no longer subscribed or no longer fit in the Segment when it was originally scheduled.


The message failed to send.


API Message Data Retention Limit

Messages sent from the OneSignal API or Automated Messages are only saved for about 30 days.
You can export message data for your records through our API or Dashboard. See Exporting Data for more details.

High-level Stats




How many messages were sent from OneSignal to the Push Servers (Google (FCM), Apple (APNS), Huawei (HMS), etc.).

Click-Through Rate

Number of messages clicked divided by Delivered * 100%.

Influenced Opens

Number of notifications confirmed received that were not clicked, but the app/site was visited shortly after. Depends on the Influenced Opens time period set within Settings > Analytics.

Outcomes Statistics

Graph over the last 30 days of how many clicks, sessions and other Outcomes set. See Outcomes for more details.

Image showing Outcome graph along with custom outcomesImage showing Outcome graph along with custom outcomes

Image showing Outcome graph along with custom outcomes

Delivery & Platform Statistics

Delivery & Platform statistics gives you feedback on how the message performed.

Image showing delivery and platform statisticsImage showing delivery and platform statistics

Image showing delivery and platform statistics



Total Sent

The number of devices targeted to be sent the message.


The number of notifications successfully sent to Google, Apple, Microsoft, etc server. This does not necessarily mean the devices have received these notifications.


The number of devices that successfully received the notification. See Confirmed Deliveries for more details.

Failed (Unsubscribed)

The number of devices that unsubscribed from push notifications. See below What are Failed Notifications? for more details.

Failed (Errored)

The number of devices that did not get notifications due to an error. See below What are Failed Notifications? for more details.


The number of devices that have not received the notification yet. These would be for notifications sent using Intelligent Delivery or Timezone optimizations.


The number of notifications that were not sent due to your frequency capping settings. See Frequency Capping for more details.

Audience Activity

Audience Activity is the ability to send push or sms to devices based on interaction (or lack thereof) with the notification. See Retargeting Messages for more details.

Image showing audience activityImage showing audience activity

Image showing audience activity

Message Settings

The Message Settings is a visual of all data sent within the message including which segment or filters used to target and total number of recipients (number of users targeted).


What are Failed Notifications?

There are 2 types of Failed Notifications.

1. Failed (Unsubscribed)

This means the device has unsubscribed from receiving push notifications.

For Web Push this can happen when the user has cleared their browser cookies or has opted-out of notifications from the browser settings.

For Mobile Apps this can happen when a subscribed device has either uninstalled your application or opted-out of notifications from the device settings.

For Android Mobile apps and Web, a device must receive at least two notifications to be detected as Failed (Unsubscribed). The first notification will appear to have been successfully delivered. The device must be turned on and have a network connection to silently reject this first notification.

After this, future notifications will then return as Failed (Unsubscribed) .

Once a device has been detected as unsubscribed, it will be marked as unsubscribed and future notifications will not be sent to it unless it re-subscribes to notifications again.


  • Notification 1 sent and user receives on device, then user unsubscribes.
  • Notification 2 sent, the OneSignal Dashboard shows "Delivered" but the user does not actually receive it.
  • Notification 3 sent, the OneSignal Dashboard shows Failed (Unsubscribed)
  • Notification 4 will not be sent to that device.


iOS Unsubscribe Detection

To protect user privacy, Apple doesn't want developers to know when a user removes the app. Some details provided by Apple can be found here: https://developer.apple.com/forums/thread/670868

If a device unsubscribes and opens the app, OneSignal detects this unsubscribe event right away and updates the record through our SDK. However if the device uninstalls the app or unsubscribes and does not open the app, it may take several weeks for Apple to report the unsubscribe event.

Apple will wait a random amount of time, typically over 14 days, before saying a device is unsubscribed. The unsubscribed detection requires at least two notifications to be sent to the app, after the app is uninstalled. This is in addition to the device being turned on and the required random number of days elapsing after the first notification.

If you need to remove older devices, you can delete them using our dashboard or API or send Background Notifications to all users once a week. Once Apple responds that the token is invalid, we will unsubscribe it automatically.

2. Failed (Error)

Web Push - Failed (Error) generally happens when you change one of the following:

  • the domain of your site or adding the same domain to another app ID
  • the notification data exceeds 4kb
  • there was a temporary issue with the Google Servers

Mobile Apps - Failed (Error) means the FCM sender id on Android or the Bundle ID on iOS have changed from what these devices originally subscribed under. You will need to put the original version to what the users subscribed under to fix this.

Please contact [email protected] with your OneSignal App ID and all the major changes you made to your site.

Did this page help you?