Sequence outcomes

By default, all sequence messages are delivered to users who meet the conditions, but you can configure alternative outcomes.

Possible outcomes

You can configure the following outcomes for a sequence:

• Continue to an in-app experience (In-App AutomationMessages cached on users’ devices and displayed when users meet certain conditions within your app, such as viewing a particular screen or opening the app a certain number of times. or SceneA single or multi-screen in-app experience cached on users’ devices and displayed when users meet certain conditions in your app or website, such as viewing a particular screen or when a Custom Event occurs. They can be presented in fullscreen, modal, or embedded format using the default swipe/click mode or as a Story. Scenes can also contain survey questions.) or another sequence when Airship sends the last message in the current sequence.

• Exit the sequence when a specific event occurs. When configuring the event, you designate it as a conversion or cancellation for reporting.

• Exit the sequence when a specific event occurs, then continue to an in-app experience or another sequence.

Exit events

You can configure a sequence to exit users based on these events:

• Contact association — This event occurs when an anonymous channel is associated with a Named UserA customer-provided identifier used for mapping multiple devices and channels to a specific individual..

• Tag change — End the sequence when a specified tag is added to, or removed from, a device.

• Custom event — Select an event that represents a key value exchange with your customers.

• Subscription event — This event occurs when a user opts in to or out of a Subscription ListAn audience list of users who are opted in to messaging about a specific topic. Users can manage their opt-in status per list using a Preference Center.. This exit event can only be configured 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., not the sequence settings.

Exit events are designated as either Conversion or Cancellation. Both have the same effect on a sequence, but the classifications are used for reporting and mapping. Their occurrence is evaluated during the delay period configured when adding each message.

Continuation

Configuring a sequence to continue to an in-app experience or another sequence creates a JourneyA continuous user experience of connected Sequences, Scenes, and/or In-App Automations.. You can configure the downstream component in two ways:

• Create new — After entering a name, it is saved as a draft.
• Insert existing — Search for and select a sequence or in-app experience in your project. Archived items are excluded from search results.

For downstream sequences, channel selection is eliminated since your audience is predetermined by the upstream sequence.

Routing to an in-app experience requires: iOS SDK 17+Android SDK 17+

Delay period

You can set a delay period — the time Airship should wait before evaluating triggers and conditions for the downstream sequence or in-app experience. The delay period starts after the last message in the upstream sequence is sent or when an exit event occurs. The maximum delay period is 90 days.

In-app experience expiration period

If the downstream in-app automation or scene does not display on a user’s device within the default period of 31 days, they will exit the journey. 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.

Configuring continuation

Route users to a sequence or in-app experience when Airship sends the last message in the current sequence or an exit event occurs.

1. Go to Journeys and select a sequence.

2. Click to the right of the sequence or a previously configured exit event. A configuration drawer will open.

3. Select Continuation. This step is eliminated if configuration is for an exit event.

4. Select Create new or Insert existing.

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

6. Select Sequence, Scene, or In-App Automation, then enter a name for the draft or search for an existing message. Routing to a scene or in-app automation requires: iOS SDK 17+Android SDK 17+

7. (For in-app experiences only, optional) Edit the expiration period and/or set a fallback sequence.

   If the downstream in-app automation or scene 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, 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].

8. Click Save.

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.

1. Go to Journeys and select a sequence.

2. Click to the right of the sequence. A configuration drawer will open.

3. Select the exit type: Cancellation Event or Conversion Event.

4. Select the exit event and configure.

   • Contact association: No configuration needed.

   • Subscription event:

     1. Search for and select a subscription list.
     2. Choose whether to exit when the user opts in to or out of the subscription.

   • Tag change:

     1. 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.
     2. (Optional) Click Add Another to add more tags. Airship handles multiple tags as a Boolean OR.
     3. Choose to perform the event when a tag is Added, or Removed.

   • Custom event:

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

     2. (Optional) Click Add Another to add more events. Airship handles multiple events as a Boolean OR.

     3. (Optional) Filter custom events by value or key/value properties. Filtering events this way can help you more precisely target your audience.

        1. Select Add event properties for the custom event.
        2. Select Add property and search for a property or select 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) Select the plus icon () to add an alternative for a filter.
        6. (Optional) Select Add property or Add event value to add more filters.
        7. Select All or 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. Select Save.
         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.

         Tip

        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. 100 KB maximum file size.

     4. (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.

        1. Enable Event Expiration.
        2. Enter a value in minutes, hours, days, months, or years.

5. (Optional) Enable Add continuation and complete the steps above for Configuring continuation, starting at step 4.

6. Click Save.

The map will now show a connection from the sequence to the exit event.