Skip to main content

Quiz Flow

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

Why Flow matters​

  • You can see the whole journey at a glance.
  • You catch dead ends or missing links before publishing.
  • You keep branching under control when multiple outcomes exist.

Requirements​

  • A quiz must contain at least two steps for a valid journey. If you have fewer, the product shows a message that you need more steps before Flow is useful.
  • If you have not added steps yet, Flow explains that you should add steps in the builder first.

What you can connect​

Flow supports linking from common interactive elements (for example buttons, text, and images configured for navigation) to a target step. The exact controls appear when you select an element that supports a “continue” or “go to step” style action in the builder.

When you draw a link:

  1. Start from the outgoing side of an interaction on one step.
  2. Attach to the incoming side of another step card.
  3. Adjust until every active path ends where you expect.

Best practices​

  • Label steps in the builder so the Flow cards stay readable (“Offer”, “Quiz Q1”, “Result A”).
  • After large edits, re-open Flow and verify every step that should receive traffic has an incoming link from the right source.
  • Test mobile paths—branching that feels obvious on desktop can confuse small screens.

Frequently asked questions​

Flow versus 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 would confuse analytics or create infinite loops. If a connection is rejected, read the message and adjust the path.