From the Urban Airship dashboard, click the Messages dropdown menu, and select Messages Overview.
The view defaults to the History tab, which lists messages that you have already sent. Please note that this only includes messages that were delivered immediately. See the Automated tab for reports on Automated messages.
Click a Reports action icon at the end of a message row.
- Eye = Preview Report
- Expands the row, displaying metrics from the Message Report. Click the icon again to collapse the preview. Available metrics vary per message type. Click the question mark icon next to each for its definition.
- Histogram = View Full Report
- Opens the full Message Report. To return to the History list, click your browser’s Back button or the view all messages link above the report title.
Click Expand All and Collapse All to expose and hide Preview Reports for all listed messages.
Metrics can take 10 - 15 minutes to update after our servers have received the event.
The metrics displayed at the top of the Message Report vary per message type.
Click the question mark icon next to each for its definition. The line graph
is a comparison of Influenced Opens, Direct Opens
Below the graph are four primary headings:
Notification: The message’s content. If an In-App Message was included, that heading and message content appears. See In-App Sends.
Audience: The devices that received your message, along with associated segments and tags.
Platforms: Send Distribution and Influenced Open rates, partitioned by device.
In-App Message Impressions: The number of times an in-app message is displayed, also partioned by opted-in vs opted-out. See In-App Sends.
Automated messages have an Automation heading, rather than Audience, with a summary of the message’s Trigger information, Status, and Creation and Last Modified dates and times. If the message status is changed from within the report, you must refresh the page to see the new Status under the Automation heading.
Additional headings and information will appear, depending on the message’s original configuration.
If you have Custom Events enabled, the
Event Tracking pane displays a list of events attributed, both
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
% of Total Count: Count divided by the Total Count (listed on the bottom row)
Value: The value (monetary or otherwise) generated by the event
Avg. Value: Value divided by Count
Click the Download CSV button in the Event Tracking pane to export the report.
An Automated message’s Message Report has a small panel in the upper right corner, with options to manage the message and to filter the report view.
Edit your App-level automation rule limits, which control over-notification to users who repeatedly meet automation criteria, capping automated messages per device per given time interval, e.g., a maximum of 4 messages every 10 hours.
Click the pencil icon to open your app’s Configuration settings. Click the Automation Limits tab, and make and save your desired changes. See Settings: Configuration: Automation Limits for detail.
Pause/Resume, Cancel, Edit, Duplicate
Active messages have the option to Pause. Paused messages have the option to Resume.
Cancel deletes the messsage.
Edit opens the message for editing.
Duplicate creates a copy of the message and opens it for editing. You must complete the composer steps in order to send the new message.
Make your selections from the date range and frequency dropdown menus. The report updates after each change.
If you send a message with In-App Messaging, the associated Message Report will contain In-App Message Sends metrics.
These metrics represent the number of in-app and silent sends associated with a push. Silent sends are via Background Processing; see Delivery: Optional Features: iOS Only for Message, Automation, and A/B Tests composers.
An In-App Message Send is logged for these scenarios:
An in-app message, with or without an associated push, is sent to an opted-out device. Because opted-out devices will only receive the in-app message, this is counted as an In-App Send.
An in-app message only is sent to an opted-in device.
An in-app message combined with a push notification that is sent to an opted-in device will always be counted as a Notification Send rather than an In-App Send.
In-App Message information appears in three locations in a Message Report:
Above the line graph.
The In-App Message heading below Notifications.
Contains the in-app message text. This section is only included for in-app message only sends, or in-app messages combined with push notifications where the push notification text differs from the in-app message text.
In-App Message Impressions in the bottom right corner.
An In-App Message Impression is logged when a user encounters an in-app message. Either of the two scenarios that result in an In-App Message Send being logged will most likely also result in an Impression on open, assuming a user opens the app before the in-app message expires.
Below the Total Impressions count is a breakdown by opt-in status.
An in-app message combined with a push notification that is sent to an opted-in user can also result in an Impression; if the user opens the app without tapping the push notification, the in-app message will still display, counting as an Impression.