Actions

Actions determine what happens when a user interacts with your App and Web messages.

About actions

With actions, you gain much greater control of your users' experience with your app, and can not only provide them with more relevant, specific content, you can learn from their usage and continue to do so over time.

You set an action for all Push NotificationsA message that can appear on any screen on a mobile device. Push notifications appear as banners. , In-App MessagesA message that appears inside of your app. You can send in-app messages to your entire app audience, not just users who have opted-in to push notifications. , and Web Push NotificationsA message that slides into the top right or bottom left corner of your audience’s web browser (depending on the browser). On a mobile device, web push notifications appear similar to a push notification. , and you associate actions with your buttons and images in Rich PageA landing page or Message Center message in your app that can include HTML, video, etc. content. After selecting an action, you can set up adding or removing TagsMetadata that you can associate with channels or named users for audience segmentation. Tags are generally descriptive terms indicating user preferences or other categorizations, e.g., wine_enthusiast or weather_alerts_los_angeles. Tags are case-sensitive. when the notification, button, or image is pressed or clicked.

Adaptive Link opens a mobile wallet pass. Select an Adaptive LinkA vendor-agnostic, shortened mobile wallet pass link that supports templates for both Google Pay and Apple Wallet. When a user taps the link, Airship determines the user’s platform and generates the right pass for that platform. from the list.

App Rating

App Rating prompts the user to rate the app in the app store. Optionally enter a custom message title and body.

 Note

App Rating display behavior differs by operating system and version:

App rating prompts will process as configured by your message settings, but the displayed dialog is controlled by Apple, not Airship.

 Important

iOS requires that you provide your app’s Apple ID, which is used as the iTunes App Store Identifier. (Android and Amazon generate app store links automatically based on information already in your app, so no configuration is required.)

You can do this by adding the ID in your Airship project settings, or by editing your plist dictionary.

In your plist dictionary, add the following, substituting 1111111111 with the app’s actual ID:

<key>itunesID</key
<string>1111111111</string>

A quick way to find the Apple ID is to copy the numbers at the end of the app’s iTunes URL. If the URL is https://itunes.apple.com/app/id123456789, the Apple ID is 123456789.

Another way is to locate your app in iTunes Connect and copy the Apple ID.

Deep Link opens a screen in your app or website. Select a deep link from the list.

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 are example template URLs:

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

yourapp://products/{Product Id}

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:

http://yourcompany.com/products/1872983490

yourapp://products/1872983490

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

Dismiss Message

Dismiss Message closes the notification.

Home

Home opens your app’s home screen. For web push notifications it opens your Default Action URL. You can override the default URL by selecting the Web Page action and entering a different URL.

Landing Page

Landing Page opens a Landing page.

 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 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.

See UAActionArguments for more detail on the methods involved with this display behavior.

Message Center

Message Center opens a Message Center message. See: Message Center content.

Share

Share prompts the user to share your message with apps, social media accounts, and other services. Enter the text you want to accompany the share, including any promotional information, shortened links, hashtags, etc.

Web Page

Web Page opens 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.

Availability

For app and web messages, you set an action in the Content step of a composer.

Actions for push notifications and in-app messages:

  • Home
  • Dismiss Message
  • Message Center
  • Landing Page
  • Deep Link
  • Adaptive Link
  • Web Page
  • Share

Actions for web push notifications:

  • Home
  • Adaptive Link
  • Web Page

When creating landing page and Message Center content, you can assign an action that occurs when a user taps a button or image in the message. Options vary between the Interactive and Visual editors.

Actions in the Interactive editor — See: WYSIWYG editor: Rich Page Actions

  • Adaptive Link
  • Deep Link
  • Share
  • Web Page
  • App Rating

Actions in the Visual editor:

  • Deep Link
  • Share
  • URL (Web Page)

Disable actions

You can disable actions (except for Home) from appearing in the composers: Go to Settings » Project Configuration and click Manage for Dashboard Settings, then disable Landing Page, Deep Link, URL, and Add Tags (UA Actions Framework).