Button Actions

Choose the action that occurs when a user taps a button in your In-App Automated message. These are called button actions. This page details the different button actions, how to set them, and additional options.

Setting Button Actions

A button action is the action that occurs when a user taps a button in your In-App Automated message. You add buttons during the Content step of the In-App Automation composer, and you set button actions during the Actions step. You must associate an action for each button.

  1. Select a button action.
  2. (Optional) Set tag behavior.
  3. (Optional) Limit the display to once if the user taps the message.
  4. Repeat for each button.
  5. Click   to move on to the next step.

Fullscreen messages include a Footer field, which is designed to link to your Terms and Conditions, Privacy Policy, or additional information to help the user make a more informed decision about the actions they could take in the message. The footer inherits the styling of the body text and functions as a button.

It is configured in the same way as the other buttons, and they are presented in separate panes: Footer and Buttons. The actions available for the footer button are Adaptive Link, Deep Link, and Web Page.

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 App Store URL. If the URL is https://apps.apple.com/app/id1195168544, the Apple ID is 1195168544.

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

App Settings

App Settings opens the device’s settings page for the app. Available for buttons in a SceneMulti-screen experiences that are cached on users’ devices and displayed when your users meet certain conditions within your app, such as viewing a particular screen or opening the app a certain number of times. only.

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

 Tip

The default action of a button is to dismiss the message, without any other effect. For example, a “Not Now” button allows a user to defer taking action and dismisses the message, which can be configured to reappear at a later time. An effective way to pair actions is to provide a “Not Now” button with the Dismiss Action, and an additional button with the Deep Link action, providing a direct link to your content.

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:

https://yourcompany.com/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 Message 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:

https://yourcompany.com/products/1872983490

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

Dismiss Message

Dismiss Message dismisses the In-App Message.

Location Opt-in

Location Opt-in opens the system prompt for location opt-in.

Push Opt-in

Push Opt-in opens the system prompt for push notification opt-in.

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.

Set a Tag

Set a tag on the device when the button is pressed. It’s also possible to remove a tag, or combine setting and removal actions on one button press.

  1. Click Set a tag.
    Button Actions
  2. Select Add or Remove, then search for tags that exist in the system, or create a new tag.
 Tip

The ability to set tags based on user actions is key to promoting new features. The suggested approach is to display messages regarding a feature if the tag does not exist, and to then set the tag to record either the fact that the user has acknowledged the message, or to record actual usage of the feature. You can set a tag when a user clicks a button on an In-App Message, or even upon In-App Message display, but recording actual feature usage requires some native code within the app. See:

Disable Multiple Display

Keep the message from displaying more than once if the user taps the message. Check the box to enable.

Button Actions
 Tip

Use this for repeated goal-related messages, e.g., prompt to opt-in. You would want to prevent re-display when the user accomplishes the goal.