Journey triggers

A trigger is an event that initiates an automation or journey. This page details the triggers and options for journeys.

Configuring a journey trigger

You configure triggers in the Journey MapA visualization of journeys and in-app experiences that can be connected to create a continuous user experience. You can also create and edit from the map. . Select a journey, then you can add, edit, or remove triggers.

If a journey does not have a trigger configured:

  1. Click its trigger card.
  2. Click Configure.
  3. Select and configure a trigger.
  4. Click Save.

To add another trigger, click   below a configured trigger. Adding more triggers to an existing journey does not require publishing changes. To remove triggers, click a trigger card and click Remove.

You can configure up to 10 triggers unless you are using the Inactivity trigger.

You can also edit the trigger for draft and paused journeys:

  1. Click a trigger card.
  2. Click Edit.
  3. Make your changes.
  4. Click Save.

Triggers

Supported triggers per channel:

TriggerAppWebEmailSMSOpen
Custom Event
First Seen
Inactivity
Location
Location Attributes
Manual Entry
Predicted to Churn
Subscription List
Tag Change

Custom Event

The Custom Event trigger initiates an automation or journey when a custom event associated with members of your audience occurs. See: Custom Events.

Configuration steps:

  1. Select the Custom Event trigger.
  2. Use the Events box to find an event, then click to select from the listed results. 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. (Optional) Click Add Another to add more events. Airship handles multiple events as a boolean OR.
  4. (Optional) Follow the Filtering Custom Events steps to add custom event filters.
  5. (Optional) Set the maximum age for the events. If an event is received after it is older than a certain age, the automation or journey will not start.
    1. Enable Event Expiration.
    2. Enter a value in minutes, hours, days, months, or years.
 Tip

If you are a Radar customer and have configured the Airship and Radar integration, Radar location events and properties will be available for use with the Custom Event trigger.

Filtering Custom Events

When configuring the Custom Event trigger you can filter custom events 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.

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

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.

 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.

Filtering custom events using file upload

You can use file upload to provide multiple values to match against a specified event property’s value. For string properties only.

For example, for a point-of-sale system that emits events when a sale occurs, an event might have the following data:

name: "sale-completed"
properties:
   customer_id: 234234
   store_id: 103843
   region: "northwest-usa"

To trigger only when sales occur in the regions of northwest-usa and southwest-usa but not midwest-usa or any other region, you would do the following to filter your custom events:

  1. Search for or enter the property name region.
  2. Select operator File upload (is one of).
  3. Upload a .txt file containing values northwest-usa and southwest-usa.

Provide your values in a line delimited .txt file. Each value must be on a separate line. 100KB maximum file size.

First Seen

The First Seen trigger initiates an automation or journey when members of your audience opt in to notifications or open your app for the first time. The behavior of the First Seen trigger varies by channel:

  • Apps: Triggers the automation or journey when users first open your app.
  • Web, SMS, and open channels: Triggers the automation or journey when users opt in to notifications.
  • Email: Triggers the automation or journey when users opt in to commercial notifications.

Configuration steps:

  1. Select the First Seen trigger. No further setup is required.
 Important

Inactivity

The Inactivity trigger initiates an automation or journey when a member of your audience does not use your app or website for a period of time. The inactivity period begins the later of a) the creation time of the automation or journey, or b) the last app or website activity by the user.

Configuration steps:

  1. Select the Inactivity trigger.
  2. Enter the period of inactivity in days.
 Note

The Inactivity trigger cannot be used with multiple triggers.

  • If you configure the Inactivity trigger as the first trigger, you will not have the option to add more triggers.
  • After configuring a trigger that is not Inactivity, you will not have the option to add the Inactivity trigger.

Location

 Note

The Location trigger requires Gimbal integration.

The Location trigger initiates an automation or journey based on an audience member’s device location. You can select a maximum of 20 locations per automation or journey.

Configuration steps:

  1. Select the Location trigger.

  2. Click Select a Location.

  3. Enter a search term. Results, if any, display on the map and are listed on the Results tab. There are two types of locations available for selection: geofences and beacons.

    Click a result for a detailed view of a location. If selecting a geofence, the map will zoom to the selected location. Click and drag, and use the **+/-** zoom controls to change the displayed area.
  4. On the Results tab, check the box next to the locations you want to use as the trigger.

  5. Review the Selections tab, then click Save and continue.

  6. (Optional) Click Select a Location to add more locations.

  7. Choose whether to trigger your automation or journey when the user enters or exits a location.

Location Attributes

 Note

The Location Attributes trigger requires Gimbal integration.

The Location Attributes trigger initiates an automation or journey based on key/value pair metadata associated with a particular location. You can add a maximum of 50 location attributes per automation or journey.

Configuration steps:

  1. Select the Location Attributes trigger.

  2. Enter a key/value pair for the location you want to use as the message trigger.

  3. (Optional) Click   to add an alternative location attribute.

  4. (Optional) Click Add Another to add more location attributes.

  5. Select ALL/ANY to determine how to evaluate multiple location attributes and alternatives within each location attribute.

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

    By default, the automation or journey is triggered if the audience meets ALL the location attributes. For example, if you selected ALL, with attributes half_off and has_cafe, you’d only reach users who enter or exit locations that meet both conditions. If you select ANY, you’d reach all users who enter a location running a half-off campaign as well as all users who enter a location that has a cafe.

  6. Choose whether to trigger your automation or journey when the user enters or exits a location.

Manual Entry

The Manual Entry trigger initiates a journey for the audience members in a specified SegmentA grouping of audience members selected by unique or shared identifiers. Multiple identifiers can be combined within a segment. . See also: Segmenting your audience.

 Note

You cannot schedule delivery or set rule limits for journeys using the Manual Entry trigger.

Configuration steps:

  1. Select the Manual Entry trigger.
  2. Search for and select a segment.

After saving the trigger configuration, the segment name appears in the trigger card in the journey map and in Message Details in Messages OverviewA view of all your project’s messages, journeys, and A/B tests, with options for editing their settings, content, status, and more. .

Next, you must enter the audience into the journey before they can start receiving messages. In the journey map, locate your journey, then:

  1. Click the trigger card for the journey.
  2. Click Enter and confirm entering the audience into the journey.
    • Enter is not available unless the journey has been started.
    • If you enter a segment into the journey more than once, the users may receive messages from the journey more than once.
    • Click Edit on the trigger card to change the selected segment.

Predicted to Churn

The Predicted to Churn trigger initiates an automation or journey when Airship predicts an audience member’s likelihood of becoming inactive, or churning. Predictive Churn analyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, or Low Risk.

 Note

To enable Predictive Churn features, go to Settings » Project configuration and click Manage for Predictive AI.

Configuration steps:

  1. Select the Predicted to Churn trigger.

  2. Select a risk profile.

    • High risk: Users most likely to become inactive.
    • Medium risk: Users who exhibit signs of potentially becoming inactive.
    • Low risk: Users least likely to become inactive.
  3. Choose whether to apply the trigger when the risk is added or removed.

Subscription List

The Subscription List trigger initiates an automation or journey when a member of your audience opts in to or out of a subscription list.

Configuration steps:

  1. Select the Subscription List trigger.
  2. Search for and select at least one list.
  3. Specify whether to trigger when users opt in to, or opt out of, the list.

Tag Change

The Tag Change trigger initiates an automation or journey when a tag is added or removed from a device.

Configuration steps:

  1. Select the Tag Change trigger.
  2. Search for a tag. If the tag you search for does not appear, click Create [search term] to create a new tag. You can select a tag group filter before or after searching.
  3. (Optional) Click Add Another to add more tags. Airship handles multiple tags as a Boolean OR.
  4. Choose whether to apply the trigger when a tag is added or removed.

Trigger options

You configure trigger options in Journey Settings. Options do not appear if using the Manual Entry trigger.

  1. Go to Journeys to open the Journey MapA visualization of journeys and in-app experiences that can be connected to create a continuous user experience. You can also create and edit from the map. , and select a journey.
  2. Click Manage.
  3. Click Journey Settings in the header.
  4. Select the Target tab.
  5. Configure one or more of the trigger options described below.
  6. Click Next, then Save & Continue.

You will return to the Journey ManagerA preview of the messages in a journey, with options for editing and testing, and for running experiments. . You can start adding messages, or click Exit   » Save and exit to return to the map.

Automatic start and stop dates

Start and end dates define the times during which an automation or journey can deliver messages to your audience.

  1. Enable the Start Date and/or End Date options.
  2. Click the date field and either use the date picker, or enter a date in YYYY-MM-DD format.
  3. Select the time and time zone.

Frequency limits: Ignore Channel Message Limits

Enable this option to override the project-level Message LimitsLimits that cap the number of messages you can send within a specified time frame, preventing you from over-messaging your users. They are set at the project level. , ensuring that your audience will receive your message even if they’ve reached the message limit. Overriding message limits does not override Rule limits (see below).

Frequency limits: Rule Limits

Rule limits cap the number of times a named user can trigger a journey, preventing you from over-messaging your audience, e.g., a maximum of 1 per day. Rule limits are set per journey and apply at the named user level. Rule Limits appears in the Options section after you select your trigger.

Click Add a daily limit and/or Add an all-time limit and enter the maximum number of times a named user can trigger the journey.