Library variables
Built-in answers about the responder's context and state.
Library answers allow access to built-in attributes about the responder's environment or context. They allow you to reach into the internals of Formsort, or the responder's browser, and pull out information that may be useful to you.
The ID of the current step (falling back to the current step index if an ID is not set). The Step ID is useful to include if using any analytics integrations, in order to analyze step-level performance. This id can be manually set in the Step Settings.
The index of the current step, which is the number automatically assigned to the step according to where it is in the flow (e.g. first step is step "0", second step is step "1", etc.). The step index cannot be manually set.
Where is the user getting redirected?
Will be set even if not currently redirecting: this is where the responder would be redirected at any point in the flow.
When the flow is being finalized, this is the same as the URL they were finally redirected to.
This variable will include the base flow url in the answer payload.
Is the responder on an Android device?
Useful as a condition for displaying an Play Store link if you have an app.
Is the responder on an iOS device, such as an iPhone?
Useful as a condition for displaying an App Store link if you have an app.
Is the responder on a mobile device, regardless of manufacturer?
Has the responder been to this flow before?
The URL of the previous step, useful for back links.
The URL that form user arrived from, corresponding to
document.referrer
.May be undefined if the user navigated directly to the flow, or if the referring page does not send the referrer per their Content Security Policy.
Take care with collecting the referrer: it may contain personally-identifying information, if the referring page puts user data in its own URL and does not have a Content Security Policy defined.
Last modified 1yr ago