Routing between pages and endings
Send respondents to a later page, a specific ending, another website or a disqualification depending on how they answered.
Why route
Without routing, everyone walks through the pages in order and reaches the first ending. Routing lets one form serve different people: a screening question that ends the form early for people who do not qualify, a branch that skips a section that does not apply, or a different thank-you message per group.
Routing works on pages, so a form needs a page break where you want a decision. Add pages with Add page in the builder.
Adding a route
On the Logic tab, each page ends with a block headed After this page.
- Select Add a route.
- Build the condition in the same way as a show-if rule: choose a question, an operator and a value, and add more conditions if needed.
- Under THEN, choose where to go.
- Optionally set Otherwise go to for the case where no route matches.
Where can a route go?
| Target | What happens |
|---|---|
| Page N | The respondent skips ahead to that page. Only later pages are offered |
| Ending: title | The form finishes and shows that ending |
| Disqualify | The form stops and shows a short "Thanks for your time" message. The response is saved and marked Disqualified |
| Redirect to address… | The response is saved and the respondent is sent to a web address you enter |
Otherwise go to defaults to Next page.
A page can have several routes. They are checked from top to bottom, and the first one whose conditions match wins. Put the most specific route first.
The routes can only look at answers given on this page or earlier, plus calculated fields and hidden fields, since later answers do not exist yet.
The map
To the right of the rules, Paths draws a diagram of the form: pages on the left, endings on the right. Solid lines are the default path and dashed lines are conditional routes, labelled with the number of conditions. The diagram is a quick way to spot a page that no route can reach or an ending that nothing leads to.
What respondents experience
They see one page at a time and never see that a decision was made. Pages that were skipped are treated as if their questions were hidden: not asked, not required, nothing stored. Going back with Back takes them through the pages they actually visited.
Routing runs again on the server when the form is submitted. Only answers to questions on pages the respondent really passed through are accepted and stored.
Routes cannot loop
Routes go forward only. A route cannot send someone back to an earlier page, which means a form always finishes. If you move pages around in the builder and a route would then point backwards, that route is removed when the form is saved.
Testing
Use the Preview tab, or Preview in the top bar, and click through each branch. Preview shows the ending a respondent would reach, and for a redirect it tells you where they would be sent without leaving the page. Nothing is saved.
Plans
Routing is part of the conditional logic plan feature. See Default plan limits.
Updated Sep 30, 2026