1. Home
  2. /Guides
  3. /Messaging
  4. /User guide
  5. /Sequences
  6. /Creating sequences
  7. /Sequence outcomes

Sequence outcomes

Configure alternatives to the default sequence ending. Exit the sequence based on an event and/or link sequences together so that the end of one sequence is the beginning of another.

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

  • Continuation sequence — Users start another sequence after all the messages in the current sequence are sent.
  • Exit based on event — Users exit the sequence when a conversion or cancellation event occurs.
  • Exit based on event, then route to another sequence — Users exit the sequence when a conversion or cancellation event occurs then continue to another sequence.

Exit events

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

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. They are determined during the delay period configured when adding each message.

 Note

Sequences triggered by Inactivity are automatically configured such that a user becoming active is a conversion event labeled Reactivation, and you cannot configure additional conversion events.

Continuation sequences

Continuation, or downstream, sequences can be added in two ways:

  • Create new — You enter a name, then it is saved as a draft sequence.
  • Insert existing — You search for and select a sequence in your project.

For both you also set a delay period — the time Airship should wait after before triggering the downstream sequence. The delay period starts when the last message in the current sequence is sent.

For downstream draft sequences:

  • Channel selection is eliminated since your audience is predetermined by the upstream sequence.
  • When you are ready to make draft sequences active for your audience, the upstream sequence must be started first, then you can start the downstream sequence.

Configuration locations

You can configure 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. or in a sequence’s Settings. Both support:

  • Routing users to a continuation sequence that starts when all the messages in the current sequence are sent
  • Configuring an exit event WITHOUT continuing to another sequence

There is differing support for configuring an exit event AND continuing to another sequence:

  • Settings: Supports continuing to a new sequence only.
  • Map: Supports continuing to a new sequence or an existing sequence.

Configuring outcomes in the journey map

You can exit users from the sequence based on an event and/or route users to another sequence.

Continuation sequence

Route to a downstream sequence after all the messages in the current sequence are delivered or after 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 sequence. This step is eliminated if this configuration is for an exit event.

  4. Select Create New or Insert Existing.

  5. Set the delay period. Enter a value in minutes, hours, or days. This step is eliminated if this configuration is for an exit event.

    • The default value is 1 hour.
    • The maximum delay period is 90 days.

  6. Search for and select an exiting sequence or enter a name for a new draft sequence.

  7. Click Save.

The map will now show the downstream sequence with a connection to the upstream sequence or exit event.

Event and optional continuation sequence

Exit users from the sequence based on an event. You can set up multiple 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 or Conversion.

  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. Click Add event properties for the custom event.
        2. Click Add property and search for a property, or click 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) Click   to add an alternative for a filter.
        6. (Optional) Click Add property or Add event value to add more filters.
        7. 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)
        8. Click 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. 100KB 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 Sequence and configure:

    1. Select Create New or Insert Existing.

    2. Search for and select an exiting sequence or enter a name for a new draft sequence.

  6. Click Save.

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

Configuring outcomes in Settings

You can exit users from the sequence based on an event and/or route users to another sequence.

Continuation sequence only

Route users to a new sequence after all messages in the sequence are delivered.

Sequence outcomes
Outcome options in Settings

  1. Go to Journeys and select a sequence.

  2. Click  .

  3. Click Settings in the header.

  4. Go to the Outcomes tab.

  5. Click Add Link  .

  6. Set the delay period — the time Airship should wait after this sequence ends before starting users on the new sequence. Enter a value in minutes, hours, or days. The maximum delay period is 90 days.

  7. Enter a name for the new sequence.

  8. Click Save then Save and 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. .

Event and optional continuation sequence

  1. Go to Journeys and select a sequence.

  2. Click  .

  3. Click Settings in the header.

  4. Go to the Outcomes tab.

  5. Select Add Goal   or Add Event  .

  6. Select Contact association, Tag change, or Custom event.

    • For 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.

    • For 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. Click Add event properties for the custom event.
        2. Click Add property and search for a property, or click 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) Click   to add an alternative for a filter.
        6. (Optional) Click Add property or Add event value to add more filters.
        7. 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)
        8. Click 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. 100KB 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.

  7. (Optional) Route users to a new sequence when an exit event occurs. Enter a name for the sequence.

  8. Click Save then Save and 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. .