Configure Triggers

A trigger is an event that initiates an automation or journey. This page details each trigger, as well as cancellation events, conditions, and rule limits.

See also:

Configuring Triggers

You configure a single trigger in the Setup step in an automation or the Trigger step in a journey.

  1. Select a trigger.
  2. Set any additional options that apply to the trigger.
  3. (Optional) Configure settings that apply to the automation or journey: cancellation events, conditions, and rule limits.

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.

In the Setup step in an automation or Trigger step in a journey:

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

Do not set tag conditions for custom events attributed to named users. An automation or journey specifying tag conditions for a custom event attributed to named users will never run.

 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. See Location Triggers for more information and the Location Triggers Tutorial for detailed usage steps.

Custom Event Filtering

When configuring the Custom Event trigger or Cancellation Events, you can filter your 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

Acceptable values and operators for event properties are based on the project's settings. See: Manage Event Properties.

  1. Click ADD PROPERTIES/VALUES for the custom event.
  2. Click Add Property or Add Event Value.
  3. Select the operator you want to use to evaluate the value or property, and enter the value or property you want to filter for.
  4. (Optional) Click to add an alternative for a filter.
  5. (Optional) Click Add Property or Add Event Value to add more filters.
  6. 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)
  7. Click Save.

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.

In the Setup step in an automation or Trigger step in a journey, select the First Seen trigger.

 Important

  • Users added to Airship through an Inline List An ad-hoc, CSV-formatted list of email, SMS, or open channel addresses that you want to register and/or send a message to. Unlike static lists or segments, you upload this list while creating your message. or the create-and-send API Used to simultaneously register and send a notification to email, sms, or open channels; synonymous with the Upload Users feature. API are purposely excluded from the First Seen trigger, preventing them from receiving duplicate messages when added to the system.

  • The First Seen trigger requires a delay of at least one hour to ensure delivery. In the Delivery step in an automation or when composing a message in a journey, you must specify a delay of at least one hour.

Inactivity

The Inactivity trigger initiates an automation or journey when a member of your audience does not use your app 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 activity by the user.

In the Setup step in an automation or Trigger step in a journey:

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

Location

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.

 Note

  • The Location trigger requires Gimbal integration.
  • The Location trigger is not supported for web push notifications.

In the Setup step in an automation or Trigger step in a journey:

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

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.

 Note

  • The Location Attributes trigger requires Gimbal integration.
  • The Location Attributes trigger is not supported for web push notifications.

In the Setup step in an automation or Trigger step in a journey:

  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 will be triggered if the location attributes meet ALL the attributes you entered. For example, if you selected ALL, with attributes half_off and has_cafe, you’d only reach users who entered or exited a location that met both of those conditions. If you selected ANY, you’d reach all users who entered a location running a half-off campaign as well as all users who entered a location that has a cafe.

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

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

  • Predictive Churn tags are available to customers who purchase predictive analytics as an add-on to either a Performance Analytics or Real-Time Data Streaming pricing plan. Contact Airship Sales for details.
  • Go to Settings » Configuration » Predictive AI to enable Predictive Churn features.

In the Setup step in an automation or Trigger step in a journey:

  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.

Tag Change

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

In the Setup step in an automation or Trigger step in a journey:

  1. Select the Tag Change trigger.
  2. Use the Tags box to search for a tag. If the tag you search for does not appear, click Create [search term] to create a new tag.
  3. Choose whether to apply the trigger when the tag is added or removed.

Cancellation Events

Cancellation events are events that prevent an automation from sending a message if a custom event occurs while the automation is in a delay period. Cancellation Events is in the Options section after you select your trigger. Not supported for the Inactivity trigger.

After configuring your trigger in the Setup step in an automation:

  1. Enable Cancellation Events.
  2. Complete the same workflow used for the Custom Event trigger. This includes the option to filter the cancellation events.
 Important

Cancellation events require a delay of at least one hour to ensure that there is time for the cancellation event to occur after the original triggering event occurs. In the Delivery step in an automation, you must specify a delay of at least one hour.

Conditions

Conditions are tags that must or must not be present on a device (or channel_id) for members of your audience to receive a message from an automation or journey. The message is not sent if your conditions are not met. You can search for tags, tag groups, Predicted to Churn risk profiles, and device property tags.

In an automation, Conditions appears in the Options section after you select your trigger, and you must enable the option before you can configure it. In a journey, Conditions are on the first screen when composing a message.

After configuring your trigger in the Setup step in an automation or when composing a message in a journey:

  1. Choose whether Any or All of the tag conditions must be satisfied before the message is sent.
  2. Choose whether audience members must have or not have the tag to receive the message.
    • Has: The device must have the tag to receive the message.
    • Doesn’t Have: The device must not have the tag to receive the message.
  3. Use the Tags box to search for a tag. To filter results, click and select Tags or a specific tag group. From the search results box, you can:
    • Select a tag. A tag's tag group, if any, is listed below the tag name.
    • Select a tag group from the dropdown menu.
    • Click to create a new tag.
  4. (Optional) Click Add another condition to add more conditions.
 Warning

Do not set tag conditions for custom events attributed to named users. An automation or journey specifying tag conditions for a custom event attributed to named users will never run.

Rule Limits for Automation

Rule limits cap the number of messages any member of your audience can receive from an individual automation, helping prevent you from over-notifying your audience, e.g., a maximum of 4 messages every 10 hours. Rule limits are set per automation. Rule Limits appears in the Options section after you select your trigger.

After configuring your trigger in the Setup step in an automation:

  1. Enable Rule Limits.
  2. Click Add a Daily Limit and/or Add an All-Time Limit and enter the maximum number of times a member of your audience can trigger your automation.

Your project-level Automation Limits Limits that cap the number of automated messages a device can receive within a time interval, helping prevent you from over-notifying your audience, e.g., a maximum of 4 messages every 10 hours. Each automation and each message in a journey counts toward your automation limit. Automation limits are set at the project level. and a link to edit those limits appear at the bottom of the pane.

Rule Limits for Journeys

Rule limits cap the number of times any member of your audience can trigger a journey, helping prevent you from over-notifying your audience, e.g., a maximum of 1 per day. Rule limits are set per journey. Rule Limits appears in the Options section after you select your trigger.

After configuring your trigger in the Trigger step in a journey, click Add a Daily Limit and/or Add an All-Time Limit and enter the maximum number of times a member of your audience can trigger the journey.