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

MetricDefinition
DeliveredThe number of push notifications that were sent from OneSignal to the Push Servers (Google (FCM), Apple (APNs), Huawei (HMS), etc.).
Confirmed DeliveryThe number of push Subscriptions that confirmed receiving the message. See Confirmed Delivery.
ClicksThe number of clicks on messages.
Click-Through RateCalculated as (Clicked / Delivered) * 100%.
Confirmed CTRCalculated as (Clicks / Confirmed Delivered) * 100%.
Influenced OpensThe number of app opens that occurred after receiving the notification, without clicking. Based on time window set in Settings > Push & In-App > Influenced Opens.
AudienceThe number of push Subscriptions in the included segments, excluding duplicates and any in excluded segments.
SentThe number of push Subscriptions in the audience minus those unsubscribed, failed, or capped.
UnsubscribedThe number of push Subscriptions that did not receive the message because they uninstalled the app, cleared browser data, or opted out of push.
FailedThe number of push Subscriptions that did not receive the message because of an error. See Failed.
RemainingThe number of notifications still queued for sending.
CappedThe 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.

​
Failed

These errors prevented OneSignal from delivering the message to the push provider:
ErrorTypeTroubleshooting Steps
SenderIdMismatchFCMFCM v1 Sender ID mismatch. Verify Firebase credentials. Users must reopen the app for updated tokens.
DeviceTokenNotForTopicAPNsToken’s Bundle ID does not match your APNs key or certificate. Fix in p8 token or p12 setup.
FcmV1InvalidToken / Not FoundFCMInvalid push token. Check Firebase credentials. Devices must reopen app to refresh tokens.
None / MissingFCMFirebase Cloud Messaging API may not be enabled in your project. Activate in the Firebase Console and retry.
AuthenticationErrorFCMMigrate to the latest FCM v1 API.
TopicDisallowedAPNsAPNs token mismatch. Check your Team ID, Key ID, and Bundle ID in p8 config.
Expired CertificateAPNsYour p12 certificate has expired. See certificate setup.
404 Not FoundWebInvalid push subscription endpoint (bad token).
401 UnauthorizedWebWeb push server gave an unclear 401 error. Retry cautiously — it may cause duplicate sends.

​
Delivery status

StatusDescription
DeliveredMessage has finished being sent to the push service.
ScheduledMessage is scheduled for future delivery.
SendingMessage is actively being sent.
QueuedMessage is waiting to be sent.
CanceledMessage was manually canceled. See Cancel push notifications.
No RecipientsNo valid audience at send time (e.g. unsubscribed or out of segment).
FailedOneSignal 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.