Page Navigation

By default, multi-page forms move sequentially from one page to the next. Goto and “Open website” blocks let you change that — jump to a specific page, skip sections, or redirect respondents to an external URL.

Both fire on Next click — never while the respondent is still filling in fields.

Goto: jump to a page

Type /goto to insert a goto block. Pick the destination page from the autocomplete, which shows all named pages. Unnamed pages appear as “Page 1”, “Page 2”, etc.

The first active goto above a page break determines the next page. If no goto fires, the form moves to the next page sequentially.

Conditional page routing

The typical pattern is to stack conditions with gotos before a page break:

  1. Add a condition like IF @service is "Web Design"
  2. Place a goto block inside it pointing to the “Web Details” page
  3. Add more conditions with gotos for other paths
  4. The page break follows — whichever condition is true determines where the respondent goes

Name your pages to make them easy to reference — open the page’s settings to set a name.

Open website: redirect to an external URL

Type /redirect (or select Open website from the insert menu) to add a redirect block. Enter the destination URL — you can use @ references to pass data as query parameters, like https://example.com?score=@score.

Mid-form vs end-page redirects

Where you place a redirect determines when it fires:

  • Mid-form (on any regular page) — fires on Next click, before submission. The respondent leaves without completing the form. Useful for disqualification or routing to a different experience.
  • Success page (on the success page) — fires after the form is submitted. Form data is saved first. Useful as a custom thank-you redirect.

Position determines behavior automatically — no configuration needed.

Tips

  • Goto references auto-update when you rename a page, and show an error if you delete the target page
  • Put redirects inside conditions — an unconditional redirect will always fire, which is usually not what you want (except on an end page)
  • You can use multiple gotos with different conditions to create complex branching flows

Related articles