Message Actions

When creating a Message, Automation, A/B Test, or Push Template, you must choose which Action occurs after a user clicks, taps, or swipes your message. Each action and its settings, configuration, and requirements are detailed here. See the Message Reference for API equivalents.

Actions listed in the dropdown menu differ depending on the message type or combination of message types. See: Message Reference: Actions.

Actions

Home

Home opens the web Default Action URL and the app's home screen.

Home (combined)

This action is available when you have combined a Push Notification with an In-App Message.

Home opens the app's home screen for a Push Notification, and dismisses the In-App Message.

Message Center

Message Center opens a rich page that is saved in the user's Message Center inbox. See Rich Pages for more information and an example Message Center image.

Click the Create button to create a new Rich Page. Usage steps are in the Rich Content Editor Tutorial.

Landing Page

Landing Page opens a rich page that appears until it is closed, and it is not stored in the user's Message Center inbox. See Rich Pages for more information and an example Landing Page image.

Click the Create button to create a new Rich Page. Usage steps are in the Rich Content Editor Tutorial.

Note

The default behavior in the iOS SDK is to not display the Landing Page when the corresponding push notification is received while the app is in the foreground state. The logic behind this behavior is that you may not wish to interrupt or distract a user who is currently occupied with the app, only to ask them to visit a different part of the app.

If you need to display a Landing Page while the app is in the foreground state, replace the registry predicate associated with that action with one that allows foreground execution.

In the Urban Airship SDK, this relative state between what the app is doing now and how the action was invoked is known as a situation, or more properly, UASituation. Other examples of situations besides foreground state include background push and app launched from push notification.

Please see the UA Action Arguments Class Reference for more detail on the methods involved with this display behavior.

Deep Link opens to a configured screen within your app or on the web. The Deep Link must be configured before it will appear in the dropdown menu. See: Settings: Configuration: Deep Links.

If you selected a Deep Link template, each template segment field will be available to fill in. If no deep links have been predefined, you will see a link to the configuration documentation.

You can also provide a Deep Link from a Landing Page or Message Center rich page. See Rich Content Editor: Action Links: Deep Link for set up instructions.

Our Deep Link functionality supports URL templates, which expose a friendly interface to your users in our UI, while constructing the correct URL behind the scenes on the fly. You can specify substitution parameters by enclosing them in brackets. For example, if you want to define a Deep Link for a product page screen in your app (or on your mobile website), you can make the product ID number a substitution parameter. Here is an example URL:

http://yourcompany.com/products/{Product Id}

When you enter this URL in the Urban Airship interface, the form parses it and previews the form your users see in the Message Workflow. It automatically identifies “Product Id” as the parameter name, and provides a field to substitute in the actual identifier. So if you had previously entered a product ID of 1872983490 for the above Product ID, the generated URL would be:

http://yourcompany.com/products/1872983490

The interface treats all values for each field as a string.

See: Settings: Configuration: Deep Links.

Adaptive Link opens a mobile wallet pass. The Adaptive Link must be configured before it will appear in the dropdown menu. See: Adaptive Links: Setup and Modification. Select from the dropdown menu.

Note

Only Adaptive Links created in the dashboard will appear in the dropdown list.

Web Page

Web Page opens to a web page or any valid-device level URL such as App Store or app protocol links. The web page opens in the device's default browser. Enter a URL.

You can also provide a Web Page URL from a Landing Page or Message Center rich page. See Rich Content Editor: Action Links: URL for set up instructions.

Share

Share prompts the user to share the message on social networks. Enter the text you would like to accompany the share, including any promotional information, shortened links, hashtags, etc.

You can prompt a user to Share in two additional places:

  1. A Landing Page or Message Center rich page. See Rich Content Editor: Action Links: Share for set up instructions.

  2. An Interactive Notification button. See: Optional Features.

Rich Pages

Rich Pages include HTML, video, etc., and are created as part of the message creation for the Message, Automation, and A/B Test workflows.

Rich Pages are used with the Action types Landing Page and Message Center, however Message Center is not available in A/B Tests.

From the mobile user perspective, the key difference between a rich page in Landing Pages and Message Center is the navigational chrome:

  • Landing Pages open as an overlay with a Close (X) button, which takes the user to the app's home screen. A Landing Page is not persistent, i.e., does not remain available for later viewing within the Message Center UI. Example:
  • Message Center messages open in the Message Center context, which contains navigation back to the Message Center inbox. Example, with Inbox navigation:

See our Support article for more about Landing Pages and Message Center messages. The Rich Content Editor Tutorial documents how to create rich pages.

Actions from Rich Pages

Rich pages can be configured with buttons that perform these actions:

  • Deep Link
  • URL
  • Share

See Rich Content Editor: Action Links for setup instructions.