Journeys is a visual campaign builder that lets you create omnichannel messaging experiences for your users.
Journeys are ideal for engaging users across the lifecycle of your app.
To list a few sample use cases:
- Build User Onboarding Journeys that engage users over several days or weeks and on different channels as you educate them about your service.
- Build Promotional Journeys to entice your users to transact at different points of time.
- Long-running re-engagement campaigns to pull users back into your service if they begin to slip away.
You can access Journeys under the “Engage” section of your CleverTap Dashboard. Click on the “Journeys” link in the left nav bar in your CleverTap Dashboard. Once on the page, you can click on the “create” icon to create your first journey.
Journeys are only available to customers who are on the Essentials plan.
A Journey is a combination of Segment nodes and Engagement nodes. You can connect Segment nodes and engagement nodes to each other to create powerful automation.
Types of Segment nodes
As soon as the user performs an action, the user enters this node.
Qualification to this node occurs as soon as the user performs the said event.
Segment users who did the 1st event, but did not do the 2nd event within a specified time interval.
E.g. Qualify users who added to cart, but did not purchase within 5 mins.
Segment users who performed and did not perform a set of events in the past n days.
E.g. Users who did Video Watched AND did not do Subscription Paid in the Last 30 days.
Segment users based on a date time property value like flight time, etc.
E.g. Users who have their flight after 2 hours.
You can use this node in the entry criteria only.
A user is qualified on this node when the same user is qualified for the corresponding node in another Journey, from where the current Journey is triggered.
E.g. Journey 1 has a Push message node. You want to move all users who were sent the push into another Journey. Journey trigger allows you to do this.
Segment users as soon as they visit a specific page.
Web based segment.
Segment users based on a referring website or campaign.
Web based segment.
Segment users based on the number of pages visited by them.
Web based segment.
When you start building your Journey, you need to define your “entry criteria”, this is the condition, which when met, users will enter and be a part of the Journey. The entry criteria of a Journey is essentially the segment of users you want to target.
The various types of segments you can use are:
- Live User segments: These segments qualify people as soon as they meet your specified criteria
- Past Behavior segments: In this type of Entry Criteria, users who match your specified entry criteria will qualify once every twenty-four hours.
Live user segments are further bifurcated as follows:
- Action: In this type of Entry Criteria, users will enter your Journey, as soon as they perform an event. Example: Enter people into your Journey, as soon as they install your application.
- Inaction: Users enter your Journey, as soon as they don’t do something in the future. Example: If someone adds an item to their cart, but don’t transact within 15 mins.
- Property Date-time segments: Qualify a user relative to a specific date and time in a property.
- Page visit: Users will qualify as soon as they reach a web page that matches your specifications.
- Refer entry: When users come to your website from a certain referrer, example: Facebook, or Twitter, they will be qualified for your Journey.
- Page count: As soon as the user sees the specified number of pages, they will be a part of your Journey.
We support One time, Multiple date and recurring Journeys.
E.g. For monthly payment reminders, you can schedule a Journey to start on the 1st of every month
Journeys are sequences of campaigns. At each stage of a Journey, you can choose to further segment your audience as well as deliver campaigns across multiple channels.
While creating Journeys, you can choose to specify a Journey Timeout, this will be the maximum amount of time a user will spend in a Journey. Once this window is completed for a user, they will be exited from the Journey, no matter which stage they are at.
Once a user has exited the Journey, the user is free to re-qualify, if you have allowed re-entry in your setup.
Allow Users to Re-Enter a Journey
By default, a user will qualify for a Journey only once. However, you can optionally allow users who have exited from a Journey to re-enter it should they meet the entry criteria at a later date.
Once a user is a part of a Journey, the only way they can re-qualify is if they exit the Journey, either by matching one of the specified goals, or by being forced out of the Journey and subsequently meeting the specifications of the entry criteria.
Take the following simple example.
When a user makes a purchase they enter into the Journey. After a 20 minute wait time qualifying users will receive a Push Notification with a discount promotion code.
If the Journey was set-up with the default behavior (users cannot re-enter the Journey) then after they purchase and receive the push notification they exit from the Journey. If a user makes another purchase subsequent to the initial purchase they will not receive another promotional Push Notification since this Journey does not allow for re-entry.
If however, your intent is to allow users to receive a new promotional discount after each subsequent purchase, you’d select the option to allow a user to re-enter as follows.
Connect Segment & Engage Blocks
Once you have defined a segment of users, you can choose to communicate with the segment by dragging and dropping a channel of communication from the palette on the right hand side. This communication could go to users who match the segment criteria specified by you, or to the rest of the users i.e. the users who don’t match your segment criteria.
Connect Engage & Segment Blocks
After a user receives a message, you can add a segment after that to ensure that only users who meet the criteria specified by you are taken further in the Journey.
Example: After users receive a push notification, wait for 1 day, check if users have transacted, for the people that have transacted, send them down path A, and for those who haven’t send them down path B.
Connect Engage & Engage Blocks
After a user receives a message, you can follow it up immediately, or with a delay with another message on a channel of communication of your choosing.
Example: After a user receives a push notification, you can wait for 3 days, and send another push notification.
Connect Segment & Segment Blocks
After a user has been segmented, you can follow it up with with another segment to further refine your Journey.
Example: If someone has not transacted in the last 30 days, send users who qualify for this segment down path A and if one of these users adds and item to their cart, and doesn’t buy within 15 mins, send them down a specific path.
You can apply campaign limits in a Journey. However, global throttling is not supported in Journeys.
Your users perform one action in a Journey and then move on to the next action. However, there may be instances when they do not move forward in the Journey.
There may be users waiting at the Segment node. For example, there may be users who added a product to the cart and did not buy it. They may have changed their decision or maybe they simply forgot about it. These users are waiting in the Journey until they perform the next action. You must be able to nudge them to perform the next action and continue the Journey.
You can send these users on a different path or exit them from the Journey completely.
To send them on a different path, set the qualifying period and then send them to the following node to continue their Journey.
Click the hexagon on the Segment node to set the qualifying window for the users.
The qualifying window must be set up in combination with the drawing of the Node Timeout connector. The users will not move if the Node Timeout is not connected to another node.
Connect the Node Timeout connector to another node. After the qualifying window is complete, the user automatically moves on to the next node through this timeout connector.
The yellow indicator on your segment node is a reminder that you may need to plan for Waiting users on this node in the Journey.
There may be another instance where the users have received a message but they may still wait for action. If the users do not click the message, then they are waiting for the next action. It means that when you created the Journey, the node following the Engage node is connected with a 'Viewed' or 'Clicked' connector. However, we have you covered! When you draw a 'Viewed' or 'Clicked' connector, a Phantom node with a node timeout will appear automatically. You can set the qualifying window from this Phantom node.
You can use the Force exit operator node to create an exit for users in the Journey. For example, if you want the users to exit and re-enter the current Journey you can set up this node. Drag the Force exit node from the Operator Node pane and connect it to the Segment node.
An elaborate Journey may contain multiple overlapping nodes and connections. The Auto Align & Space button will help you add clarity to the Journey canvas.
Click the Auto Align & Space button on the upper right corner of the Journey canvas.
The Auto Align & Space button automatically rearranges and spaces your nodes so that all the stats are visible clearly.
The nodes on the Nodes Stats tab are arranged automatically so that all the stats are visible clearly.
Goals are behaviors that you want users to perform. On completing a goal, users are exited from the Journey. You can drag and drop any segment from the right hand side palette and add it as a goal for your Journey. A Journey can support up to 3 goals, if a user completes any one of the goals, they will be exited from the Journey.
Common Examples of Goals
- Action based goals: In this goal, users will exit your Journey as soon as they perform a goal, in real time. Example: Exit people as soon as they perform the “Charged” event, where “item” is “Red Nike Shoes”
- Past behavior goals: Past behavior goals, like segments, are evaluated once every twenty four hours, at 12:00 am. Once the goal is evaluated, users who meet this goal will not be a part of the Journey from that day onwards. Example: Exit people if they have spent at least $300 in the last week.
We have now successfully built a Journey!
Now that we have built a Journey, save it. You can save a Journey in draft mode so that you can make more changes at a later date or time. All edits are possible to the Journey at this stage.
Click the Save button.
When you are ready to publish your Journey and all the edits are complete, your Journey can go live. Open the Journey and click Publish. You can view the Journey Statistics page to check the status of your Journey.
Editing a Journey
You can edit only the 'What' section in an engagement node after you publish a Journey.
- If your entry criteria is a Past Behavior segment, users will be qualified for your Journey at the start time specified.
- If you have added a Past Behavior segment along your Journey that segment will be evaluated once a day at 12:00 am (in the timezone of your account).
- If you have added a Past Behavior segment as a goal that segment will be evaluated once a day at 12:00 am (in the timezone of your account).
- Node timeout Evaluation - Node timeout evaluation happens every 2 hours from the start of the journey. Let me explain with example -
Journey start time 2 PM
- User A reaches a node 4 at 2:30 PM with node time out of 1 hour. His window will get over at 3:30 PM post which even if the user performs the action, he will not move via ‘Yes’ path as user is marked for node timeout. At 4 PM, user A will timeout.
- User B reaches a node 4 at 3:30 PM with node timeout of 1 hour. His window will get over at 4:30 PM post which even if the user performs the action, he will not move via ‘Yes’ path as user is marked for node timeout. At 4 PM, user B will NOT move out. At 6 PM (i.e. next evaluation run), user will move via node timeout.
- If you have added a Past Behaviour segment in middle of the journey and have drawn Node timeout path with qualifying window set less than 24hours value, all users might move via node timeout path as PBS is only evaluated every 24 hours.
Updated 24 days ago