This article covers push reporting, which you can use to view and analyze the success of your push campaigns.
Once you’ve launched your campaign, you can return to the details page for that campaign to view key metrics. Navigate to the Campaigns page and select your campaign to open the details page. For push messages sent in Canvas, refer to Canvas Analytics.
Looking for definitions for the terms and metrics listed in your report? Refer to our Report Metrics Glossary and filter by Push.
From the Campaign Analytics tab, you can view your reports in a series of panels. You may see more or less than those listed in the sections below, but each has its own useful purpose.
The Campaign Details panel shows a high-level overview of the entire performance for your push message.
Review this panel to see overall metrics such as how many messages have been sent to how many recipients, the primary conversion rate, and the total revenue generated by this message. You can also review your general settings from this page: Delivery Settings, Audience Settings, and Conversion Settings.
The Message Performance panel outlines how well your message has performed across various dimensions. The metrics in this panel vary depending on your chosen messaging channel, and whether or not you are running a multivariate test. You can click on the Preview icon to view your message for each variant or channel.
If you want to simplify your view, click Add/Remove Columns and clear any metrics as desired. By default, all metrics are displayed.
Here is a breakdown of some key metrics you may see while reviewing your message performance. For the definitions of all push metrics, refer to the Report Metrics Glossary and filter by push.
|Bounces||The push notifications sent to these users were undeliverable. These users have been automatically unsubscribed from all future push notifications. See Bounced Push Notifications.|
|Direct Opens||Instances in which a user opened your app by interacting directly with a push notification.|
|Opens||Instances including both Direct Opens (defined above) and Influenced Opens in which the Braze SDK has determined, using a proprietary algorithm, that a push notification has caused a user to open the app.|
Delivery of notifications is a “best effort” by APNs. It is not intended to deliver data to your app, only to notify the user that there is new data available. The important distinction is that we will display how many messages we successfully delivered to APNs, not necessarily how many APNs successfully delivered to devices.
Bounced push notifications
Apple push notification service
Bounces occur in the APNs when a push notification attempts delivery to a device that does not have the intended app installed. APNs also has the right to change tokens for devices arbitrarily. If you attempt to send to a user’s device in which their push token has changed in between when we previously registered their token (i.e. at the beginning of each session when we register a user for a push token) and the time of send, this would cause a bounce.
If a user disables push within their device settings on subsequent app open the SDK will detect that push has been disabled and notify Braze. At this point we will update the push enabled state to be disabled. When a disabled user receives a push campaign before having a new session, the campaign would successfully send and appear as delivered. The push will not bounce for this user. Following a subsequent session, when you attempt to send a push to the user Braze is already aware of whether we have a token as such no notification is sent.
Push notifications that expire before delivery are not considered as failed and will not be recorded as a bounce.
Firebase Cloud Messaging
Firebase Cloud Messaging (FCM) bounces could occur in three cases:
|Uninstalled applications||When a message attempts delivery to a device and the intended app is uninstalled on that device, the message will be discarded and the device’s registration ID will be invalidated. Any future attempts at messaging the device will return a NotRegistered error.|
|Backed up application||When an application is backed up, its registration ID could become invalid before the application is restored. In this case, FCM will no longer store the application’s registration ID and the application will no longer receive messages. As such, registration IDs should not be saved when an application is backed up.|
|Updated application||When an application is updated, the previous version’s registration ID may no longer work. As such, an updated application should replace its existing registration ID.|
The Historical Performance panel allows you to view the metrics from the Message Performance panel as a graph over time. Use the filters at the top of the panel to modify the stats and channels shown in the graph. The time range of this graph will always mirror the time range specified at the top of the page.
To get a day-by-day breakdown, click the hamburger menu and select Download CSV to receive a CSV export of the report.
Conversion Event Details
The Conversion Event Details panel shows you the performance of your conversion events for your campaign. For more information, refer to Conversion Events.
The Conversion Correlation panel gives you insight into what user attributes and behaviors help or hurt the outcomes you set for campaigns. For more information, refer to Conversion Correlation.
Retention reports show you the rates at which your users have performed a selected retention event over time periods in a specific campaign or Canvas. For more information, refer to Retention Reports.
Funnel reporting offers a visual report that allows you to analyze the journeys your customers take after receiving a campaign or Canvas. If your campaign or Canvas uses a control group or multiple variants, you will be able to understand how the different variants have impacted the conversion funnel at a more granular level and optimize based on this data.
For more information, refer to Funnel Reports.