Sequence triggers
A trigger is an event that initiates an automation or sequence. This page details the triggers and options for sequences.
Configuring a sequence trigger
You configure triggers in the Journey MapA visualization of messaging components that can be connected to create a continuous user experience. You can also create and edit from the map. . Select a sequence, then you can add, edit, or remove triggers.

If a sequence does not have a trigger configured:
- Click its trigger card.
- Click .
- Select and configure a trigger.
- (Optional) Under Conditions, build a SegmentA grouping of audience members selected by unique or shared identifiers. Multiple identifiers can be combined within a segment. to filter the audience members entering the sequence. Creating a segment here uses the same segmentation data and procedure as in the Segment builder. Conditions are not available for the Inactivity or Manual Entry triggers.
- Click Save.
To add another trigger, click below a configured trigger. Adding more triggers to an existing sequence does not require publishing changes. To delete a trigger, click its card, then click .
You can configure up to 10 triggers unless you are using the Inactivity trigger.
You can also edit the trigger for draft and paused sequences:
- Click a trigger card.
- Click .
- Make your changes.
- Click Save.
You can route users to a sequence when an In-App AutomationMessages 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. , SurveyQuestion-and-answer experiences used to collect and aggregate feedback or generate a net promoter score. They 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. , or 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. is displayed on a device or when they click a button in the message/survey/scene. See: Create a journey: Connecting components.
Triggers
Supported triggers per channel:
Trigger | App | Web | SMS | Open | |
---|---|---|---|---|---|
Custom Event | ✓ | ✓ | ✓ | ✓ | ✓ |
Date Attribute | ✓ | ✓ | ✓ | ✓ | ✓ |
First Seen | ✓ | ✓ | ✓ | ✓ | ✓ |
Inactivity | ✓ | ✓ | |||
Location | ✓ | ||||
Location Attributes | ✓ | ||||
Manual Entry | ✓ | ✓ | ✓ | ✓ | ✓ |
Predicted to Churn | ✓ | ✓ | |||
Recurring Schedule | ✓ | ✓ | ✓ | ✓ | ✓ |
Specific Date and Time | ✓ | ✓ | ✓ | ✓ | ✓ |
Subscription | ✓ | ✓ | ✓ | ||
Tag Change | ✓ | ✓ | ✓ | ✓ | ✓ |
Custom Event
The Custom Event trigger initiates an automation or sequence when a custom event associated with members of your audience occurs. See: Custom Events.
Configuration steps:
- Select the Custom Event trigger.
- 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.
- (Optional) Click Add Another to add more events. Airship handles multiple events as a boolean OR.
- (Optional) Follow the Filtering Custom Events steps to add custom event filters.
- (Optional) Set the maximum age for the events. If an event is received after it is older than a certain age, the automation or sequence will not start.
- Enable Event Expiration.
- Enter a value in minutes, hours, days, months, or years.
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 value125.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.
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.
Acceptable values and operators for event properties are based on the project’s settings. See: Manage Events.
- Click Add event properties for the custom event.
- Click Add property and search for a property, or click Add event value.
- If applicable, select the operator you want to use to evaluate the value or property.
- Enter or select the value you want to filter for.
- (Optional) Click to add an alternative for a filter.
- (Optional) Click Add property or Add event value to add more filters.
- 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)
- 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:
- Search for or enter the property name
region
. - Select operator File upload (is one of).
- Upload a
.txt
file containing valuesnorthwest-usa
andsouthwest-usa
.
Provide your values in a line delimited .txt
file. Each value must be on a separate line. 100KB maximum file size.
Date Attribute
The Date Attribute trigger initiates a sequence for your entire audience or for a specified segment based on the month and day of a date attribute. You can enter your selected audience into the sequence on the next occurrence of the actual attribute date or a number of days before or after the date. See also: See also: Segmenting your audience and AttributesMetadata that you can use for audience segmentation. Attributes differ from tags in that when evaluating users with attributes, Airship uses operators, e.g., equals, less than/greater than, contains, before/after, to determine whether or not to target a user. Supported attribute types are TEXT, NUMBER, and DATE. .
Segmentation data is evaluated at send time. For example, if your sequence targets an audience list whose members change over time, it is sent to the current version of the list when the sequence is triggered.
Configuration steps:
- Select the Date Attribute trigger.
- Select your audience: all users or a segment.
- (Segment audience only) Search for and select a segment. You can click View segment details to confirm the audience in a new window.
- Set when the audience should start the sequence.
- Search for and select a date attribute.
After saving, you can click the trigger card to view the segment name and scheduled send time relative to the attribute date. Click the name to open the segment in the Segment Builder.
First Seen
The First Seen trigger initiates an automation or sequence 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 sequence when users first open your app.
- Web, SMS, and open channels: Triggers the automation or sequence when users opt in to notifications.
- Email: Triggers the automation or sequence when users opt in to commercial notifications.
Configuration steps:
- Select the First Seen trigger. No further setup is required.
Users added to Airship through an Inline ListAn 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 when creating your message; Airship registers new addresses in the list as channels when you send your message. or the create-and-send APIUsed to simultaneously register and send a notification to
email
,sms
, oropen
channels; synonymous with the Upload Users feature. are purposely excluded from the First Seen trigger, preventing them from receiving duplicate messages when added to the system.Automation: The First Seen trigger requires a delay of at least one hour to ensure delivery. Set a delay in the Delivery step in an automation.
Sequences: For the First Seen trigger, a delivery delay shorter than one hour is allowed but may result in dropped sends. Set a delay as the first step when creating a new message.
Inactivity
The Inactivity trigger initiates an automation or sequence 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 sequence, or b) the last app or website activity by the user.
Configuration steps:
- Select the Inactivity trigger.
- Enter the period of inactivity in days.
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
The Location trigger requires Gimbal integration.
The Location trigger initiates an automation or sequence based on an audience member’s device location. You can select a maximum of 20 locations per automation or sequence.
Configuration steps:
Select the Location trigger.
Click Select a Location.
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.
On the Results tab, check the box next to the locations you want to use as the trigger.
Review the Selections tab, then click Save and continue.
(Optional) Click Select a Location to add more locations.
Choose whether to trigger your automation or sequence when the user enters or exits a location.
Location Attributes
The Location Attributes trigger requires Gimbal integration.
The Location Attributes trigger initiates an automation or sequence based on key/value pair metadata associated with a particular location. You can add a maximum of 50 location attributes per automation or sequence.
Configuration steps:
Select the Location Attributes trigger.
Enter a key/value pair for the location you want to use as the message trigger.
(Optional) Click to add an alternative location attribute.
(Optional) Click Add Another to add more location attributes.
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 sequence is triggered if the audience meets ALL the location attributes. For example, if you selected ALL, with attributes
half_off
andhas_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.Choose whether to trigger your automation or sequence when the user enters or exits a location.
Manual Entry
The Manual Entry trigger initiates a sequence for the audience members in a specified segment. See also: Segmenting your audience.
Segmentation data is evaluated at send time. For example, if your sequence targets an audience list whose members change over time, it is sent to the current version of the list when the sequence is triggered.
Configuration steps:
- Select the Manual Entry trigger.
- Search for and select a segment. You can click View segment details to confirm the audience in a new window.
After saving, you can click the trigger card to view the segment name. Click the name to open the segment in the Segment Builder.
Next, you must enter the audience into the sequence before they can start receiving messages. In the journey map, locate your sequence, then:
- Click the trigger card for the sequence.
- Click Enter and confirm entering the audience into the sequence.
- Enter is not available unless the sequence has been started.
- If you enter a segment into the sequence more than once, the users may receive messages from the sequence more than once.
- Click on the trigger card to change the selected segment.
Predicted to Churn
The Predicted to Churn trigger initiates an automation or sequence 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.
To enable Predictive Churn features, go to Settings » Project configuration and click Manage for Predictive AI.
Configuration steps:
Select the Predicted to Churn trigger.
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.
Choose whether to apply the trigger when the risk is added or removed.
Recurring Schedule
The Recurring Schedule trigger initiates a sequence for the audience members in a specified segment periodically at specified intervals. You can also set an end date for the sequence and exclusion periods. See also: Segmenting your audience.
Segmentation data is evaluated at send time. For example, if your sequence targets an audience list whose members change over time, it is sent to the current version of the list when the sequence is triggered.
Configuration steps:
Select the Recurring Schedule trigger.
Search for and select a segment. You can click View segment details to confirm the audience in a new window.
Specify the delivery interval by number of hours/days/weeks/months/years. For weeks, also specify which days of the week when the sequence will be triggered.
Set the initial date to trigger the sequence.
Set the initial time and time zone to trigger the sequence.
(Optional) Specify when the sequence can no longer be triggered.
- Enable End Date.
- Enter a date.
- Set the time and time zone.
(Optional) Specify dates or days of the week when the sequence should not be triggered. If you select the hours interval, you can also specify which hours of the day should be excluded. If you select the weeks interval, you can only specify which dates should be excluded.
If the scheduled date and time fall during an excluded period, Airship waits to trigger until the next available valid time. For example, if you scheduled weekly on Thursdays but added the date for Thanksgiving Day as an exclusion, the next available trigger time would be the Thursday after Thanksgiving Day.
- Enable Do not send.
- Click Add date exclusion, enter a date, and repeat for additional dates.
- Click Add day exclusion and select days.
- Click Add time exclusion and set start and end times.
After saving, you can click the trigger card to view the segment name, interval, and initial scheduled date and time (UTC). Click the name to open the segment in the Segment Builder.
Specific Date and Time
The Specific Date and Time trigger initiates a sequence for the audience members in a specified segment at a set date and time. See also: Segmenting your audience.
Segmentation data is evaluated at send time. For example, if your sequence targets an audience list whose members change over time, it is sent to the current version of the list when the sequence is triggered.
Configuration steps:
- Select the Specific Date and Time trigger.
- Enter a date in YYYY-MM-DD format and select the time and time zone.
- Search for and select a segment. You can click View segment details to confirm the audience in a new window.
After saving, you can click the trigger card to view the segment name and scheduled date and time (UTC). Click the name to open the segment in the Segment Builder.
Subscription
The Subscription trigger initiates an automation or journey when a member of your audience opts in to or out of a subscription list. Lists enabled for Auto opt-in are not available for this trigger. See: Auto opt-in.
Configuration steps:
- Select the Subscription trigger.
- Search for and select at least one list.
- 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 sequence when a tag is added or removed from a device.Configuration steps:
- Select the Tag Change trigger.
- 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.
- (Optional) Click Add Another to add more tags. Airship handles multiple tags as a Boolean OR.
- Choose whether to apply the trigger when a tag is added or removed.
Trigger options
- Go to Journeys and select a sequence.
- Click .
- Click Settings in the header.
- Select the Trigger tab.
- Configure one or more of the trigger options described below.
- Click Next, then Save & Continue.
You will return to the Sequence ManagerA preview of the messages in a sequence, 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 sequence can deliver messages to your audience.
- Enable the Start Date and/or End Date options.
- Click the date field and either use the date picker, or enter a date in YYYY-MM-DD format.
- 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 sequence, preventing you from over-messaging your audience, e.g., a maximum of 1 per day. Rule limits are set per sequence 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 sequence.
Categories