Steps, branches & flow

A Janus popup is a graph, not a slideshow. Buttons decide where visitors go next, so flows can branch on quiz answers, skip for subscribers, loop back, or fan into parallel paths.

Adding steps

The Add step button at the bottom of the Pages panel opens a grouped catalog:

Each step card in the Pages panel has a menu for Rename, Clone, Create parallel step and Delete. Deleting a step that others still route to asks where those routes should point instead. Double-click a card to rename, drag to reorder.

Parallel branches

Parallel steps are alternatives at the same position: a quiz sending different segments to different pitches, or an A-path/B-path inside one campaign. In the Pages panel they carry a fork badge (2a, 2b, 2c…); the deepest branches collapse into an "open Flow view" chip so the list stays readable.

Buttons & actions

Every clickable element carries an Interactions tab with plain-language chains like "When clicked", "When this answer is picked", "After a successful submit", "After the win", "When scratched open". Actions run in order and can be re-arranged:

ActionWhat it does
Go to stepNext step, a specific step, or most recent step (with a fallback). The workhorse of navigation.
Submit the form / answerCommits the enclosing form or the picked answer.
Close popupDismisses, optionally redirecting to a URL.
Issue rewardMints/serves the reward: Auto (whatever they won) or a specific reward. See Offers.
Branch if already subscribedThen/else routing for known subscribers: skip the form for people who already gave their email.
Branch on a quiz answerPer-answer routing with an otherwise case. The segmentation switch.
Set user property / profile propertiesRecord zero-party data beyond quiz answers.
Add item(s) to cartAdds a variant (with quantity and selling plan) to the Shopify cart; Modify selling plan adjusts one.
Open URL / Time delay / Track click / Show contact cardUtility actions for custom flows and measurement.
Minimize to teaser buttonCollapses the popup into its teaser button instead of closing outright.
Custom code (JS) / Set variable(s)Escape hatches; see Custom code and variables.

What happens on close

Each step can define its own on-close behavior: dismiss entirely, or route to another step (a "wait, here's the deal" save attempt). Publish-time checks guarantee an on-close route can never point at a deleted step.

The Flow view

Flow view: step cards connected by arrows with a legend for route, default, when-closed and broken edges
Flow view draws the whole routing graph: solid routes, dashed defaults, close routes, broken links.

Toggle Design / Flow in the bottom toolbar. Every step renders as a card with arrows for each route. You can:

Selecting an edge opens its editor in the sidebar. Flow view has its own zoom and a desktop/mobile toggle for the card previews.

Patterns that work

Watch forThe publish ready check flags double navigation (two actions both trying to navigate), unreachable steps and broken routes as warnings. The popup will run, but the flow probably isn't what you meant.