Engagement reports are available in a messaging project’s Reports menu. See: View Engagement Reports.
With the exception of the Event Tracking report, which will display custom events for any platform, reports show data for iOS, Android, and Amazon only.
Reports » App Metrics assesses app activity: sends, app opens, and time in app.
Three panes display individual metrics for the current month to date. Hover over the trend chart in a pane to see metrics per day. Click the arrows to change the month.
Total Sends: Monthly total to date, percentage change from prior month, daily trend. Count includes alerting sends only; silent sends (via silent push notifications) are ignored.
Total App Opens: Monthly total to date, percentage change from prior month, daily trend. Count includes repeated app opens by individual users. To see the number of unique users that have opened your app, see the Unique App Opens report.
Average Time In App: Average number of minutes per user session, percentage change from prior month, hourly trend. Airship collects this data from user session events and measures it in seconds. Though behavior varies by operating system, we calculate this from events received each time your app is opened, brought to the foreground, or sent to the background.
A chart displays combined metrics. Toggle displayed data by clicking Sends, App Opens and Time In App in the upper left corner of the chart.
View Time In App with Sends to see the influence your message may have had with users' session length.
Sends counts notifications rather than total pushes sent, so rich messages are included in the report only if:
- The users receiving the messages have opted-in to push notifications, and
- The messages include a notification, e.g., a badge, sound, alert text, etc.
To view the total number of rich messages delivered, see Message Reports.
An increase in Sends often corresponds to a decrease in the Time In App metric. An increase in sends may cause your audience to open your app more often, but opens from push notifications can be very short, i.e., just long enough to read the message or perform a short action).
Reports » Devices provides a current view of your audience by the number of devices opted in to and out of notifications. This report is generated daily. For the purposes of this report, a web browser is a “device."
The registration call that returns opt in/out status is slightly different for apps vs. browsers:
Apps: On initial app open, a channel ID is created for the user and is registered with Airship, passing along segmentation info, i.e., tags, and opt-in/out status. On subsequent app opens, registration calls are made, passing the current metadata and opt-in/out status.
Browsers: A registration call to Airship is made when the user initially opts in to web notifications. This initial registration passes device metadata and opt-in status to Airship. See: Web: User Registration.
Once we receive the event, we record the status, which is reflected in the next day’s report.
Unique Devices: Total number of devices that have opted in or opted out of push notifications. The Unique Devices count does not include uninstalled devices. If your app only supports one platform, Combined Unique Devices is not displayed.
Opted-in: Devices with notification permissions on.
Opted-out: Devices with notification permissions off. For web, this only includes users who had previously opted in to web notifications. For SMS, opt-outs occur by sender ID, so a user might opt out of one program but still have an MSISDN known to your project.
Uninstalled: Amazon/Android: Number of app uninstalls observed from opted-in devices.
Uninstalled: iOS: Number of app uninstalls observed from either opted-in devices or devices with background app refresh enabled.
Uninstalled: Open: Number of successful calls to the open channel Uninstall API.
Uninstalled: SMS: Number of MSISDNs that have been uninstalled. This happens automatically for any MSISDN on the carrier deactivation lists.
Uninstalled: Web: Number of users who have opted out of web notifications via browser settings and have not returned to your website.
See Detecting Uninstalled Devices for information about the nuances related to the Uninstalled metric.
The Devices report requires that analytics be enabled in the SDK. Analytics are enabled by default, and disabling them renders certain features, e.g., reports or location triggers, useless. See the Analytics and Reporting sections of the SDK documentation for information about enabling analytics:
The total devices count in Message Reports may differ from the total devices count listed in the Devices report. This may be due to but is not limited to:
- Additional platforms supported beyond iOS and Android.
- Devices registered via the server.
- Timing of when the Devices report is generated and when a user opens your app for the first time or uninstalls your app.
Use the CSV Download to save daily snapshots and perform custom comparison. For example, if you’d like to see how many people have opted in to your app for the first full week in January, download the January 5th and January 11th reports, open the files in a spreadsheet app, and calculate the difference in device counts.
Detecting Uninstalled Devices
When you send a push notification to a device that has uninstalled your app, Airship receives feedback from the platform push service (APNs or FCM) that the device is inactive. When we generate the daily Devices report, we remove the device from the Unique Devices total and opt-in/out status breakdown, and add it to the Uninstalled count.
Uninstalls are detected by either:
- A standard push notification, sent to iOS or Android devices, or
- A background push using the
content-availableflag, sent to iOS devices.
A device must have push enabled so that it can receive the notifications you send. Also keep in mind that users can prevent receiving background pushes by disabling the Background App Refresh option in their phone’s settings.
To send background pushes, first
enable it in your application,
then send an empty push notification that has the
API: See iOS Platform Overrides for information about using the
UI: Enable Background Processing to use the
content-availableflag. See: Optional Features: Background Processing.
Since there are two detection methods for iOS, the iOS Uninstalled count can include 1) devices that were opted-in to push, and 2) opted-out devices that have background push enabled. The Android Uninstalled count will only include devices that were opted-in to push.
If a user re-installs the app and opens it, the device is moved out of the Uninstalled count and placed back in the Opted-in/out count.
Uninstalls are determined by these two methods only. For instance, a Rich Message sent without a push notification would not receive uninstall feedback.
When you send a push notification to a web user, their opt-in status is returned to Airship via the push service, e.g., FCM (Chrome) or Mozilla (Firefox).
A user is considered to be Uninstalled if they have both:
- Opted out via the browser settings, AND
- Not returned to the website.
When we generate the Devices report, we remove the device from the Unique Devices total and opt-in/out status breakdown, and add it to the Uninstalled count. If the user opts out via the browser settings and does return to the website, we instead include the device in the Opted-out count.
If the user again opts in to notifications, we remove the device from the Uninstalled count and add it back to the Opted-in count.
See Web: User Registration for additional information about registration status and options.
Reports » Email aggregate email notification information for your entire Airship project and per campaign categoryAn optional delivery feature used to group messages of similar types or messaging strategies for aggregate reporting. Campaigns help you track the efficacy of both your individual messages and a messaging campaign as a whole. . Percentages are based on the total number of notifications sent.
Sent: Total number of messages sent to users.
Delivered: Percentage and number of messages accepted by the recipient’s mailbox provider for delivery. This count does not include messages that were accepted by the mail server but bounced before delivery. See note below regarding Bounced Messages.
Opened: Percentage and number of times messages were displayed. This is a raw count, not per unique user.
Clicked: Percentage and number of clicks on tracked links. This is a raw count, not per unique user.
Bounced: Percentage and number of bounced messages, for all reasons. See note below regarding Bounced Messages.
Unsubscribed: Percentage and number of unique users who unsubscribed via unsubscribe links in your emails.
Complained: Percentage and number of spam complaints.
Mail servers generally process messages as they are received, either accepting for delivery or rejecting (bouncing) them.
Some mail servers, however, first accept all incoming messages and later process bounces and inbox delivery. The Email report’s Delivery count does not include messages that were accepted by the mail server but bounced before delivery to the recipient inbox.
Reports » Event Tracking is an aggregate view of your Custom EventsEvents that indicate that a user performed a predefined action, such as adding an item to a shopping cart, viewing a screen, or clicking an Unsubscribe button. Custom events can trigger automation and journeys. You can code them into your app or website, or send them to Airship from an external source using the custom event API. Custom events contain
properties that you can use to personalize messages.
. This report only shows custom events associated directly with channels. It does not show events associated with named usersA customer-provided identifier used for mapping multiple devices and channels to a specific individual.
Event Name: Human-readable name assigned to a particular Custom Event.
Notification Attribution: Displays whether your event was directly or indirectly attributed to the push notification.
Location: The source from which the event originates, most commonly one of Interactive Notification, Message Center, Landing Page, or Custom.
Count: Number of instances of this event.
Value: The value (monetary or otherwise) generated by the event.
Avg. Value: Value divided by Count.
% of Total Count: Count divided by the Total Count (listed on the bottom row).
Only events that have been assigned a value within your app project will generate values for the aggregate view. Event values are assigned by you when creating events, and should align with your campaign strategy when considering the respective weights of different activities you seek to measure. The aggregate view is only meaningful when the unit of measure for these activities is the same. See Custom Events for details on Custom Events setup and strategy.
Reports » Performance AnalyticsA customizable marketing intelligence tool that provides access to reports and graphs based on engagement data. is an add-on tool. See: Performance Analytics Dashboards and Spaces.
Reports » Push Response assesses the impact of notification sends on app opens, with data displayed per platform.
Reports » SMS provides aggregate SMS notification information for your entire Airship project and per campaign categoryAn optional delivery feature used to group messages of similar types or messaging strategies for aggregate reporting. Campaigns help you track the efficacy of both your individual messages and a messaging campaign as a whole. . Percentages are based on the total number of notifications sent. Select a preset date range or set a custom range to adjust the scope of the report.
Sent: The total number of SMS messages sent from your Airship project.
Delivered: The total number of SMS messages that your audience received. Messages might go undelivered if the recipient device is turned off or deactivated.
Clicked: The total number of links users clicked or tapped from your SMS messages. This is a raw total. It is not limited to a single use per message or audience member.
For reporting on individual messages, go to Messages » Messages Overview and click for a message.
Unique App Opens
Reports » Unique App Opens counts the number of unique users who opened your app — it is not the number of times a single user opened the app. Change the date range to determine the frequency used to count app opens: hourly, daily, weekly, etc. The default view is Last 7 days.
The top chart displays counts for Opt-in Opens and Opt-out Opens compared to Sends for all platforms, with total, average, high, and low values below. To filter by platform, click All Platforms and select iOS or Android. If your app only supports one platform, the filter is not displayed. When viewing a weekly or longer date range, you can click the column for a specific day to narrow the report to that day’s data.
Total is the sum of the displayed bars rather than the total number of unique users who opened the app in the defined time period. For example, if you are displaying seven days of data, a given user will appear only once per day but might be counted up to seven times in the total.
The Percentage pie chart compares the percentage of users who opened your app and were opted in to notifications (Opt-in Opens) to users who were opted out (Opt-out Opens). The Trend line graph displays the trending percentage of unique user app opens per platform.
The Percentage pie chart only counts users who opened your app in the displayed time range. This may not be an accurate representation of the percentages of your install base as a whole.
You might use the Unique App Opens report report to determine the opt-in and opt-out breakdown of your daily and monthly active users. By default, the report is set to the last 7 days, providing a view of daily active users.
When viewing daily active users (7 days' activity), a user who opens the app three times on a single day and an additional four times on a different day would contribute one unique open for each of those days.
When viewing a monthly active users (30 days' activity), a user who opened the app 10 times would contribute exactly one unique open for that month.
Reports » Web provides aggregate web notification information for your entire Airship project and per campaign categoryAn optional delivery feature used to group messages of similar types or messaging strategies for aggregate reporting. Campaigns help you track the efficacy of both your individual messages and a messaging campaign as a whole. . Percentages are based on the total number of notifications sent. Select a preset date range or set a custom range to adjust the scope of the report.
Sent: The total number of Web notifications sent from your Airship project.
Clicked: The total number of notifications that users clicked.
Sessions: The total number of web sessions in the specified date range. This does not necessarily equate to total audience; audience members can initiate multiple sessions.
Attributed Sessions: Attributed web sessions are the total number of sessions attributed to a push notification. An attributed session is a session that occurs within a 12-hour window of a web push notification. Sessions are generated when a user directly visits the website with the Airship Web SDK present, or by clicking a web notification that leads the visitor to the site. The page the user visits must have the Web SDK installed to track sessions.
For reporting on individual messages, go to Messages » Messages Overview and click for a message.
Appendix: Push Influence Primer
A number of technical and user-behavior factors make it difficult to attribute an app open to a push notification with 100% accuracy. As the industry’s first and largest commercial push notification provider, Airship has both the experience and the data to recognize and model attribution across all app types with a high degree of confidence. The result is our Push Influence algorithm which informs the Push Response report.
As in the graph below, we see that App Opens rise dramatically after a push notification is sent.
App Opens vs. Pushes Sent
As such, Direct Opens understate the true impact of a push notification. A significant number of additional opens will occur in the wake of a push, but in the absence of an interaction with the notification itself, attribution is complicated. Understanding that users are often occupied when the notification arrives and will return to the app later, we have a higher degree of confidence that a push influenced an open the sooner the open occurs relative to the push.
Indirect Open: when a user is sent a push, but DOES NOT tap it. Instead, it reminds them to open the app later, at a more convenient time.
To complicate matters, we must deal with the fact that some of the observed App Opens would likely have occurred anyway, even in the absence of a push notification. Every app has as natural amount of organic opens which will vary depending on app category, popularity, and other factors. We refer to this natural rate of App Opens as the Baseline Open Rate
With the context of Direct Opens, Indirect Opens, and Baseline Opens, we have a framework for understanding the true impact of push notifications on App Opens. We call this derived metric Influenced Opens.
Influenced Opens represent the number of opens that occur both directly and indirectly as a result of a push notification, less the baseline organic opens that would be expected anyway. The following four bullets describe the basic formula for arriving at the Influenced Opens figure:
- Influenced Opens include Direct Opens and Indirect Opens by opt-in users.
- Only opens within a 12-hour window* after the push is sent are included in the calculation.
- Baseline Opens are excluded from the Push Influence calculation.
- The Push Influence algorithm is more likely to attribute an open as “Influenced” the closer it occurs to the push.
The 12-hour window for App Open attribution has proven to be the most meaningful to Push Influence, when consistently applied across tens of thousands of apps in our database. Beyond 12 hours, we cannot maintain a high degree of confidence in the statistical significance of Indirect Opens vs. Baseline Opens.
Following a push notification, we typically observe a flurry of new opens above the Baseline Open Rate for a period of time. These “Influenced Opens” include both Direct Opens
The Push Influence algorithm attributes App Opens that occur within a 12-hour window of the push to this calculated metric, accounting for the Baseline Open Rate.
The further an indirect opt-in open occurs from the original send time, the less likely it is to be considered an Influenced Open.
Appendix: Push Response Terminology
- Opt-in Open
- Any app open observed by a user who has opted in to receive push notifications. The Airship SDK observes open events for all users and reports both total opens and opt-in opens.
- Direct Open
- An app open that occurs when a user interacts with a notification to open an app, e.g., taps a push notification in the notification center, lock screen, etc.
- Indirect Open
- An app open that is attributed to the presence of a push notification, but is not measured directly, i.e., the user does not tap the notification directly. Indirect opens are a derived metric which is explained more fully in Appendix: Push Influence Primer.
- Influenced Open
- The calculated number of App Opens attributed to a push notification, having occurred within a 12-hour window of the push being sent. This includes both Direct and Indirect Opens, and the algorithm subtracts expected hourly opens that are likely to have happened without the push, and also takes less credit for opens the further they occur from the push.
- Baseline Open
- App Opens that occur regularly, irrespective of push notifications being sent. Baseline Opens might also be considered a “natural” or “organic” open in that they are expected to occur even in the absence of push notifications. Baseline Opens are derived from historical open trends on an app-by-app basis, and are excluded from Push Influence attribution.