LogoLogo
Back to studio
  • Formsort documentation
  • โฉQuickstart
    • ๐ŸŸขGet started with Formsort
    • ๐ŸŽCore concepts
    • โ„น๏ธQuestion and content reference
    • ๐Ÿ“•Key terms
    • ๐Ÿž๏ธCreate your first flow
    • ๐Ÿ“–Add content and collect answers
      • ๐ŸคณCapture demographic data
      • โ„น๏ธAdd informational content
      • ๐Ÿ” Review your variable schema
    • ๐ŸŽจCreate a theme
      • Set brand guidelines
    • ๐ŸคนPersonalize your flow
      • ๐ŸŒŸTemplate your variables
      • ๐Ÿง Add conditional logic
      • ๐Ÿ’ซUsing conditional logic with Calculated and API variables
      • ๐Ÿ”šEnd the flow
    • ๐Ÿ”€Set up integrations
    • ๐Ÿš€Go live
      • Auditing your flow for content, functionality, and design
    • ๐Ÿ’ผCommon use cases
      • ๐Ÿ’”Disqualify responders
      • ๐Ÿ—“๏ธAdd a scheduling option
      • ๐Ÿ“„Allow responders to read and accept your company policies
  • ๐Ÿ—๏ธBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • ๐Ÿ’พHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
  • ๐Ÿ“บGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • ๐ŸขTeams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page
  • Default redirects
  • Redirecting at a particular step
  • Open redirect in new tab?
  • Adding query parameters to redirect URLs
  • Redirecting into Formsort
  • Accessing the expected redirect URL as an answer

Was this helpful?

  1. Building flows

Redirects

Send responders to other URLs during a flow, or once completed.

PreviousValidating flow schemasNextStyling and themes

Last updated 7 months ago

Was this helpful?

Redirecting is a crucial part of a multi-application user experience, so Formsort has made this easy to flexibly configure. In any form, you can set up redirects in two places:

  • at the end of the flow - this is the default redirect; or

  • at a particular step in a flow.

In either case, you can set for the redirect, which allows you to add different redirects for different possible scenarios. Any redirect set without conditions will always automatically redirect the user when they reach it.

Users can also be to a different flow than the one already finalized, which is incredibly useful when linking multiple Formsort forms together. Dont forget, using URL parameters when redirecting users to different forms!


Default redirects

From your Studio, you can specify a flow's redirects in the Endings section. This is the "default" redirect, and will occur automatically whenever a responder has completed a flow and they have not triggered any redirects tied to previous steps.

If a default redirect is not set, users will instead see a screen with the confirmation text at the completion of their form.


Redirecting at a particular step

Redirects may also be defined at an individual step. With a step selected, click the Redirect tab to open the Redirect menu.

If you have a redirect specified on a step without a condition, users that complete that step will finalize the flow and be redirected.

Open redirect in new tab?

If this is enabled, the redirect page will be opened in a new tab in the user's browser. This is useful if you don't want the user to be redirected out of Formsort (which will also finalize the form for them).

A good example is opening a terms and agreements page for the user to read, while still being able to advance in the flow.


Adding query parameters to redirect URLs

Query Parameters can be appended to a Redirect URL: simply add the question mark (?) separator to the Redirect URL, and enter a key-value pair. Use ampersand(&) to separate additional key-value pairs. For example:

https://redirect-out-url.com?item1=value1&key2=value2

https://redirect-out-url.com?email={{responder_email}}.

When using templated answers in your redirect URL, you can specify a URL fallback, in case the answer is not available at the time of redirect. This is highly suggested by the Formsort crew.


Redirecting into Formsort

For instance, if a user is coming from a site with a utm_source attached to the url, and you want to capture that data, you can use an external variable. The URL that redirects to Formsort would look something like https://flow.formsort.com/client/{{your_account_name}}/flow/{{your_flow_name}}/variant/{{your_flow_variant_name}}/?utm_source=example

Answers passed with the wrong type, or to non-existent variable names, are ignored when loading the flow.

Check the javascript console if you are having problems ingesting answers - a warning will be present if URL parameters don't match known answers, or the value you're providing is invalid.


Accessing the expected redirect URL as an answer

on step-level redirects may use answers defined on that same step, but it cannot use answers that are defined after that step.

Form answers can also be into the query parameters. For example, if you want to pre-populate the redirect URL with information collected from the flow, you could do so by specifying the redirect address like:

Users can be redirected into Formsort and data from the source site can be passed in. The passed in can be stored as an , or used to set the answers for questions.

The utm_source data being passed in can be captured in an external variable by creating an external variable in your called "utm_source". Formsort will now know to look for that value in the url parameter, and can update your variable as such.

If you need access to the current expected redirect URL, to show to the responder or to save in your data, you can add the expected redirect URL as a .

๐Ÿ—๏ธ
Conditional logic
templated
URL parameters
external variable
schema
System library answer
condition
redirected back in to formsort
al logic
answers can be set
Setting a default redirect