Overview

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 if not handled correctly.
We will walk through various combinations to ensure all users' participation in journeys.

Users Waiting at Segment Node

In scenarios where the next node in a Journey is a Segment Node, the Users will wait till they qualify for the node or exit via Journey Timeouts or Goals.
For instance, you have shown the Users a Welcome message In-app and are now waiting for them to qualify for the next Segment Node, Redeem Offer. In this case, you’d want to set a time limit based on which the users should move down a different path if they don’t qualify for the Segment. This will allow you to nudge the Users to Redeem their offer in this example, and then they can join the main journey again.

Set the Qualifying Window

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 to Another Node

Connect the Node Timeout connector to another node. After the qualifying window is complete, the user automatically moves to the next node through this timeout connector.

📘

Note

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.

Users Waiting at Engage Node

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. 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 to move the users further.