Optional Delivery Features

When composing a Message, Automation, or A/B Test, you can select from many optional delivery features. Each feature's purpose and settings are detailed here. See the Message Reference for API equivalents.


Available features are dependent on which message types and platforms are selected.



Discard your message if it hasn't been delivered or displayed by a specific time. Toggle to enable, then select the radio button for either Duration or Date & Time.

  • Duration: Enter the number of minutes, hours, or days past your defined send time to expire the delivery.

  • Date & Time: Enter the date and time when delivery attempts should cease.

Push Notifications
If a device is online, the notification will be delivered immediately. If a device is offline, the push service for each platform, e.g., APNs for iOS and FCM for Android, preserves the notification and attempts to deliver it as soon as it comes online, up until the expiration date.

For Web Notifications, if no expiration is set and a device is offline, the delivery service, e.g., Google or Mozilla, preserves the notification and attempts to deliver it as soon as it comes online, for a maximum of 28 days.

There is no way to remove a delivered Push Notification.

In-App Messages
Since In-App Messages are delivered via push notifications, they will not be delivered past the expiration date if the user has been offline. In addition, Urban Airship will not display an In-App Message past the expiration date.

Campaign Categories

Assign Campaign Categories to group messages of a similar type or messaging strategy for aggregate reporting. You can then track the efficacy of both your individual messages and a messaging campaign as a whole.

Togle to enable, enter a campaign category name, then click Add. Click the X next to any category to remove it. Category names have a 64-character maximum. Enter up to ten.


Campaign Categories are listed in the Message Detail section of Message Reports.

Custom Keys

Set Custom Keys, also known as key/value pairs, pass extra data through your push notification payload for use by custom code in your app. Common uses of custom keys include passing additional campaign identifiers for analytics, passing user profile information to the device, controlling the look and feel of the app, providing image links, etc.

Enable via toggle, make your platform selection from the dropdown menu, then enter the key and value. Click Add Another for additional keys.

By default, a custom key is sent to push notifications on all platforms, but you can choose platform-specific keys as well if your message is going out to more than one platform, e.g., one imageURL for iOS and another imageURL for Android.

iOS Only

Background Processing

Wake the app and give it some running time to perform work, such as downloading content for future display. Data included in the push notification is available for background processing, e.g., to send URLs and then download that content. Enable via toggle.

Mutable Content

Allow a push notification’s content to be changed or downloaded before delivery. Automatically enabled if media is defined in Content » Optional Features » Media. Enable via toggle. iOS 10+ only.


Group multiple related notifications from your app into a single stack. Enable via toggle, then type an identifier in the text field. iOS 12 only.


Remember to use the same identifier for subsequent messages you wish to group.


Send the notification as a Critical Alert. Critical Alerts play sounds that ignore Do Not Disturb and the device’s mute switch. Enable via toggle, then use the slider to select the alert volume level. Volume can be specified at 10% increments. iOS 12 only.


  • Critical alerts require a special entitlement issued by Apple, so not all users will see this option in the dashboard.

  • These notifications should contain information that require a user to take immediate action.

  • Critical Alerts must be allowed by a user on their device.

Android & Amazon Only

Collapse Key

Suppress previous messages sent with the same key. Only the most recent message (using the same key) will be viewable. Enable via toggle, then type the key in the text field.

Delay While Idle

Delay delivery of your message until FCM detects that the device is active. This is a potential way to increase the likelihood of the user engaging with the notification. Enable via toggle.

Delivery Priority

Send your notification using Firebase Cloud Messaging (FCM) high priority. When not enabled, messages default to normal priority. Enable via toggle. Android only.


From Google's About FCM Messages: Delivery options: Setting the priority of a message:

High priority. FCM attempts to deliver high priority messages immediately, allowing the FCM service to wake a sleeping device when necessary and to run some limited processing (including very limited network access). High priority messages generally should result in user interaction with your app. If FCM detects a pattern in which they don't, your messages may be de-prioritized.

Web Only

Require Interaction


Support for Require Interaction varies by browser and OS.

Requires a user to interact with your notification in order to remove it from their computer screen. Enable via toggle.

Users may interact with a web notification in these ways:

  • Click the notification, which opens the message-defined URL, or the default Action URL.
  • Dismiss the notification.
  • Click the Settings icon or button on the notification.

SMS Only


Discard your message if it hasn't been delivered to the device by a specific number of hours. 72 hours is the default. Enter the number of hours, between 1 and 72.