Journeys. Automate behavior-driven user flows.
Guide users with flows that respond to their behavior.
Journeys let teams create behavior-driven flows using triggers, conditions, waits, and goals. They are useful for moments where timing matters, such as nudging users who stall mid-KYC, and for guiding users toward a specific action inside the product.
Behavior triggers
Start flows when users take or miss important actions. This helps teams respond to real product behavior instead of sending the same message to everyone.
Conditions and waits
Add logic and timing between steps. Journeys can adapt based on what the user does next before showing more content.
Goal-based flows
Define the outcome each journey should support. Teams can use Analytics to understand whether users reached the intended goal.
Journeys work with ContentFlow audiences, campaigns, messaging channels, and analytics. After the app integrates through the REST API, with native SDKs in preview, teams can use user behavior to decide when content appears and measure whether each journey reaches its goal.