Analyze delivery statistics and audience engagement for messaging templates across push, email, and SMS channels in OneSignal. Leverage detailed reports, channel-specific metrics, and exportable audience data to optimize template performance.
Delivery statistics for a push template
Go to Templates
Review analytics and statistics
Edit or export data
Name | Description |
---|---|
Delivered | The number of messages that were sent from OneSignal to the Push Servers (Google (FCM), Apple (APNS), Huawei (HMS), etc.). |
Click-Through Rate | Click-Through-Rate (CTR) is measured by (total clicks/delivered) * 100%. |
Confirmed Click-Through Rate | Confirmed Click-Through-Rate (CCTR) is measured by (total clicks/confirmed delivered) * 100%. |
Influenced Opens | Influenced Opens are tracked when a user does not directly click on a notification received, but opens your app within the βInfluenced time periodβ set in your OneSignal Appβs Settings > Push & In-app > Influenced Opens. |
Name | Description |
---|---|
Sent | The total number of messages sent from OneSignal. This value includes failures. |
Delivered | The number of messages that were sent from OneSignal to the Push Servers (Google (FCM), Apple (APNS), Huawei (HMS), etc.). |
Confirmed | The number of devices that sent us a received confirmation for this message. Note that a few factors may impact this count. See Confirmed Delivery for details. |
Unsubscribed | A failure reason. The number of devices that were unreachable and likely due to being unsubscribed from push notifications. Once a device has been detected as unsubscribed, it will be marked as unsubscribed and future notifications will not be sent to it unless it re-subscribes to notifications again. Older, inactive subscriptions, may also become unsubscribed by Google FCM expiring the device token. Learn more about causes of Unsubscribes. |
Failed | The message failed to be sent due to some kind of error. Common errors and troubleshooting steps can be found in this reference to push errors. |
Remaining | The number of notifications that are queued to be sent. |
Capped | The number of notifications that were not sent due to your frequency capping settings. See Frequency capping for details. |
Name | Description |
---|---|
Clicks | Tracks number of clicks/opens on a push message. Clicks are always measured with direct attribution |
Confirmed Delivery | The number of devices that sent us a received confirmation for this message. Note that a few factors may impact this count. See Confirmed Delivery for details. Paid plan required . |
Sessions | Represented as either a count of sessions, or a sum of cumulative sessions (in seconds) resulting from a push message. OneSignal only counts a session after the user has left the app for over 30 seconds. If a user has fully quit your app or website and reopens it, the session data will apply to Session. If the app or website is still in the background, and the user brings it to the foreground, a new session will not apply. Professional plan required . |
Custom Outcomes | Additionally, you can set up custom outcomes such as purchase amount, action taken by the user, or any other outcome of interest. These are configured in your appβs code. To learn more, read Custom Outcomes. |