Skip to main content

How to Set Quiz Flow and Branching Logic

Flow is the map of your quiz. Each step appears as a card, and you draw connections showing where respondents go after specific interactions.

Use Flow after you have question content in Builder and before you send production traffic.

Before You Start​

Make sure you have:

  • At least two steps in the quiz (Flow needs a journey, not a single screen).
  • Interactive elements configured in Builder (buttons, options, or images with go to step / continue actions).
  • Named steps in the rail so Flow cards stay readable.
  • Preview available to walk each branch after linking.

See Quiz Flow (reference).

Step 1: Prepare Steps in Builder​

  1. Open the quiz in Quiz Builder.
  2. Confirm each step that should receive traffic has:
    • A clear name in the steps rail (Intro, Q1, Result B, etc.)
    • At least one interactive element (button, quiz option, linked text/image)
  3. Save before switching to Flow.

If you have fewer than two steps, Flow shows a message to add more steps first.

Step 2: Open Flow View​

  1. Click Flow in the quiz editor header.
  2. Review the step cards laid out on the canvas.
  3. Identify the entry step (where visitors start) and result steps (where paths should end).

Flow gives a whole-journey view that Builder alone cannot show.

Step 3: Connect Interactions to Target Steps​

For each branch you need:

  1. On a step card, find the outgoing connector on an interaction (button, option, etc.).
  2. Drag a link to the incoming side of another step card.
  3. Release to create the connection.
  4. Repeat until each choice routes to the correct next step or result.

Supported interactions commonly include:

  • Buttons with continue / go-to-step actions
  • Quiz options that advance on selection
  • Text or images configured for navigation (when enabled in Builder)

Exact controls appear when you select an element that supports navigation in Builder first.

Step 4: Validate Branching Logic​

Check the map for:

CheckWhy
Every step has an incoming link (except entry)Orphans mean visitors never reach that step.
Every path ends at a result, form, or exitDead ends frustrate users and break tracking.
No unintended loopsProduct may block cycles that confuse analytics.
Mobile paths match desktopSame links should work after Preview on phone width.

Re-open Flow after large Builder edits — structural changes can disconnect links.

Step 5: Test Every Branch in Preview​

  1. Save the quiz.
  2. Click Preview.
  3. Walk each answer combination you expect in production:
    • Path A → Result 1
    • Path B → Result 2
    • Multi-select paths if applicable
  4. Note any step that skips or lands wrong — fix in Flow, then Preview again.

Analytics and webhooks depend on visitors following the paths you defined.

Step 6: Publish When Paths Are Stable​

When all branches work in Preview:

  1. Configure webhooks or Leads if needed.
  2. Publish the quiz so live traffic uses the latest Flow. See How to publish a quiz.

Republish after any Flow change that should affect live visitors.

Best Practices​

  • Label steps for marketers and support (Offer – warm, Result – supplement).
  • Keep branching shallow when possible — deep trees are hard to QA.
  • Document result URLs per branch in your campaign brief.
  • Test edge answers (fast click-through, back button if enabled).

Troubleshooting​

ProblemWhat to try
Flow empty or disabledAdd at least two steps in Builder first.
Cannot draw a linkElement may lack navigation action — configure in Builder, return to Flow.
Connection rejected (cycle)Adjust path to avoid infinite loops per product rules.
Preview differs from FlowSave; republish if testing live URL; clear cache.
Wrong step after answerRe-select outgoing connector; confirm target step card.

Outcome​

Your quiz has explicit branching logic — every interaction routes to the intended next step or result, validated in Preview and ready for publish.

FAQ​

Flow vs Builder?

Builder edits what people see on each step. Flow edits how they move between steps. Use both together.

Can I loop back to an earlier step?

The product may block cycles that confuse analytics or create infinite loops. Read the message and adjust the path.

Do I need Flow for a linear quiz?

Even linear quizzes benefit from Flow verification — confirm each Next button targets the following step.

When should I open Flow?

After adding steps and interactive elements in Builder, and again after major structural edits.

Does Flow change require republish?

Yes, for live visitors to follow updated paths and for webhooks tied to stage completion.