You can configure these outcomes 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. :
- Exit events
- Continuation to a new or existing sequence, in-app automation, scene, or survey
- Exit events with continuation to a new or existing sequence, in-app automation, scene, or survey
Route users to a sequence or in-app experience when Airship sends the last message in the current sequence or an exit event occurs.
Go to Journeys and select a sequence.
Click to the right of the sequence or a previously configured exit event. A configuration drawer will open.
Select Continuation. This step is eliminated if configuration is for an exit event.
Select Create new or Insert existing.
Set the delay period — the time Airship should wait before evaluating triggers and conditions for the downstream sequence or in-app experience. Enter a value in minutes, hours, or days. The maximum delay period is 90 days.
Select Sequence, Scene, Survey, or In-App Automation, then enter a name for the draft or search for an existing message. Routing to a scene, survey, or in-app automation requires minimum SDKs: iOS 17 and Android 17.
(For in-app experiences only, optional) Edit the expiration period and/or set a fallback sequence.
If the downstream in-app automation, scene, or survey does not display on a user’s device within the default period of 31 days, they will exit the JourneyA continuous user experience of connected Sequences, Scenes, Surveys, and/or In-App Automations. . This period starts after any configured delay period elapses. As an alternative to exiting, you can route to a fallback sequence. You can also set a shorter expiration period.
- Expiration — Enter a number of days.
- Fallback sequence — Search for an existing sequence or enter a name for a draft and click Create new sequence: [draft name].
The map will now show the downstream sequence or in-app experience with a connection to the upstream sequence or exit event.
Configuring exit events and optional continuation
Exit users from the sequence when an event occurs. You can set up multiple events. After configuring an event, you have the option to then route users to a sequence or in-app experience. See also: Exit events.
Go to Journeys and select a sequence.
Click to the right of the sequence. A configuration drawer will open.
Select the exit type: Cancellation Event or Conversion Event.
Select the exit event and configure.
Contact association: No configuration needed.
- Search for and select a subscription list.
- Choose whether to exit when the user opts in to or out of the subscription.
- 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 to perform the event when a tag is Added, or Removed.
Search for a custom event, then select an event from the listed results. The search shows events that occurred in the last 30 days. If your event name does not appear in the search results, 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) Filter custom events by value or key/value properties. Filtering events this way can help you more precisely target your audience.
- 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.
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.
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
midwest-usaor any other region, you would do the following to filter your custom events:
- Search for or enter the property name
- Select operator File upload (is one of).
- Upload a
.txtfile containing values
Provide your values in a line delimited
.txtfile. Each value must be on a separate line. 100KB maximum file size.
(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.
(Optional) Enable Add continuation and complete the steps above for Configuring continuation, starting at step 4.
The map will now show a connection from the sequence to the exit event.