> 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>

If journey approval is enabled for your app, these buttons change. See [Approval](#approval).

### Approval <a href="#approval" id="approval"></a>

Journey approval adds a review step before a journey goes live. When it is enabled, only users with the journey approval permission can publish or approve journeys. This permission is included in the **App Admin** role. Other users can save drafts and send journeys for approval, but cannot activate them.

{% hint style="info" %}
Approval is enabled per app by Netmera and is off by default. Contact your Netmera account team to turn it on. When approval is off, **Save** and **Publish Journey** work as described above.
{% endhint %}

#### Buttons when approval is enabled

<table><thead><tr><th width="180">Action</th><th width="220">Who sees it</th><th>Result</th></tr></thead><tbody><tr><td><strong>Save as a Draft</strong></td><td>All users, on new, draft, and stopped journeys (replaces <strong>Save</strong>)</td><td>Saves the journey as a draft. It is not sent for approval.</td></tr><tr><td><strong>Send to Approval</strong></td><td>Users without approval permission (replaces <strong>Publish Journey</strong>)</td><td>Sends the journey for approval. Its status changes to <strong>WAITING FOR APPROVAL</strong> and approvers are notified by email.</td></tr><tr><td><strong>Publish Journey</strong></td><td>Users with approval permission</td><td>Activates the journey directly, without an approval step.</td></tr></tbody></table>

The same labels appear in the confirmation dialog shown when you leave the page with unsaved changes. On active journeys, and on waiting journeys opened by an approver, the button still reads **Save**.

#### Send a journey for approval

1. Build the journey. Use **Save as a Draft** at any time to keep your work without sending it for review.
2. On the **Launch** step, click **Send to Approval**. A confirmation message tells you that the journey was sent to approval.
3. The journey appears in the journey list with the **WAITING FOR APPROVAL** status. On the **Launch** step, the status on the **Build** card shows **Waiting for Approval**.
4. Approvers receive an email with a link that opens the journey's **Launch** step. From there, they can review the journey and click **Approve & Publish**. Opening the link does not approve the journey. If you click **Send to Approval** again for the same journey, approvers do not receive a second email.

#### Approve or reject a journey

In the journey list, open the action menu (**…**) of a journey with the **WAITING FOR APPROVAL** status. These actions are available only to users with approval permission. Other users can only view the journey.

* **Edit**: review or change the journey before deciding. When an approver saves changes, the journey stays in **WAITING FOR APPROVAL**, and the **Launch** step shows **Save** and **Approve & Publish**.
* **Approve**: publishes the journey. Its status changes to **ACTIVE**.
* **Reject**: returns the journey to **DRAFT**. The creator can edit it and send it for approval again.

To reject a journey you opened from the approval email, use **Reject** in the journey list.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FSB4J6xEtrOrkF6dfrvAb%2Fdoc-journey-approval-2.png?alt=media" alt="Journeys list showing journeys with WAITING FOR APPROVAL status and the action menu with Edit, Approve and Reject"><figcaption><p>Approve or reject from the journey list</p></figcaption></figure>

#### Things to know

* **Stopped journeys:** Users without approval permission see **Send to Approval** instead of **Reactivate**. Approval changes the journey to **Active**. Rejection changes it to **Draft**, not **Stopped**.
* **Test active journeys:** Users without approval permission can't reactivate a **Test Active** journey. Stop it first, then send it for approval.
* **Approvers:** Users with approval permission can select **Reactivate** directly.
* **Editing a stopped journey:** Selecting **Save as a Draft** changes the journey to **Draft**. Send it for approval to make it live again. Approvers can publish it directly. Saving might fail briefly after stopping a journey. Wait a few seconds, then try again.
* **Editing a waiting journey:** When a user without approval permission saves a journey awaiting approval, it returns to **Draft**. Send it for approval again. Approvers aren't notified.
* **Live edits:** Only users with approval permission can change a **Trigger Journey** target on an active journey.
* **Existing journeys:** Journeys active before approval was enabled keep running. Drafts created before approval was enabled need approval before going live.

### 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](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/journey-analytics.md).

To manage the journey later, use [Journey list and actions](https://user.netmera.com/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>


---

# 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.
