Set Event Triggers

Choose the events that will send your Automated message to members of your audience. This page details the available triggers and the options that appear when you select triggers.

Setting Event Triggers

Event triggers are events that cause an automation to send messages to individual members of your audience. You set a single event trigger during the Setup step of the Automation composer.

  1. Select an event trigger.
  2. Set any additional options that apply to the trigger.
  3. (Optional) Set additional Automation options.

Custom Event

A Custom Event event trigger causes Automation to send a message to your audience when custom events associated with members of your audience occur. See: Custom Events.

In the Setup step of the Automation composer:

  1. Select the 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 custom event triggers. Multiple event triggers are handled as a Boolean OR.
 Warning

An automation pipeline with tag-based operations and custom event triggers attributed to named users will not 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 Event trigger. See the Intro to Automation: Location Triggers for more information and the Location Triggers Tutorial for detailed usage steps.

Filter

When setting Custom Event triggers, 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.

After configuring the Event trigger in the Setup step of the Automation composer:

  1. Click ADD PROPERTIES/VALUES for the custom event.
  2. Click Add Property or Add Event Value.
  3. Choose from the dropdown menu and complete the filter. For Properties, click Search for Properties, enter a search term, and select from the listed results.
  4. Set the property or value for your event filter and the operator determining how you want to evaluate the property or value.
  5. (Optional) Add an alternative by clicking the plus sign icon at the end of a row.
  6. Select ALL/ANY to determine how to evaluate multiple filters. This determines not only multiple filters, but also alternatives within each filter.
    • ALL = all criteria must be met (Boolean AND)
    • ANY = any criteria must be met (Boolean OR)
       Note

      If set to ALL, filters with alternatives use a Boolean OR operator. If set to ANY, filters with alternatives use a Boolean AND operator.

  7. Click Save.

First Seen

A First Seen event trigger causes Automation to send a message 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:

  • Mobile apps: Triggers the automation when users first open your app.
  • Web browser, SMS, and open platforms: Triggers the automation when users opt in to notifications.
  • email: Triggers the automation when users opt in to commercial notifications.

In the Setup step of the Automation composer, select the First Seen event trigger.

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 An API through which you can simultaneously register and send a notification to email, sms, or open channels; synonymous with the inline list feature API are purposely excluded from the First Seen trigger, preventing them from receiving duplicate messages when added to the system.

 Important

The First Seen trigger requires a delay of at least one hour to ensure delivery. In the Delivery step of the Automation composer, you must specify a delay of at least one hour after the first time your audience opens the app or opts in to notifications.

Inactivity

An Inactivity event trigger causes Automation to send messages to your audience when they do not use your app for a period of time. The inactivity period begins when you create the trigger. The full inactivity period, beginning when you create the trigger, must elapse before your message is sent.

In the Setup step of the Automation composer:

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

Location

A Location event trigger causes Automation to send messages to your audience based on their device location.

 Note

In the Setup step of the Automation composer:

  1. Select the Location trigger.
  2. Configure according to the Location Triggers Tutorial.

Location Attributes

A Location Attributes event trigger causes Automation to send messages to your audience based on key/value pair metadata associated with a particular location.

 Note

In the Setup step of the Automation composer:

  1. Select the Location Attributes trigger.
  2. Configure according to the Location Triggers Tutorial.

Predicted to Churn

A Predicted to churn event trigger causes Automation to send messages to your audience when Airship predicts their 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.
  • Predicted to Churn is not supported for web push notifications.

In the Setup step of the Automation composer:

  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 either added or removed.

Tag Change

A Tag Change event trigger causes Automation to send messages to members of your audience when a tag is added or removed from a device.

In the Setup step of the Automation composer:

  1. Select the Tag Change trigger.
  2. Use the Tags box to find 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 Automation event trigger options you can set that will prevent a delayed message from being sent to your audience if a custom event occurs while the message is pending. The Options section appears below your event trigger selection, depending on the trigger you select.

After setting your event triggers in the Setup step of the Automation composer:

  1. Enable Cancellation Events.
  2. Complete the same workflow used for Custom Events. This includes the option to Filter, cancelling delivery only when a specified property or value is met.
 Important

A delivery delay is required for Cancellation Events, with a minimum of one hour to ensure that there is time for the cancellation event to occur after the original event trigger. In the Delivery step of the Automation composer, specify a number of hours or days after the triggering event occurred.

Conditions

Conditions are Automation event trigger options you can set to determine the tags that must or must not be present on a device (or channel_id) for members of your audience to receive messages. 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. The Options section appears below your event trigger selection, depending on the trigger you select.

After setting your event triggers in the Setup step of the Automation composer:

  1. Enable Conditions.
  2. Choose whether Any or All of the tag conditions must be satisfied before the message is delivered.
  3. Choose whether the device must have or not have the tag to receive the message.
    • Has = The device must have a selected tag to receive the message.
    • Doesn’t Have = The device must not have a selected tag to receive the message.
  4. Use the Tags box to find a tag. To filter results, click and select Tags or a specific tag group. From the search results box, you can:
    • Select a tag from the listed results. 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.
  5. (Optional) Click Add another condition to add additional conditions for the event trigger.
 Warning

You cannot set tag conditions if your event trigger is a custom event attributed to named users.

Rule Limits

Rule limits are Automation event trigger options you can set to determine the maximum number of messages any member of your audience can receive from an individual automation rule within a period of time. The Options section appears below the event trigger dropdown menu, depending on which trigger you selected.

After setting your event trigger in the Setup step of the Automation composer:

  1. Enable Rule Limits.
  2. Click Add a Daily Limit and/or Add an All-Time Limit
  3. Enter the maximum number of messages for your limits. For the daily limit, also specify the number of days.

Your project-wide automation rule limits, and a link to edit those limits, appear at the bottom of the pane. Automation limits control over-notification to users who repeatedly meet automation criteria, capping automated messages per device per given time interval, e.g., a maximum of 4 messages every 10 hours.