Branching: send visitors down different paths

Branching lets you send visitors to different steps based on the answer they pick. Instead of marching everyone through the same questions in order, you can build a quiz or survey that adapts. Pick “Oily skin” and you go one way. Pick “Dry skin” and you go another. This is how you turn one popup into a personalized path for each shopper, so the steps they see (and the products you recommend at the end) actually match what they told you.

Before you start

Branching works on Answer Choice sections, which means survey answers and quiz options. Add the steps and answers you want first, then set up the routes.
Have your steps roughly in place before you wire routes. Routes point at specific steps, so it helps to know what each step is for.

How branching works

Routing is set on the answer, not on the step. Every survey answer and quiz option carries its own route. So a question with four answers can send visitors to four different places. There is no single “where does this question go next” setting. You set one route per answer button.

If you do not set a route on an answer, the visitor simply advances to the next step in order. That is the default, so you only need to set routes where you actually want a visitor to jump somewhere specific.

How to route an answer to a specific step

Open your popup in the editor and select the Answer Choice section you want to route (a survey answer or a quiz option).
In the config panel on the right, expand the Routing section. The help text reads: “Route visitors to different steps based on their answer. If no routing is set, visitors advance to the next step in order.”
Under Action, choose Go to specific step.
A Target step dropdown appears. Pick the step you want this answer to lead to. Steps are listed as “Step {N}: {label}”.
Repeat for each answer you want to route. The Routing summary updates to show “(Routed: Step N)” once a target is chosen, so you can see at a glance which answers have a route.

To remove a route, set Action back to Next step (default). The Action dropdown also has a Redirect to URL option, which reveals a Redirect URL field with a “https://…” placeholder.

How to see your whole flow

Once at least one route exists, a collapsible Flow map appears above the step tabs in the editor. The summary reads “Flow map (N routes)”. Expand it to see every step listed left to right. Any step that sends visitors somewhere gets a blue border and bold text, and shows ”> {target label}” so you can read the path. Use it to sanity-check that your branches go where you expect before you publish.

If you build quiz steps that branch on a calculated score, those score routes show up in the same Flow map and go through the same publish checks below, even though you did not set them on an individual answer.

How to use a routing-only step

Some steps only exist to be reached by a route, never in the normal sequence. A “thank you” step for one specific answer is a good example. Next to each step tab is a small ”⤴” button. Its tooltip reads Routing only (skip in sequential flow). Turn it on and that step tab gets a dashed border and a ”⤴” prefix. The step is then skipped in the normal order and can only be reached when an answer routes to it.

Two things to remember. A routing-only step that no answer points at can never be reached, so always pair it with at least one route. Routing-only steps are also left out of your abandonment analytics, since passing through one is not a real step view.

How to publish safely

When you click Publish, the editor checks your routes for problems.

If a route points at a step that no longer exists, or your branches form a loop, you get a Cannot publish message and publishing is blocked. Fix the route, then publish again.
If a step can never be reached, you get a Published with N warning(s) message. This does not block publishing, so the popup still goes live. Read the warning and decide if it matters.
When everything checks out, you see Published to storefront.

Tips

Set routes on answers, not on the question. If a visitor lands somewhere unexpected, check the routing on the individual answer they picked, not the step.
The display label and the stored value are two different fields. The first field on a survey answer is labeled Answer value (for routing) (on quiz options it is Answer value (stored)), and the second is Display label. You can safely change the display label visitors see. Answer-to-step routing is controlled by the Target step you pick in the Routing section, not by the stored value. The stored value is what feeds Klaviyo rules and how answers are matched in analytics, so change it with care.
A broken route does not crash anything. If you route an answer to a step you later delete or pause, the visitor quietly continues to the next step in order instead. They never get stuck on a blank popup.
The publish check only runs when you click Publish. If you pause a target step after publishing, the live popup keeps running and visitors fall through to the next step. Re-publish after edits so the check runs again.
The engine will not loop a visitor back onto a step they already saw in the same session. If a branch would send them backward to a step they visited, it moves them forward to the next unvisited step instead. Keep this in mind if you are trying to build a revisit loop.
Quiz options move on quickly after a click. Survey answers branch after the answer is submitted, so if an answer also captures data, the jump happens once the submission finishes, not instantly.
Analytics shows steps in editor order, not in branch order. There is no separate “path A vs path B” funnel, so a heavily branched quiz still lists its steps in the order you built them.

Klaviyo Routing is a different feature

There are two things in SupaPop called routing, and it is easy to mix them up.

Answer-to-step branching is what this article covers. It lives in the Routing section on each answer and decides which step a visitor sees next.

Klaviyo Routing is separate. You will find it as the Klaviyo Routing section on the popup detail page, and as a Klaviyo panel inside the answer’s config panel. It adds visitors to a Klaviyo list or fires a Klaviyo event when they pick an answer. It does not send them to a different step. If you are looking for branching and you are under a “Klaviyo Routing” heading, you are in the wrong place.