Edit a Message, Journey, or A/B Test

Make changes to Automation, In-App Automation, Journeys, unsent messages, and unsent A/B tests.

Editing behavior and availability depends on the composer used to create the original message, status, and if it was scheduled for delivery.

Edit a Message or A/B Test

  • Message, Automation, and A/B Test: Opens the message or A/B test for editing in its composer of origin.

    • For scheduled A/B tests and scheduled messages created with Message composer, this action cancels the scheduled delivery, saves the message or A/B test as a draft, and opens the message or A/B test for editing.
  • In-App Automation: Opens the message for editing. Availability for editing depends on message status. Active messages can be edited at any time. An Expired or Canceled message can be edited and its end date extended, making it active again, within 14 days of the original expiration. After 14 days you can only duplicate the expired message. See: In-App Automation: Message Status.

  1. Go to Messages » Messages Overview.
  2. Click for the message or A/B test you want to edit.

Edit a Message in a Journey

Editing the content of messages in a started journey has no impact on message delivery. For example, if you edit the content of message 3 and a user has not yet received message 3, the user will receive the updated version of message 3.

 Tip

Do not pause a journey before you edit. Edit the journey, then click Publish Changes.

  1. Go to Messages » Messages Overview.
  2. Hover over the journey you want to edit and click .
  3. Click for the message you want to edit, and select Edit Message.
  4. Complete the steps in Compose a Message In a Journey.

Edit Journey Settings

 Tip

Do not pause a journey before you edit. Edit the journey, then click Publish Changes.

  1. Go to Messages » Messages Overview.
  2. Hover over the journey you want to edit and click .
  3. Click Journey Settings in the header.
  4. Follow the steps for what you want to edit:
    Trigger
    1. Select and configure the trigger that will initiate your journey.

      Custom Event

      The Custom Event trigger initiates an automation or journey when a custom event associated with members of your audience occurs. See: Custom Events.

      In the Setup step in an automation or Trigger step in a journey:

      1. Select the Custom Event trigger.
      2. 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.
      3. (Optional) Click Add Another to add more events. Airship handles multiple events as a Boolean OR.
       Warning

      Do not set tag conditions for custom events attributed to named users. An automation or journey specifying tag conditions for a custom event attributed to named users will never run.

       Tip

      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. See Location Triggers for more information and the Location Triggers Tutorial for detailed usage steps.

      First Seen

      The First Seen trigger initiates an automation or journey 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 journey when users first open your app.
      • Web, SMS, and open channels: Triggers the automation or journey when users opt in to notifications.
      • Email: Triggers the automation or journey when users opt in to commercial notifications.

      In the Setup step in an automation or Trigger step in a journey, select the First Seen trigger.

       Important

      • Users added to Airship through an Inline List An 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 while creating your message. or the create-and-send API Used to simultaneously register and send a notification to email, sms, or open channels; synonymous with the Upload Users feature. API are purposely excluded from the First Seen trigger, preventing them from receiving duplicate messages when added to the system.

      • The First Seen trigger requires a delay of at least one hour to ensure delivery. In the Delivery step in an automation or when composing a message in a journey, you must specify a delay of at least one hour.

      Inactivity

      The Inactivity trigger initiates an automation or journey when a member of your audience does not use your app for a period of time. The inactivity period begins the later of a) the creation time of the automation or journey, or b) the last app activity by the user.

      In the Setup step in an automation or Trigger step in a journey:

      1. Select the Inactivity trigger.
      2. Enter the period of inactivity in days.
      Location

      The Location trigger initiates an automation or journey based on an audience member's device location. You can select a maximum of 20 locations per automation or journey.

       Note

      • The Location trigger requires Gimbal integration.
      • The Location trigger is not supported for web push notifications.

      In the Setup step in an automation or Trigger step in a journey:

      1. Select the Location trigger.

      2. Click Select a Location.

      3. 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. Click a result for a detailed view of a location.If selecting a geofence, the map will zoom to the selected location. Click and drag, and use the +/- zoom controls to change the displayed area.

      4. On the Results tab, check the box next to the locations you want to use as the trigger.

      5. Review the Selections tab, then click Save & Continue.

      6. (Optional) Click Select a Location to add more locations.

      7. Choose whether to trigger your automation or journey when the user enters or exits a location.

      Location Attributes

      The Location Attributes trigger initiates an automation or journey based on key/value pair metadata associated with a particular location.

      You can add a maximum of 50 location attributes per automation or journey.

       Note

      • The Location Attributes trigger requires Gimbal integration.
      • The Location Attributes trigger is not supported for web push notifications.

      In the Setup step in an automation or Trigger step in a journey:

      1. Select the Location Attributes trigger.
      2. Enter a key/value pair for the location you want to use as the message trigger.
      3. (Optional) Click to add an alternative location attribute.
      4. (Optional) Click Add Another to add more location attributes.
      5. 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 journey will be triggered if the location attributes meet ALL the attributes you entered. For example, if you selected ALL, with attributes half_off and has_cafe, you’d only reach users who entered or exited a location that met both of those conditions. If you selected ANY, you’d reach all users who entered a location running a half-off campaign as well as all users who entered a location that has a cafe.

      6. Choose whether to trigger your automation or journey when the user enters or exits a location.
      Predicted to Churn

      The Predicted to Churn trigger initiates an automation or journey 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.

       Note

      • Predictive Churn tags are available to customers who purchase predictive analytics as an add-on to either a Performance Analytics or Real-Time Data Streaming pricing plan. Contact Airship Sales for details.
      • Go to Settings » Configuration » Predictive AI to enable Predictive Churn features.

      In the Setup step in an automation or Trigger step in a journey:

      1. Select the Predicted to Churn trigger.

      2. 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.
      3. Choose whether to apply the trigger when the risk is added or removed.

      Tag Change

      The Tag Change trigger initiates an automation or journey when a tag is added or removed from a device.

      In the Setup step in an automation or Trigger step in a journey:

      1. Select the Tag Change trigger.
      2. Use the Tags box to search for a tag. If the tag you search for does not appear, click Create [search term] to create a new tag.
      3. Choose whether to apply the trigger when the tag is added or removed.

    2. (Optional) Select start and/or end dates for your journey under Scheduling.Start and end dates define the times during which your automation or journey can deliver messages to your audience.

      1. Enable the Start Date and/or End Date options.
      2. Click the date field and either use the date picker, or enter a date in YYYY-MM-DD format.
      3. Select the time and time zone.
    3. (Optional) Set rule limits Limits that cap the number of times any member of your audience can trigger a journey, helping prevent you from over-notifying your audience, e.g., a maximum of 1 per day. Rule limits are set per journey. . Click Add a Daily Limit and/or Add an All-Time Limit and enter the maximum number of times a member of your audience can trigger the journey.

    4. Click Target in the header to move on.

    Target
    1. Select the Channels A communication medium supported by the Airship service. Supported channels include app, web, email, SMS, and Open Channels. Within some channels there may be specific platforms with individual characteristics. Example platforms include Chrome for the web channel and Android for the mobile app channel. you want to include in your audience. The available channels are based on your selected journey trigger.

    2. Click Goal in the header to move on.

    Goal
    1. Select a goal:

      • Completion: Airship delivers all messages in the journey as long as conditions for delivery are met. If you select this option, you can click Save & Continue now and skip to Compose a Message.

      • Event: Airship cancels remaining messages in the journey for a user when a specific event occurs. Configure the custom event.
        1. Use the Events box to search for 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.

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

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

    2. Click Save & Continue.

Edit a Journey Name

  1. Go to Messages » Messages Overview.
  2. Hover over the journey you want to edit and click .
  3. Click the journey name in the header.
  4. Enter a new journey name, then click Continue , then Save & Continue.

Edit Delay and Conditions for a Message in a Journey

 Tip

Do not pause a journey before you edit. Edit the journey, then click Publish Changes.


 Note

By default, Airship does not send messages to a device without knowing its time zone. It may take a few minutes for Airship to process time zones when first registering devices. If you are using the First Seen trigger or another trigger set to send shortly after a user opens your app for the first time, we recommend that you include a delay when using the Schedule or Send during available window delivery timing options to give Airship time to record time zone information.

You can edit the delay period that must elapse before the message is sent and the conditions that your audience must meet to receive the message.

  • If a member of the audience doesn't meet the tag conditions, they will not receive the message or any subsequent messages in the journey; they will exit the journey.

  • Editing the timing delay between messages in a started journey may cause users to exit the journey. For example, if you edit the delay between message 2 and message 3, users who have already received message 2 will not receive message 3.

  1. Go to Messages » Messages Overview.

  2. Hover over the journey you want to edit and click .

  3. Click for the message you want to edit, and select Edit Delay & Conditions.

  4. Set the delay period — the time Airship should wait after receiving the triggering event before sending your message. Enter a value in minutes, hours, or days. The maximum delay period is 90 days.
    • For the first message in your journey:

      • The delay period starts when the triggering event is received by Airship.
      • You must set a delay of at least one hour when using the First Seen trigger.
      • You must set a delay of at least one hour if your journey that has the goal of Event.
    • For subsequent messages:

      • The delay period starts when the previous message was sent.
      • You must set a delay of at least one hour for each message in a journey that has the goal of Event.

  5. (Optional) Set conditions for sending this message. If a member of the audience doesn't meet the tag conditions, they will not receive this message or any subsequent messages in the journey; they will exit the journey. You can search for tags, tag groups, Predicted to Churn risk profiles, and device property tags.

    1. Choose whether Any or All of the tag conditions must be satisfied before the message is sent.
    2. Choose whether audience members must have or not have the tag to receive the message.
      • Has: The device must have the tag to receive the message.
      • Doesn’t Have: The device must not have the tag to receive the message.
    3. Use the Tags box to search for a tag. To filter results, click and select Tags or a specific tag group. From the search results box, you can:
      • Select a tag. A tag's tag group, if any, is listed below the tag name.
      • Select a tag group from the dropdown menu.
      • Click to create a new tag.
    4. (Optional) Click Add another condition to add more conditions.
     Warning

    Do not set tag conditions for custom events attributed to named users. A journey specifying tag conditions for a custom event attributed to named users will never run.

  6. Click Save & Continue.

  7. Click Publish Changes to apply the changes to a journey that is already in progress.