Journeys

Automate Your Message Sequences

Our easy-to-use visual builder empowers you to craft personalized messaging journeys, all with no code.

Create Journeys for every situation:

  • Onboarding sequences to guide your users to success
  • Re-engagement campaigns to get your users back
  • Abandoned cart workflows to drive sales and revenue
  • Promo, upsells, post-action followups, and more
21412141

Requirements

Journeys are currently available to customers on our Professional and Enterprise plans (see pricing).

To utilize Journeys you need to be identifying your users with External User ID. Only users with an External User ID can enter a Journey. This will enable OneSignal to track a user all the way through a Journey, sending messages from across any of the channels you'd like to use. You can see if you are setting these IDs today by checking your All Users page and turning on the External User ID column to see if it is populated.

713713

If you are not setting External User ID today and want to make use of Journeys, there are multiple ways to set these including CSV upload or in our web and mobile SDKs.

The Journeys feature is available today for the full Omni-Channel experience - mobile push, web push, in-app message, email, and SMS.

Creating a Journey

  1. Configure your Journey, including entrance and exit rules
  2. Configure the messages you want to send and when
  3. Make the Journey live

Journey Settings: Trigger

756756

This defines how users will enter your Journey and any filters you want to apply to that audience.

User matches the audience segment criteria

Use this option to target specific segments. When a user enters a segment they will enter the Journey.

Users will not automatically exit a Journey when they exit the segment, instead you need to define an exit rule.

User is inactive for amount of time

Use this option to support re-engagement and reactivation campaigns, targeting users who have not been on your website or app for a specific time period. This setting will take into account the duration that current users may already have been inactive, allowing for more immediate re-engagement activity upon Journey creation.

Audience

757757

The segment(s) of devices that are eligible to enter the Journey.

To enter a Journey a device must have an External User ID defined so the user is identified.

Users will not automatically exit a Journey when they exit the segment, instead you need to define an exit rule.

Current and future additions

Segments are dynamic and have users entering and exiting them constantly. Use this option if you want to target every user that is in your selected segments or that will enter them in the future.

Future additions only

Use this option if you only want users after the Journey goes live to enter. For example if you have an onboarding Journey with a welcome message you would only want future users to receive these messages and not any users who previously signed up.

Journey Settings: Exit + Re-entry Rules

644644

These settings define if and when a user should automatically exit your Journey. They can re-enter a Journey based on the re-entry rules you define.

Exit when user becomes active in your app/website

Use this option if you want users who visit your website or app to exit immediately. This is useful if your Journey is a re-engagement or reactivation campaign.

Exit when user no longer matches the audience conditions

Use this option if you want users to exit immediately in cases where they no longer match the original target audience segment.

Exit when a user enters a segment

If at any time the user falls into one of the selected Segments, they will immediately exit and not enter any more steps or be sent any more messages.

Re-Entry Rules

Defines how often they can repeatedly enter a Journey. Some message sequences you want to send once, like a Black Friday promotion. Some messages you’ll want to send every time a user is eligible to receive, like an abandoned cart campaign every time a user abandons the card, or a reactivation campaign every time they are inactive. This helps you space out the time in between.

❗️

Journey Settings: Scheduling

Scheduling is not currently supported. Once you make your Journey live it is live until you stop or delete it.

Journey Messages

Send a Push Notification

10681068

Select the Message Template you would like to send. We strongly encourage creating new templates specifically for your Journey to ensure analytics are accurate and not shared across instances of the template. Also, name the template something recognizable so you can easily find it in the dropdown.

Message scheduling is not currently supported. When a user reaches this step in your Journey they will be sent the message immediately.

Send an In-App Message

First, ensure that you’re set up to support sending In-App Messages.

Once set up, you can add an in-app message node to your Journey by clicking on the (+) and selecting “In-App Message”. This will open up a side panel where you can manage the content and format of your message via drag and drop or HTML editor.

Aside from the content of the message, you also have the option to set trigger conditions for the message as well as a delivery schedule, which defines the duration of time the in-app message will remain active and continue triggering for your users.

Send an Email

10681068

First ensure you’ve set up your app to support sending email.

Select the Message Template you would like to send. We strongly encourage creating new templates specifically for your Journey to ensure analytics are accurate and not shared across instances of the template. Also, name the template something recognizable so you can easily find it in the dropdown.

Message scheduling is not currently supported. When a user reaches this step in your Journey they will be sent the message immediately.

Send an SMS

First ensure you’re set up to support sending SMS.

Next, make sure you’ve created an SMS template with the messaging you’d like to send out from your Journey. You can access this by:

  • Clicking on “Messages” at the top of your screen
  • Then click on “Templates”
  • Finally click “(+) New Template” where you’ll select “New SMS Template”

Then, in your Journey, click on the (+) to add an SMS node. This will open up the side panel where you can select the template you’d like to send out at that specific point in the Journey.
Once users reach that step in the Journey, SMS messages will send out to them immediately.

Journey Actions

Wait

Use the wait action to space out your messages and steps. Define your wait time in seconds, minutes, hours, days or weeks. When a user enters these steps they will wait here the defined amount of time before leaving and going to the next step.

Tag User

10671067

Use the tag user action to add tags to users. Examples of why you might add a tag include tagging them with the Journey and step they are on in case you want to creates a segment or target this group later.

You can also use tags to make use of in-app messaging in Journeys. Tag users at a particular step in a Journey and then set up an in-app message that targets an audience with that tag.

Yes/No Branch

15561556

Yes/No Branch based on previous message behavior

Use the Yes/No Branch to personalize a users journey based on segment membership or message behavior.

Segment Membership

Branches depending on what segment the user is in. For example, if you tag your users with a plan type (lets say “Free” and “Paid”) then you can create a branch for free users and paid users. The free branch may contain more messaging incentivizing users to upgrade, while the paid branch may introduce more paid features.

Previous Message Behavior

Branch depending on what behavior the user had for other messages in the same Journey. For push those options are “Clicked” and “Delivered”. For email those options are “Delivered”, “Opened” and “Clicked”. For example, if a user did not click a previous notification, maybe you want to get more aggressive and send more messages, or send them a bigger incentive.

Safari does not support Confirmed Delivery so keep this in mind when you create branched messages.

Split Branch

11991199

Split branches are used to send randomized portions of your audience down each branch, under the Split Branch step of your Journey. This is a great way to test various things like message content, channel performance at that step of your Journey, or even larger flow structures.

You can add a Split branch by clicking on the (+) when building or editing your Journey, then selecting “Split Branch” under the “Actions” menu. At that point, the right-side settings panel will open, where you can set the proportion of your audience you’d like randomized per branch.

Make sure to utilize tags so you can track which branch your audience members experienced!

NOTE: The way the randomization works is each audience member that reaches that step of the Journey will have the defined percent chance to move down each path. This means that, especially with smaller sample sizes, you may not always see perfectly proportioned groups (for example, with a 50/50 split and a 6-person audience, you may see 4 go down one path and 2 down another); however, this will look much closer with larger sample sizes and again ensures truly randomized groupings per variant in your test.

ABN Tests (Multi-Variant Testing)

You can set up ABN tests by nesting your Split Branches and setting the percentages in accordance with your ideal sample group structure.

For example, if you want to set up a test with 3 variants with equally proportioned, randomized sample groups, then you start by adding a Split Branch set to send 33% of the audience down one path, and 67% down the other. Next, under the 67% branch, you’ll nest another Split Branch, sending 50% of that group down each branch. This will give you approximately a 1/3 breakdown across each of your 3 branches.

Control Groups

See how audience members naturally behave without a touch point by keeping one path free of message nodes.

Choosing a Winner

Once you’ve assessed and concluded that one branch is the highest performing, the split branch node can be edited to send 100% of the audience down that particular path.

Managing Journeys

"More Options" Dropdown

  • Delete — will delete a Journey. Once deleted you cannot retrieve it.
  • Stop & Archive — stops the Journey and gives it an archive status. These can still be accessed and duplicated.
  • Duplicate — creates a copy of that Journey which you can then edit and make live.
    ###"Edit Journey" Button
  • Edit Journey - will enter "Edit Mode" allowing you to update your Journey Name, add new steps between existing steps, and update details of existing steps. Please note that changes made in edit mode will be made live immediately - as soon as steps are added or changed, audience members will be able to enter into or other experience those changes, as applicable.

Deleting steps, updating Journey Settings (outside of Journey Name), and pausing live Journeys are not currently supported. To make these changes, you will have to stop and archive the Journey then duplicate and potentially exclude any previous users who have already received/experienced the Journey.

Journey Stats

Warning: Stats are reported at a template level. If you are reusing a template across different Journeys or in combination with Automated Messages the send and open stats will be combining these counts. We recommend creating a new template or duplicating a template for each Journey it is used in to reduce any confusion here.

Stats for each step

Name

Description

Started

Number of users that entered this step. For “Entrance” this is the total number of users that started this Journey. This will increment every time a user restarts a Journey.

Waiting

Number of users that are waiting in this step. For message steps this will typically be 0 as users are immediately sent the message and they move to the next step.

Completed

Number of users that have completed this step and moved to the next step. For “Exit” this is the total number of users that went through the full Journey.

Exited Early

Number of users that exited due to the exit rule configured. For “Exit” this is a count of all users who exited early at any point in the Journey i.e. they didn’t make it all the way through the Journey. This is a good way to track the goal of your Journey, for example, if your exit rule is entered an upgrade segment, this is a good way to track how many users converted.

Push Stats

Name

Description

Sent

Number of messages we attempted to send.

Things that will affect delivery include users not being subscribed to push, if you have frequency capping turned on, if users have unsubscribed from push. You can get a better idea on deliverability by looking at your Delivery page to see in detail what is happening with each individual message.

Clicked

Total clicks for this message.

In-App Message Stats

Name

Description

Viewed

Total unique views for this message.

Clicked

Total unique clicks for this message.

Email Stats

Name

Description

Sent

Number of messages we attempted to send.

Things that will affect delivery include users not being subscribed to email, if users have unsubscribed from email. You can get a better idea on deliverability by looking at your Delivery page to see in detail what is happening with each individual message.

Opened

Total opens for this message. Note this is total opens and not unique opens.

SMS Stats

Name

Description

Sent

Number of messages we attempted to send.

Things that will affect delivery include users not being subscribed to SMS, if users have unsubscribed from SMS. You can get a better idea on deliverability by looking at your Delivery page to see in detail what is happening with each individual message.


Did this page help you?