Redirects
Send responders to other URLs during a flow, or once completed.
Last updated
Send responders to other URLs during a flow, or once completed.
Last updated
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 conditional logic 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 redirected back in to formsort to a different flow than the one already finalized, which is incredibly useful when linking multiple Formsort forms together. Dont forget, answers can be set using URL parameters when redirecting users to different forms!
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.
Redirects may also be defined at an individual step. With a step selected, click the Redirect tab to open the Redirect menu.
Conditional logic on step-level redirects may use answers defined on that same step, but it cannot use answers that are defined after that step.
If you have a redirect specified on a step without a condition, users that complete that step will finalize the flow and be redirected.
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.
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
Form answers can also be templated 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:
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.
Users can be redirected into Formsort and data from the source site can be passed in. The URL parameters passed in can be stored as an external variable, or used to set the answers for questions.
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
The utm_source data being passed in can be captured in an external variable by creating an external variable in your schema called "utm_source". Formsort will now know to look for that value in the url parameter, and can update your variable as such.
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.
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 System library answer.
