In-App Automation Triggers

A trigger is an event that causes an In-App Automation message to appear to your audience.

Triggers

You configure a trigger in the Behavior step in an in-app automation.

App Open

The App Open trigger causes an In-App Automation message to appear based on the number times your audience opens your app.

In the Behavior step of the In-App Automation composer:

  1. Select the App Open trigger.
  2. Enter the number of times your audience must open your app to before the message will appear.

App Open display timing varies depending on whether users have opened the app before or currently have the app open. For a message with App Open value of 1:

  • If a user has never opened the app before, they will see the message the first time they open the app.
  • If a user has opened the app before and does not currently have the app open, they will see the message the next time they open the app.
  • If a user currently has the app open, the message will appear during the current session.
 Tip

If you are configuring a “Welcome” message intended to display when users first open your app:

If you want an onboarding message to appear the third time users open your app, set the App Open trigger value to 3.

App Update

The App Update trigger causes an In-App Automation message to appear when your audience opens your app some number of times after an app update.

In the Behavior step of the In-App Automation composer:

  1. Select the App Update trigger.
  2. Select All app updates or Specific app updates and then enter the number of times your audience must open your app before they will see your message.
  3. If you selected Specific app updates, you must set versions for each of your app’s platforms. For each platform:
    • Select any version or the operator you want to use to evaluate specific version numbers.
    • If you selected an operator, enter the version number(s) you want to evaluate against. For Android apps, enter the versionCode; you can find your app’s versionCode in your Google Play dashboard.
 Note

The Is between operator includes boundary values, i.e., entering versions 4.3 - 5.1 includes 4.3 and 5.1.

Custom Event

The Custom Event trigger causes an In-App Automation message to appear to your audience when custom events occur (or recur some number of times).

Custom EventsEvents that indicate that a user performed a predefined action, such as adding an item to a shopping cart, viewing a screen, or clicking an Unsubscribe button. Custom events can trigger automation and journeys. You can code them into your app or website, or send them to Airship from an external source using the custom event API. Custom events contain properties that you can use to personalize messages. capture key events in your app, e.g., screen views, media views, stories read, button clicks, items purchased or added to cart.

 Note

Server-side events cannot be used to trigger an In-App Automation.

In the Behavior step of the In-App Automation composer:

  1. Select the Custom Event trigger.
  2. Use the Events box to find an event. The search shows events that occurred in the last 30 days. If the event name you search for does not appear, click Use [search term] to use the event name as typed.
  3. Enter the number of times the event must occur before the message will display.
  4. (Optional) Click Add Another to add more custom event triggers. Multiple events are handled as a boolean OR.

Filtering Custom Events

When configuring the Custom Event trigger, you can filter custom events that are set on Channel IDsAn instance representing an entity addressable via the Airship service, e.g., an iOS device, email address, SMS number or web browser. The channel instance or channel object contains all relevant information about a channel, including metadata used for targeting, opt-in status, device-specific information, and, importantly, a unique identifier for the channel, the channel ID. , using numeric values associated with those custom events, or by key/value properties attached to the events. Filtering events this way can help you more precisely target your audience.

 Note

The filter does not show events and event properties for custom events associated with named usersA customer-provided identifier used for mapping multiple devices and channels to a specific individual. . You can still use events associated with named users as triggers, but you must enter their information manually.

Example
If you have a custom event named “Purchase”, with a purchase category fedoras and a value 125.0 representing the dollar amount of the purchase, you can add these criteria to the Purchase event so that your message is only seen by users spending at least $125 on fedoras.
 Note

Acceptable values and operators for event properties are based on the project’s settings. See: Manage Events.

  1. Click Add event properties for the custom event.

  2. Click Add property and search for a property, or click Add event value.

  3. If applicable, select the operator you want to use to evaluate the value or property.

  4. Enter or select the value you want to filter for.

  5. (Optional) Click   to add an alternative for a filter.

  6. (Optional) Click Add property or Add event value to add more filters.

  7. Select ALL/ANY to determine how to evaluate multiple filters and alternatives within each filter.

    • ALL = all criteria must be met (boolean AND)
    • ANY = any criteria must be met (boolean OR)

  8. Click Save.

Screenview

The Screenview trigger causes an In-App Automation message to appear when your audience views a screen a specified number of times. You must configure app screens before you can select them as a part of this trigger. See: Manage App Screens.

In the Behavior step of the In-App Automation composer:

  1. Click Add a screen name, and find the screen you want to use for the trigger.
  2. (Optional) Click Add another screen name to specify multiple screens. Multiple screens are handled as a boolean OR.
  3. Enter the number of times your audience must view the screen before they will see your message.

Trigger Options

After configuring a trigger, you can set cancellation events and additional display conditions.

Cancellation Events

Cancellation events prevent an In-App automation from displaying a message if a custom event occurs while the In-App Automation is in a delay period or if a specific screen has been viewed. You must specify at least one custom event as a cancellation event and also at least one condition: Time Has Elapsed and/or Viewing a Specific App Screen. Cancellation events appears in the composer after selecting a trigger.

  1. Enable Cancellation Events.
  2. Complete the same workflow used for the Custom Event trigger. This includes the option to filter the cancellation events.
  3. Configure one or both conditions.

Conditions

Set conditions that determine whether or not your message displays after a trigger event occurs. The message is not displayed until your conditions are met. You must set at least one condition if you enabled Cancellation Events.

Time Has Elapsed

Set the amount of time that must elapse after receiving the triggering event before your message is eligible for display.

After setting your triggers in the Behavior step of the In-App Automation composer:

  1. Enable Time has elapsed.
  2. Enter the minimum time in seconds or minutes.

Viewing a Specific App Screen

Limit message display to when a trigger occurs while your audience is viewing a specific app screen. You must first configure app screens in your project settings before you can select them as a condition.

After setting your triggers in the Behavior step of the In-App Automation composer:

  1. Enable Viewing a specific app screen.
  2. Click Add a screen name and find the screen that you want to limit the message to.
  3. (Optional) Click Add another screen name to add additional screens. Multiple screens are handled as a boolean OR.