Managing Journey Steps

Steps are managed in the journey builder: Content → Journeys → Edit → Steps.

The step editor

Adding a step, or opening one with the edit pencil, launches a full-page editor. Its settings are grouped into sections listed in the left rail — select a section to edit it. You work on one section at a time, so the editor stays compact instead of one long scroll.

The step editor — choose a section in the left rail; the Overview pane sets the step's page, label, and role.

• Overview — the Page the step renders, its Label (shown in the journey's navigation), and an optional Role. The role picker is searchable — type to filter the full list by name or description (see Step roles).

• Variables — Input variables the step reads from the journey context, and Output variables it writes for later steps to use.

• Custom fields — optional extra key/value data attached to the step.

• Advanced — Disable this step and Configure branching (see below).

• Tracking scripts — per-environment analytics snippets that run on this step's page, extending your tenant-wide scripts.

A dot beside a section marks unsaved edits there. Click Save step to save everything — including any tracking-script changes — in a single action.

Add a step

1. On the Steps tab, click Add step.

2. In Overview, choose the Page, give the step a Label, and (optional) set a Role.

3. In Variables, define the step's data flow:

   • Input variables — context values the step reads.

   • Output variables — context values the step writes for later steps.

4. (Optional) add Custom fields.

5. Click Save step.

Steps run in the order shown; drag to reorder them.

Disable or branch

Both live under the editor's Advanced section:

• Disable this step — hides the step from the runtime without deleting it; it's skipped on advance/back and can be re-enabled anytime.

• Configure branching — send customers down different paths based on their choices; the Flow tab visualizes the branches.

Commerce actions

Beyond rendering a page, each step can run commerce actions — create an order, create or update an account, run a fraud check, record the order in PeakCommerce, and more. Expand a step to manage them under Commerce actions. See Commerce Actions for action targets (internal vs integration), blocking vs async execution, field mapping, and required (locked) actions.

When you're done, click Done, then Publish the journey to make the changes live.