Push message reports

Push message reports show delivery outcomes, confirmed receipt, failure diagnostics, click-through rates, and per-Subscription audience activity for each push send.

Push message reports help you track the performance of individual push message sends, including delivery outcomes, user engagement (CTR), device-level confirmations, and error diagnostics.

Push message report high-level stats.

---

Delivery metrics

OneSignal sends push notifications to push services (Google FCM, Apple APNs, Huawei HMS) which deliver them to your users’ devices (Subscriptions). The Delivered, Unsubscribed, and Failed metrics come from these push services. The Confirmed receipt and Clicked metrics come from the OneSignal SDK on the device.

Metric	Definition
Audience	The number of Subscriptions in the targeted Segment(s).
Sent	The number of push notifications sent from OneSignal, including both those successfully delivered to the push services (FCM, APNs) and failures. This is a composite metric.
Remaining	The number of Subscriptions in the target audience that haven’t yet received the push notification (queued or in flight). Appears on the dashboard delivery report.
Delivered	The number of push notifications successfully delivered to the push services (FCM, APNs).
Confirmed Receipt	The number of push notifications confirmed as received by the device, verified by the OneSignal SDK. See Confirmed receipt for platform-specific details and requirements.
Clicked	The number of push Subscriptions that clicked the push notification. Push notifications can only be clicked once.
Unsubscribed	The number of push Subscriptions that did not receive the notification because they uninstalled the app, cleared browser data, or opted out and have not opened the app since. OneSignal will not retry these in future messages unless the user re-subscribes and opens the app. This is a reachability state detected at send time, when the push service (FCM, APNs) reports the token as invalid, not an opt-out triggered by this message. Unlike email Unsubscribed (an opt-out action on a specific message), push Unsubscribed reflects an earlier unsubscribe and cannot be attributed to this message’s timing or content. For more details see When do push Subscription statuses update?.
Failed	The number of push Subscriptions that did not receive the push notification because of an error. OneSignal will attempt to send to these Subscriptions in future messages.
Frequency Capped	The number of push Subscriptions that did not receive the push notification due to frequency cap settings.

The following metrics are specific to push message reports:

Metric	Definition
Confirmed Receipt	The number of push Subscriptions that confirmed receiving the message.
Remaining	The number of notifications still queued on the OneSignal side for sending.
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.

For detailed metric definitions across all channels, see the Metrics Glossary.

Failure message troubleshooting

These errors prevented OneSignal from delivering the message to the push provider:

Error	Type	Troubleshooting Steps
401 Unauthorized	Web	Web push server gave an unclear 401 error. Retry cautiously, as it may cause duplicate sends.
404 Not Found	Web	Invalid push subscription endpoint (bad token).
Authentication Error	FCM	Check your FCM credentials, re-upload the service account file, and try again.
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.

---

Delivery status

Status	Description
Delivered	Push notification successfully delivered to the push services (FCM, APNs).
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.

---

Conversions

This report shows the conversions attributed to and influenced by this message. See Conversion metrics for the attribution model and setup instructions.

Message statistics

The message statistics graph tracks clicks, sessions, and custom outcomes (legacy, being replaced by Conversion metrics) over the 30 days following a send. Use it to see whether engagement occurred immediately after delivery or continued over time.

Message statistics graph showing clicks, sessions, and custom outcomes over time.

Messages sent via the OneSignal API are only retained for 30 days. Use Template Analytics to track performance over time, or export your data for offline analysis.

---

Audience activity

The Audience activity report shows how each Subscription interacted with a specific message. Results are grouped into categories so you can diagnose delivery issues, measure engagement, identify unsubscribes tied to a specific message, and segment audiences for retargeting or export.

Audience activity tabs and table

Categories

Category	Description
Sent	Message was sent to the device.
Confirmed Receipt	Delivery was confirmed by the device.
Did Not Confirm Receipt	Delivery confirmation was not received.
Clicked	User clicked the notification.
Did Not Click	User did not click the notification.
Failed	Delivery failed.
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. We will not attempt to send to these Subscriptions in future messages unless the user resubscribes and opens the app. This reflects Subscriptions found unreachable at send time, not users who opted out in response to this message. See Why does a push show a high unsubscribe count?

Each tab displays the number of recipients in that category and lets you drill into the individual Subscription records.

Table columns

Column	Description
External ID	Your system identifier (if set).
OneSignal ID	Unique OneSignal user ID.
Subscription ID	Unique Subscription instance (device + app/browser).
Device	Browser or OS type. If you see (), the device has been deleted.
Subscription Status	Current status (for example, Subscribed, Unsubscribed).
Sent	Time the message was sent.
Confirmed Receipt	Time delivery was confirmed by the device, or - if not.
Clicked	Timestamp if the user clicked, or - if not.
Failed	Indicates if delivery failed.
Unsubscribed	Indicates the push Subscription did not receive the message because the user uninstalled the app, cleared browser data, or opted out of push and has not opened the app since.
Failure message	Error message if delivery failed (for example, “Invalid token”).

Audience activity data is only available for 30 days from the time the message is sent. Export results if you need to retain them longer.

Retargeting audiences

From the Audience activity view, you can send a Retargeted Message directly to any category (for example, all users who did not click).

This makes it easy to follow up with users who didn’t engage, re-engage those who churned, or reinforce success with users who confirmed receipt.

---

Exporting results

You can download audience data with the Export menu:

• Selected activity: exports only the currently viewed tab (for example, all users who failed delivery).
• All activities: exports the full report across every category.

Exports let you analyze results offline, share with other teams, or merge with your CRM and analytics tools.

Exporting data

Export message and user data to CSV for offline analysis.

---

Message settings

The message settings panel displays the configuration used for the send.

• 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.

---

FAQ

When do push Subscription statuses update?

Push Subscription statuses update through two mechanisms:

1. When the user opens your app or site

The OneSignal SDK checks whether the push token is valid and whether notification permissions are still granted, then updates the Subscription status immediately.

For example, if a user disables push notifications in their device settings and then reopens your app, the SDK detects the change and marks the Subscription as Unsubscribed right away.

You can capture these changes with the SDK’s Subscription Observer (mobile | web) to sync status to your own database.

2. When you send push notifications

If a user uninstalls your app, clears browser data, or disables push and never returns, OneSignal cannot detect the change until you send a notification. The push service (FCM, APNs, HMS) reports the token as invalid, and OneSignal marks the Subscription as Unsubscribed.

This detection typically takes 2 or more messages because the push service does not immediately reject an invalid token:

Send	What happens
Message 1	Delivered to device. User then unsubscribes in device settings or uninstalls the app.
Message 2	Push service accepts the message but the device does not receive it. OneSignal reports “Delivered” because the push service has not rejected the token yet.
Message 3	Push service rejects the token. OneSignal marks the Subscription as Unsubscribed.
Message 4+	OneSignal does not attempt delivery to this Subscription.

Use Event Streams to detect unsubscribes in real time when sending messages.

Because detection lags, an unsubscribe is attributed to the send that happened to trigger token rejection, not the send that caused the user to leave. You cannot infer the cause of an unsubscribe from the timing or content of the message it appears on.

If you go long periods without sending to all users, unsubscribes accumulate silently and appear as a large spike when you resume sending. Send to all users at least once or twice a month to detect unsubscribes gradually. See FCM expired token FAQ for more on unsubscribe spikes.

Apple delays unsubscribe reporting by 14+ days. To protect user privacy, Apple does not immediately report uninstalls or permission revocations. If a user opens your app after disabling push, OneSignal detects the change instantly via the SDK. If the user never opens the app again, it may take several weeks for Apple to report the invalid token. See Apple Forum and Technical Note for details.

Use the dashboard or API to delete old Subscriptions to keep your audience clean.

Why does a push show a high unsubscribe count?

A high Unsubscribed count on a specific send almost never means that message drove users to opt out. Push Unsubscribed is a reachability metric: it counts Subscriptions the push service reported as unreachable (uninstalled, cleared browser data, or opted out and never returned) at the moment of this send. The actual opt-out or uninstall usually happened earlier. This send is just when the token was finally rejected.

Common reasons a single send shows an elevated count:

• Accumulated churn since your last send. Unsubscribes build up silently between sends and surface all at once on the next one. A large count often means a big send after a quiet period, not that the send was too frequent or poorly timed.
• Detection lag. The push service does not reject an invalid token immediately. It typically takes 2 or more sends (see When do push Subscription statuses update?). The unsubscribe lands on whichever send triggers the rejection.
• Apple’s 14+ day delay. iOS unsubscribes can surface weeks after the user actually left.

Because of this, you cannot attribute a push unsubscribe to the timing or content of the individual message it appears on, the way you would with an email unsubscribe. To reduce silent accumulation, send to all users at least once or twice a month so unsubscribes are detected gradually rather than spiking. To investigate genuine opt-out behavior (users disabling push in response to your messaging), track Subscription changes via the SDK’s Subscription Observer or Event Streams rather than the per-message Unsubscribed count.

What is the unsubscribe rate?

Where Unsubscribed is shown as a rate, it expresses the share of the send that was found unreachable at send time. As with the count, it is not an opt-out response rate for the message. It rises and falls with accumulated churn between sends, not with the message’s timing or content.

Why don’t my Delivered numbers match Confirmed Receipt?

Delivered reflects what the push service (FCM, APNs) reported: it accepted the message for delivery. Confirmed Receipt requires the OneSignal SDK on the device to report back, which only happens if the device is online and the app processes the notification. Devices that are offline, have the app force-closed, or lack the SDK will show as Delivered but not Confirmed.

How long is audience activity data available?

Audience activity data is retained for 30 days from the time the message is sent. Export your results before this window closes if you need to keep them longer.

---

Related pages

Confirmed receipt

How device-level delivery confirmation works and what affects confirmation rates.

Metrics Glossary

Definitions for all delivery, engagement, and conversion metrics across channels.

Template Analytics

Track push notification performance across sends using templates.

Push throttling

Control delivery rate to manage server load during high-volume sends.