Journeys let you engage with your users in real-time without the need of any code changes.
Using data collected by the Countly SDKs you can respond to any incoming data by showing your users in-app messages, feedback widgets or by recording data on behalf of them. Journeys is a logical builder which helps you decide on what data to react to and how in a nutshell.
This documentation gives you a general overview of Journeys feature, however if you are interested in more in-depth information please check out our dedicated Journeys and Content Builder guides:
Also for the integrators of the feature we recommend the Integrating Journeys and for understanding the working principles How SDKs Work documentation:
Journey Blocks
Journeys consists of a multitude of building blocks which determines what triggers a Journey to start and how it will proceed. You should think each of your users can trigger a Journey if they meet the conditions you have set:
Triggers
First block of a Journey is always a special type of block which we call a trigger. This block will determine if a user can start the Journey or not.
In this block you can select among various options (user actions or state) to start a Journey:
- User property changes
- Cohort entry/exit
- Journey exit
- Incoming data
Logical Blocks
Another block type is a logical block, which helps you build flexible paths that change depending on user behavior:
They allow you to:
- Delay a step for a time period
- Wait for a specific trigger
- Pause until a condition is met
- Continue according to result
Engagement Blocks
Engagement blocks lets you visually engage with your customers by showing in-app messages or feedback widgets (currently with survey support only.)
Some use cases are:
- Onboarding: Guide new users with contextual in-app messages
- Promotions: Send personalized offers to high-intent users
- Feature Adoption: Encourage feature usage based on inactivity
-
Behavior-Driven Engagement: React to events such as crashes, purchases, or profile updates
Data Pipelines
With data pipeline blocks you can record data on behalf of your customers. This way you can record new types of data without releasing a new app version or making any code changes.
Journey Outcomes
To track how your users are engaging with the Journeys you have created you can use the Results tab. There you will see:
- Number of users started on a Journey
- How many completed the Journey
- How many dropped off or didn’t meet conditions
By reviewing these results, you can iterate and optimize journeys based on performance.