> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration.md). # Journey orchestration Journey orchestration builds multi-step flows that react to time and user behavior, from onboarding to reactivation. A journey is a multi-step workflow that reacts to time and user behavior. Use it to guide users through onboarding, post-purchase follow-ups, cart abandonment, or reactivation flows with timed actions and branching logic. Define entry rules, audiences, and conversion events, then monitor engagement and conversions to evaluate each step. {% hint style="info" %} This page is the overview. Use the cards below for the actual setup steps. {% endhint %} Need help managing existing drafts and live journeys? See Journey List and Actions.

Journey creation flow	Open
Step 1: Setup (name, conversion event, trigger filters)	Journey setup
Step 2: Entry Rules (time-based vs action-based)	Journey Settings
Step 3: Audience (who is eligible)	Journey audience
Step 4: Build (design the flow)	Build journey
Step 5: Launch (start, schedule, stop)	Journey launch
Measure results and evaluate performance	Journey analytics
Conversions in Journey	Conversions in journey

### Journey components

Core building blocks	Open
All journey components overview	Journey components
State (timing and holding users)	State components
Branch (split users based on rules)	Branch components
Action (send messages, update context)	Action components

### Examples and how-to videos

Examples and walkthroughs	Open
End-to-end journey patterns	Journey examples
Walkthrough videos (step-by-step)	Customer journey how-to videos
Handbook: Customer Journeys From First Touch To Loyal Advocate	https://netmera.com/omnichannel-customer-journeys/

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.