Add messages to a journey

Follow these steps to add messages to a new or existing journey.

You add messages to a journey from the Manage screenA preview of the messages in a journey, with options for editing and testing, and for running experiments. .

  • For a new journey, you can start these steps immediately for your first message; the Manage screen opens automatically after you save your journey settings.
  • For existing journeys, first click Add message from the Manage screen.

Conditions

You can set channel- and tag-based conditions for sending this message. If a member of the audience doesn’t meet the conditions, they will not receive this message or any subsequent messages in the journey; they will exit the journey. Conditions are optional.

 Tip

For channels, you can create a condition based on whether or not a channel is associated with a Named UserA customer-provided identifier used for mapping multiple devices and channels to a specific individual. . The channel condition is available for the first message in a journey only.

  1. Click   for Conditions, then click Add channel conditions.
  2. Select Authenticated channels (the channel is associated with a named user) or Anonymous channels.

Click   to close the modal.


For tags, you can create a condition based on whether a user has or doesn’t have a specific tag:

  1. Click   for Conditions, then click Add tag conditions.
    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. Search for a TagMetadata that can be associated with a channel or a named user for targeting. Tags are generally descriptive terms indicating user preferences or other categorizations, e.g., wine_enthusiast or weather_alerts_los_angeles. Tags are case-sensitive. or Tag GroupAn array of tags that you can associate with both channels and named users. , including Predicted to Churn statusAnalyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, or Low Risk. , and Device PropertiesTags that represent the properties of a device, such as language and time zone settings, OS and browser versions, and notification opt-in status. Device property tags are stored automatically and can be used to target your audience. .

      To filter results, click   and make your selection. Search behavior varies by filter:

      • All (no filter selected): Search for tags in all tag groups.
      • Tags: Search for primary device tags (tags in the device tag group).
      • Tag Groups: Search for and select a tag group, then search within that tag group.

      From the search results, 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 Create [search term] to create a new tag.
    4. (Optional) Click Add another condition to add more conditions.

    When you are done adding conditions, click   to close the modal.

    Delay

    Next, set the delay period — the time Airship should wait after receiving the triggering event before sending your message.

    • For the first message in your journey:

      • The delay period starts when the triggering event is received by Airship.
      • For the First Seen trigger, a delay shorter than one hour may result in dropped sends.
      • For journeys with the goal of Event, a delay shorter than one hour may result in sends going to users who converted/cancelled.
      • For journeys using the Inactivity trigger, there is no delay setting for the first message.
    • For subsequent messages:

      • The delay period starts when the previous message was sent.
      • For journeys with the goal of Event, a delay shorter than one hour may result in sends going to users who converted/cancelled.
    1. Click   for Message Delay.
    2. Enter a value in minutes, hours, or days. The maximum delay period is 90 days.
    3. Click Save.

    Content

    You can add message content without setting up conditions or delay.

    Click Add message content. The journey name and message position appear to the right of  . After completing a step, click the next step in the header to move on.


    If your account is enabled for Orchestration, first select a Channel CoordinationA group of strategies you can use to target users where they are most likely to receive your message. strategy and channels.

    1. Select a strategy:
      Fan Out Fan Out is a channel coordination strategy that targets a named user on all the channels they are opted in to, maximizing the chances they receive your message. This strategy is suitable for highly urgent messages, where the user will not be sensitive to over-messaging. This is the default strategy when a journey does not have a triggering channel, e.g., a message sent as a result of a named user custom event or tag change, which equally applies to all channels.
      Last Active

      Last Active is a channel coordination strategy that targets a named user on the opted-in channel they used most recently. In many cases user recency is the best indicator of preference.

       Note

      Last Active is available for app and web channels only.

      Originating Channel

      Originating Channel is a channel coordination strategy that targets a named user on the channel that triggered the journey. Messaging users on the channels they use to engage your brand can help ensure a consistent user experience. This strategy is used for all accounts not enabled for channel coordination.

       Warning

      Originating Channel will not work if the triggering behavior is a custom event applied to the named user. In that case, there is no channel associated with the behavior; Airship will instead use the Fan Out strategy for delivery.

      Priority Channel Priority Channel is a channel coordination strategy that targets a named user on the first channel they are opted in to, of the priority order you set.
    2. Select the channels you want to include in your audience.
    3. (For Priority Channel only) Drag your selected channels into priority order.
    4. Click Save and continue.

    Configure the message content per enabled channel. See: Creating content and Optional Features.

    Delivery

    Configure delivery. Timing settings do not appear if you chose the Inactivity trigger.

    Review

    Review the device preview and message summary. Click the arrows to page through the various previews. The channel and display type dynamically update in the dropdown menu above. You can also select a preview directly from the dropdown menu.

    Click Save & Continue to complete adding the message to your journey.


    From the Journey ManagerA preview of the messages in a journey, with options for editing and testing, and for running experiments. , now you can:

    • Add another message to extend the journey.
    • Test the journey before starting it or publishing changes.
    • Create a control group before starting the journey.
    • Click   Start journey to make the journey available to your audience.
    • Click Publish changes to apply your changes to a journey that is already in progress. Audience members who have already triggered the journey will only see the added or edited message content if they have not yet passed this point in the journey.

    Localize your journey messages

    Learn how to localize your messages in your journey using HandlebarsAirship’s message personalization syntax using double curly braces, more commonly known as {{handlebars}}. Use handlebars to insert variables and conditional logic in messages and templates. with conditions targeting ua_language and/or ua_country tags. Localizing messages in this way ensures that your audience only sees the message intended for their language settings.

     Note

    The else statement acts as the default message for members of your audience who do not have a ua_language