When creating or editing a journey, there are two important configuration options available in the journey settings: Limit to Trigger and Priority.
Limit to Trigger
Limit to Trigger controls how many times a single user can enter and start the same journey.
By default, there is no limit on how many times a user can trigger the same journey, as long as the trigger condition is met. This is useful for journeys that are designed to repeat, such as a journey triggered by every session. However, in many cases, you may want to cap how many times a user can go through the same journey, for example, an onboarding flow that should only run once per user.
To set a limit, enable the By total entries toggle and enter a number.
Example: If you set the limit to 1, each user can start this journey at most 1 time. If they trigger the starting event again, the journey will simply not start for them. Setting the value to 0 or leaving it empty means no limit is applied.
This limit is tracked per journey version. If you publish a new version of the journey, the entry count resets for users, they will be able to enter the new version even if they had already reached the limit on a previous version.
Priority
Priority is a block-level setting available on In-App Message and Survey engagement blocks. It controls which content gets delivered first when a user qualifies for more than one in-app message or survey at the same time, for example, if a user is in multiple journeys simultaneously and both have triggered an engagement block.
Priority can be set to one of three levels:
To set a priority, click an In-App Message or Survey block in your flow, then select the desired level from the Priority dropdown in the block details panel on the right.
If two engagement blocks have the same priority level, the one that was added to the delivery queue first will be shown first.
Publishing Journey
After clicking on the "Save" button journey is saved in "draft" status. In order to be actively used, journey must be first published. Click on publish switch and confirm to publish the journey. When journey is published it's status becomes "active". Journey definition must be complete. All the mandatory fields in the block definitions must be filled. Journey must have at least one engagement block. The branches of logical blocks must have at least one engagement block. Incomplete journeys can not be activated.
Editing Journey
In order to edit the journey, first you must unpublish the journey. After that you can add/edit/delete the blocks of the journey. There are some essentials tips to know when you edit a journey.
You can not delete a block if block has subsequent block. Delete button is deactivated. First you must delete the last block in the journey. For instance, in the journey below you can not delete the in-app Message block in the middle. First you you should delete the last one
When you are done with changes, you save the journey by clicking "save journey" button. You have to publish the journey again in order to make journey active. If there were already running journeys before your change they will be run with the previous version of the journey. New journeys that are started after your changes will be run with the actual changes.
You can also rename the journey by double clicking journey name on top left.
Journey Duplication
You can duplicate a journey by clicking three dot button. On the menu select "duplicate journey" to duplicate the journey.
Click OK in confirmation pop up
A copy of the journey will be created with the name <your_journey_name>(copy) and you will be redirected to listing page.
Journey Deletion
You can delete the journey by clicking on three dot button. On the menu select "Delete Journey"
Click "OK" in confirmation pop up.
Journey will be deleted. Important thing is the journeys that are not completed yet will continue but new journeys will not be executed.
Journey Results
You can monitor the performance of your journey by clicking the Results tab at the top of the journey editor. Results can be filtered by time range using the date picker. By default, it shows All Time results.
Result Summary
The summary section displays four tiles at the top of the Results tab, each with a count or percentage, a comparison to the previous period, and a unique users count below.
Started Journeys: The total number of times the journey was started in the selected period. A journey starts when a user triggers the first trigger block defined in the flow. The unique users count below shows how many distinct users this represents.
Completed Journeys: The percentage of started journeys where the user successfully passed all steps before the engagement block, meaning they became eligible to receive content. The unique users count shows how many distinct users completed the flow.
Content Shown: The number of times in-app content was displayed to a user as part of this journey in the selected period. The unique user count shows how many distinct users viewed content.
Content Interaction Rate: The percentage of content deliveries where the user interacted with (tapped or clicked) the shown content. A higher rate indicates your content is resonating well with users. The unique users count shows how many distinct users interacted.
Journey Performance Chart
The Journey Performance chart plots four metrics over the selected time period so you can see trends and identify when users entered, completed, dropped off, or stalled:
Started journeys - new journey starts per day
Completed journeys - completions per day
Incomplete journeys - drop-offs per day (users who failed a filter or condition)
Journeys in progress - users are currently waiting at a block
Users in Journey
| Column | Description |
|---|---|
| User ID | The internal user identifier |
| Status | Current state of this run (running, completed, incomplete, etc.) |
| Start Time | When this user entered the journey |
| End Time | When this user's run finished (empty if still in progress) |
| Name | User's name if available in their profile |
| User's email if available in their profile |
You can search within the table and export the data using the download button in the top right corner of the table.
Pausing a Journey
When a journey is published, a Pause button appears in the top right of the header. Clicking it pauses the journey immediately:
No new users will enter the journey while it is paused.
Users who are currently waiting at a Wait block are suspended and will resume from where they left off when the journey is unpaused.
To resume, click the Resume button, which replaces Pause when the journey is paused.
In-app messages delivered through journeys are subject to the Engagement Queue Cooldown. If you want in-app messages to be shown immediately with no delay, go to settings, find the Journey Engine settings section and set the Engagement Queue Cooldown value to 0 to remove all cooldown restrictions