When creating a Message, Automation, A/B Test, or Journey you must choose a message action. You will also associate an action when creating a rich page A landing page or Message Center message in your app that can include HTML, video, etc. . Available actions differ depending on the message type or combination of message types. See: Message Reference: Actions.
Each action and its settings, configuration, and requirements are detailed here.
Only Adaptive Links created in the dashboard will appear in the dropdown list.
Deep Link opens a screen in your app or website. The Deep Link must be configured before it will appear in the dropdown menu. See: Manage Deep Links.
If you selected a Deep Link template, you can fill in each template segment. If no deep links have been predefined, you will see a link to the configuration documentation.
Deep Link Templates
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:
When you enter this URL in the Airship interface, the form parses it and previews the form your users see in the composer. 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:
The interface treats all values for each field as a string.
See: Manage Deep Links.
Home opens the app's home screen. For web push notifications it opens the Default Action URL.
Landing Page opens a rich page A landing page or Message Center message in your app that can include HTML, video, etc. that appears until it is closed. Follow the steps in Create Rich Pages. See also: Rich Page Reference.
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 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
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.
Message Center opens a rich page A landing page or Message Center message in your app that can include HTML, video, etc. that is saved in the user's Message Center A place in your app where you can display persistent rich messages, including HTML, video, etc. Similar to email, Message Center represents both the medium (the in-app inbox) and the message type (the messages you send to a message center). inbox. Follow the steps in Create Rich Pages.
Share prompts the user to share your message on social networks. Enter the text you want to accompany the share, including any promotional information, shortened links, hashtags, etc.
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.