Analyze push performance with confirmed delivery tracking, failure diagnostics, CTR insights, and real-time audience metrics.
Push message report high-level stats.
Metric | Definition |
---|---|
Audience | The number of push Subscriptions in the included segments, excluding duplicates and any in excluded segments. |
Sent | The number of push Subscriptions in the audience sent the message. Excludes the unsubscribed, failed, remaining, or capped Subscriptions. |
Delivered | The number of push notifications that were successfully received by the push services. |
Confirmed Delivery | The number of push Subscriptions that confirmed receiving the message. |
Unsubscribed | The number of push Subscriptions that did not receive the message because they uninstalled the app, cleared browser data, or opted out of push and have not opened the app since. |
Failed | The number of push Subscriptions that did not receive the message because of an error. See Failure message troubleshooting. |
Remaining | The number of notifications still queued on the OneSignal side for sending. |
Capped | The number of notifications not sent due to frequency capping settings. |
Clicks | The number of clicks on the message. |
Click-Through Rate | Calculated as (Clicks / Delivered) * 100% . |
Confirmed CTR | Calculated as (Clicks / Confirmed Delivered) * 100% . |
Influenced Opens | The number of app opens that occurred after receiving the notification, without clicking. Based on time window set in Settings > Push & In-App > Influenced Opens. |
Error | Type | Troubleshooting Steps |
---|---|---|
401 Unauthorized | Web | Web push server gave an unclear 401 error. Retry cautiously — it may cause duplicate sends. |
404 Not Found | Web | Invalid push subscription endpoint (bad token). |
AuthenticationError | FCM | Migrate to the latest FCM v1 API. |
DeviceTokenNotForTopic | APNs | Token’s Bundle ID does not match your APNs key or certificate. Fix in p8 token or p12 setup. |
Expired Certificate | APNs | Your p12 certificate has expired. See certificate 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. |
Permission Denied | FCM | Check the full error message for which permission is missing. Update the permission for the Service Account file and re-upload it to OneSignal. |
SenderIdMismatch | FCM | FCM v1 Sender ID mismatch. Verify Firebase credentials. Users must reopen the app for updated tokens. |
TopicDisallowed | APNs | APNs token mismatch. Check your Team ID, Key ID, and Bundle ID in p8 config. |
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. |
Image showing Outcome graph along with custom outcomes
()
in the Device column, it has been deleted.