Push message reports
Analyze push performance with confirmed delivery tracking, failure diagnostics, CTR insights, and real-time audience metrics.
Push message reports help you track the performance of each push notification, including delivery outcomes, user engagement (CTR), device-level confirmations, and error diagnostics.
Push message report high-level stats.
Delivery statistics and outcome definitions
| Metric | Definition |
|---|---|
| Delivered | Number of messages successfully handed off to push services (e.g. FCM, APNs). This does not confirm receipt on the device. |
| Confirmed Delivery | Devices that confirmed receiving the message. May differ from Delivered due to platform support. See Confirmed Delivery. |
| Clicks | Users who clicked the notification and opened the app. Can only happen once per push Subscription. |
| Click-Through Rate (CTR) | (Clicks / Delivered) * 100% |
| Confirmed CTR | (Clicks / Confirmed Delivered) * 100% |
| Influenced Opens | App opens that occurred shortly after receiving the notification, without clicking. Controlled in Settings > Push & In-App > Influenced Opens. |
| Audience | Number of push Subscriptions in the included segments, excluding duplicates and any in excluded segments. |
| Sent | Subscriptions in the audience minus those unsubscribed, failed, or capped. |
| Unsubscribed | Devices that did not receive the message because they uninstalled the app, cleared browser data, or opted out of push. |
| Failed | Devices that did not receive the message because of an error. See Failed. |
| Remaining | Notifications still queued for sending. |
| Capped | Notifications not sent due to frequency capping settings. |
Deliveredmeans the push services accepted the message.Confirmedmeans the device confirmed receipt.Confirmed CTRis more accurate but only available for supported platforms.
Failed
These errors prevented OneSignal from delivering the message to the push provider:
| Error | Type | Troubleshooting Steps |
|---|---|---|
| SenderIdMismatch | FCM | FCM v1 Sender ID mismatch. Verify Firebase credentials. Users must reopen the app for updated tokens. |
| DeviceTokenNotForTopic | APNs | Token’s Bundle ID does not match your APNs key or certificate. Fix in p8 token or p12 setup. |
| FcmV1InvalidToken / Not Found | FCM | Invalid push token. Check Firebase credentials. Devices must reopen app to refresh tokens. |
| None / Missing | FCM | Firebase Cloud Messaging API may not be enabled in your project. Activate in the Firebase Console and retry. |
| AuthenticationError | FCM | Migrate to the latest FCM v1 API. |
| TopicDisallowed | APNs | APNs token mismatch. Check your Team ID, Key ID, and Bundle ID in p8 config. |
| Expired Certificate | APNs | Your p12 certificate has expired. See certificate setup. |
| 404 Not Found | Web | Invalid push subscription endpoint (bad token). |
| 401 Unauthorized | Web | Web push server gave an unclear 401 error. Retry cautiously — it may cause duplicate sends. |
Delivery status
| Status | Description |
|---|---|
| Delivered | Message has finished being sent to the push service. |
| Scheduled | Message is scheduled for future delivery. |
| Sending | Message is actively being sent. |
| Queued | Message is waiting to be sent. |
| Canceled | Message was manually canceled. See Cancel push notifications. |
| No Recipients | No valid audience at send time (e.g. unsubscribed or out of segment). |
| Failed | OneSignal could not send the message due to errors. |
Message statistics
Shows a graph of clicks, sessions, and custom outcomes over the last 30 days.
Image showing Outcome graph along with custom outcomes
- Messages sent via the OneSignal API are only retained for 30 days.
- Use Template Analytics to track message performance over time.
- Export your message data via the Dashboard or API.
Audience activity
See individual subscription results including:
- Sent
- Confirmed delivery
- Not confirmed
- Clicked
- Not clicked
- Failed
- Unsubscribed
Click Export to download the full list.
If a device shows () in the Device column, it has been deleted.
Message settings
This section shows the details of the message including and a visual summary of how the message was configured before delivery.
- Audience - Details of the audience including:
- Total number of recipients - How many Subscriptions were sent the message
- How the message was sent: Targeting filters or segments used
- Schedule - When the message started sending and per-user delivery options selected, if any.
- Throttling - Any throttling, frequency caps, or channel overrides
- Message - The message content.
- Platforms targeted (Android, iOS, specific browsers)
- Advanced Settings - Like Priority, Time to live, and Collapse ID.
- Additional Data - Any custom data added to the message.
Push message reports
Analyze push performance with confirmed delivery tracking, failure diagnostics, CTR insights, and real-time audience metrics.
Push message reports help you track the performance of each push notification, including delivery outcomes, user engagement (CTR), device-level confirmations, and error diagnostics.
Push message report high-level stats.
Delivery statistics and outcome definitions
| Metric | Definition |
|---|---|
| Delivered | Number of messages successfully handed off to push services (e.g. FCM, APNs). This does not confirm receipt on the device. |
| Confirmed Delivery | Devices that confirmed receiving the message. May differ from Delivered due to platform support. See Confirmed Delivery. |
| Clicks | Users who clicked the notification and opened the app. Can only happen once per push Subscription. |
| Click-Through Rate (CTR) | (Clicks / Delivered) * 100% |
| Confirmed CTR | (Clicks / Confirmed Delivered) * 100% |
| Influenced Opens | App opens that occurred shortly after receiving the notification, without clicking. Controlled in Settings > Push & In-App > Influenced Opens. |
| Audience | Number of push Subscriptions in the included segments, excluding duplicates and any in excluded segments. |
| Sent | Subscriptions in the audience minus those unsubscribed, failed, or capped. |
| Unsubscribed | Devices that did not receive the message because they uninstalled the app, cleared browser data, or opted out of push. |
| Failed | Devices that did not receive the message because of an error. See Failed. |
| Remaining | Notifications still queued for sending. |
| Capped | Notifications not sent due to frequency capping settings. |
Deliveredmeans the push services accepted the message.Confirmedmeans the device confirmed receipt.Confirmed CTRis more accurate but only available for supported platforms.
Failed
These errors prevented OneSignal from delivering the message to the push provider:
| Error | Type | Troubleshooting Steps |
|---|---|---|
| SenderIdMismatch | FCM | FCM v1 Sender ID mismatch. Verify Firebase credentials. Users must reopen the app for updated tokens. |
| DeviceTokenNotForTopic | APNs | Token’s Bundle ID does not match your APNs key or certificate. Fix in p8 token or p12 setup. |
| FcmV1InvalidToken / Not Found | FCM | Invalid push token. Check Firebase credentials. Devices must reopen app to refresh tokens. |
| None / Missing | FCM | Firebase Cloud Messaging API may not be enabled in your project. Activate in the Firebase Console and retry. |
| AuthenticationError | FCM | Migrate to the latest FCM v1 API. |
| TopicDisallowed | APNs | APNs token mismatch. Check your Team ID, Key ID, and Bundle ID in p8 config. |
| Expired Certificate | APNs | Your p12 certificate has expired. See certificate setup. |
| 404 Not Found | Web | Invalid push subscription endpoint (bad token). |
| 401 Unauthorized | Web | Web push server gave an unclear 401 error. Retry cautiously — it may cause duplicate sends. |
Delivery status
| Status | Description |
|---|---|
| Delivered | Message has finished being sent to the push service. |
| Scheduled | Message is scheduled for future delivery. |
| Sending | Message is actively being sent. |
| Queued | Message is waiting to be sent. |
| Canceled | Message was manually canceled. See Cancel push notifications. |
| No Recipients | No valid audience at send time (e.g. unsubscribed or out of segment). |
| Failed | OneSignal could not send the message due to errors. |
Message statistics
Shows a graph of clicks, sessions, and custom outcomes over the last 30 days.
Image showing Outcome graph along with custom outcomes
- Messages sent via the OneSignal API are only retained for 30 days.
- Use Template Analytics to track message performance over time.
- Export your message data via the Dashboard or API.
Audience activity
See individual subscription results including:
- Sent
- Confirmed delivery
- Not confirmed
- Clicked
- Not clicked
- Failed
- Unsubscribed
Click Export to download the full list.
If a device shows () in the Device column, it has been deleted.
Message settings
This section shows the details of the message including and a visual summary of how the message was configured before delivery.
- Audience - Details of the audience including:
- Total number of recipients - How many Subscriptions were sent the message
- How the message was sent: Targeting filters or segments used
- Schedule - When the message started sending and per-user delivery options selected, if any.
- Throttling - Any throttling, frequency caps, or channel overrides
- Message - The message content.
- Platforms targeted (Android, iOS, specific browsers)
- Advanced Settings - Like Priority, Time to live, and Collapse ID.
- Additional Data - Any custom data added to the message.