> 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

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.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FJ7J6kibTgVjI2muHrUTo%2FScreenshot%202026-01-23%20at%2011.20.37.png?alt=media&#x26;token=741734ba-b3bd-44a5-ae32-465c2567ba24" alt="" width="563"><figcaption></figcaption></figure>

<table data-view="cards"><thead><tr><th>Journey creation flow</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Step 1: Setup (name, conversion event, trigger filters)</td><td></td></tr><tr><td>Step 2: Entry Rules (time-based vs action-based)</td><td></td></tr><tr><td>Step 3: Audience (who is eligible)</td><td></td></tr><tr><td>Step 4: Build (design the flow)</td><td></td></tr><tr><td>Step 5: Launch (start, schedule, stop)</td><td></td></tr><tr><td>Measure results and evaluate performance</td><td></td></tr><tr><td>Conversions in Journey</td><td></td></tr></tbody></table>

### Journey components

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FWafbGkgB5tk1Je9IPVrJ%2Fimage.png?alt=media&#x26;token=dbfb6401-40b1-420b-a708-8ffeebeb9ae9" alt="" width="563"><figcaption></figcaption></figure>

<table data-view="cards"><thead><tr><th>Core building blocks</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>All journey components overview</td><td></td></tr><tr><td>State (timing and holding users)</td><td></td></tr><tr><td>Branch (split users based on rules)</td><td></td></tr><tr><td>Action (send messages, update context)</td><td></td></tr></tbody></table>

### Examples and how-to videos

<table data-view="cards"><thead><tr><th>Examples and walkthroughs</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>End-to-end journey patterns</td><td></td></tr><tr><td>Walkthrough videos (step-by-step)</td><td></td></tr><tr><td>Handbook: Customer Journeys From First Touch To Loyal Advocate</td><td><a href="https://netmera.com/omnichannel-customer-journeys/">https://netmera.com/omnichannel-customer-journeys/</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.