> 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/launch.md).

# Journey launch

Launch a journey after a final review of setup, entry rules and audience, then save it as a draft or activate it, with a pre-launch checklist.

Launch is the final step of journey creation. Review the setup, save a draft, or activate the journey.

{% hint style="info" %}
Launch only when the **conversion event**, **entry rule**, and **audience** are final.
{% endhint %}

### Before you launch

Review these areas before launch:

1. **Setup**, including the journey name, conversion event, and conversion filters
2. **Entry Rules**, including time-based or action-based entry logic
3. **Audience**, including segments or “all users” targeting
4. **Build**, including steps, branches, and action configurations

If any of these are still changing, save the journey as a draft and return later.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FJxMO6nyXkNNdhZ2tloPZ%2FEkran%20Resmi%202026-09-24%2015.25.48.png?alt=media&amp;token=f93e03ad-bd74-46f3-929e-e28de2b5aae0" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FDrJe1jH9mjoSu8kSZp2V%2FEkran%20Resmi%202026-09-24%2015.26.42.png?alt=media&amp;token=ff062b84-a68a-48fa-b544-a613f50ff321" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="163.67578125">Action</th><th width="280.1171875">Use it when</th><th>Result</th></tr></thead><tbody><tr><td><strong>Save</strong></td><td>The setup still needs review, testing, or approval</td><td>Saves the current setup as a draft</td></tr><tr><td><strong>Publish Journey</strong></td><td>The journey is ready to go live</td><td>Saves the latest changes and activates the journey immediately</td></tr></tbody></table>

### Navigation behavior

<table><thead><tr><th width="197.86328125">Action</th><th>Use it to</th><th>Result</th></tr></thead><tbody><tr><td><strong>Back</strong></td><td>Return to the previous step</td><td>Keeps your existing work in <strong>Build</strong> available while you continue editing</td></tr><tr><td><strong>Back to Journey List</strong></td><td>Leave the creation flow and return to the journey listing page</td><td>Discards unsaved changes</td></tr></tbody></table>

### After launch

Once the journey is active, monitor its performance in [Journey analytics](/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-analytics.md).

To manage the journey later, use [Journey list and actions](/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-list-and-actions.md). It covers **Activate**, **Test Activate**, **Archive**, and **Clone**.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FtiB16kuS0BImLYftHnPF%2FEkran%20Resmi%202026-09-24%2015.27.57.png?alt=media&amp;token=bfdc1cdd-5c5c-4345-87c8-66233133755d" alt=""><figcaption></figcaption></figure>

### Quick checklist

{% stepper %}
{% step %}
**Review the core setup**

Confirm the journey goal and conversion event.
{% endstep %}

{% step %}
**Review the entry rules and audience**

Confirm that the right users can enter at the right time.
{% endstep %}

{% step %}
**Validate the flow**

Review every state, branch, and action before going live.
{% endstep %}

{% step %}
**Choose a save action**

Use **Save** for drafts and **Save & Launch** for production.
{% endstep %}
{% endstepper %}


---

# 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/launch.md?ask=<question>&goal=<user_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.