Configuring sequence outcomes in Settings

You can configure these outcomes in a sequence’s Settings:

• Exit events
• Continuation to a new sequence
• Exit events with continuation to a new sequence

New sequences are saved as drafts.

Configuring continuation

Route users to a new sequence when Airship sends the last message in the current sequence.

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

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 route users to a new sequence. See also: Exit events.

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