Analyze push performance with confirmed delivery tracking, failure diagnostics, CTR insights, and real-time audience metrics.
Push message report high-level stats.
Metric | Definition |
---|---|
Delivered | The number of push notifications that were sent from OneSignal to the Push Servers (Google (FCM), Apple (APNs), Huawei (HMS), etc.). |
Confirmed Delivery | The number of push Subscriptions that confirmed receiving the message. See Confirmed Delivery. |
Clicks | The number of clicks on messages. |
Click-Through Rate | Calculated as (Clicked / 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. |
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 minus those unsubscribed, failed, or capped. |
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. |
Failed | The number of push Subscriptions that did not receive the message because of an error. See Failed. |
Remaining | The number of notifications still queued for sending. |
Capped | The number of notifications not sent due to frequency capping settings. |
Delivered
means the push services accepted the message.Confirmed
means the device confirmed receipt.Confirmed CTR
is more accurate but only available for supported platforms.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. |
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.