Responder UUIDs

Identifying individual responders using a unique ID.

PreviousViewing form answers NextEnvironments

Last updated 6 months ago

Was this helpful?

Responder UUIDs

Identifying individual responders using a unique ID.

The responder UUID (Universally Unique Identifier) identifies a particular browser, using a value stored in the browser's localStorage. This is generated automatically by Formsort when the user loads a first session, and by default will persist each time the user returns to the form.

Assigning a UUID allows the responder to continue where they left off on repeat visits, and provides a useful way to tie together events, answers, and data for the same user.

To create a fresh responder UUID for users at each return visit to your form, see "start each session as a new responder" in the documentation.

Manually setting the responder UUID

Again, you do not need to provide a responder UUID - Formsort will generate one at the responder's first session. However, if you would like to provide your own UUID to use as an identifier, set responderUuid as a URL parameter when linking to a flow: https://<FLOW-URL>?responderUuid=123e4567-e89b-12d3-a456-426614174000.

Alternatively, you may provide it within a : <input name="responderUuid" value="123e4567-e89b-12d3-a456-426614174000" />.

URL parameters can be used to set answers too! See our section on for more information.

Manually setting responderUuid is useful for two reasons:

You already have an identifier generated for a particular user, like an account UUID or session UUID from your own application. Additionally, any responderUUID set in Formsort (manually or automatically) can be passed along with the user when being redirected out of the flow.
You would like to force-load a session that is tied to a particular responder UUID. Keep in mind, force-loading a session with the responder UUID will not work if "start each session as a new responder" is enabled in the , or if the user's session has already been finalized.

The responderUuid must be a - a 36 character hexadecimal string hyphenated with the pattern8-4-4-4-12, for example 123e4567-e89b-12d3-a456-426614174000.

Making the responder UUID available as an answer

The responder UUID that is created for the user (either manually set or generated by Formsort) can be made available as an answer by adding to the form schema via the .

PreviousViewing form answers NextEnvironments

Last updated 6 months ago

Was this helpful?

Assigning a UUID allows the responder to continue where they left off on repeat visits, and provides a useful way to tie together events, answers, and data for the same user.

To create a fresh responder UUID for users at each return visit to your form, see "start each session as a new responder" in the documentation.

Manually setting the responder UUID

Alternatively, you may provide it within a : <input name="responderUuid" value="123e4567-e89b-12d3-a456-426614174000" />.

URL parameters can be used to set answers too! See our section on for more information.

Manually setting responderUuid is useful for two reasons:

You already have an identifier generated for a particular user, like an account UUID or session UUID from your own application. Additionally, any responderUUID set in Formsort (manually or automatically) can be passed along with the user when being redirected out of the flow.
You would like to force-load a session that is tied to a particular responder UUID. Keep in mind, force-loading a session with the responder UUID will not work if "start each session as a new responder" is enabled in the , or if the user's session has already been finalized.

The responderUuid must be a - a 36 character hexadecimal string hyphenated with the pattern8-4-4-4-12, for example 123e4567-e89b-12d3-a456-426614174000.

Making the responder UUID available as an answer

The responder UUID that is created for the user (either manually set or generated by Formsort) can be made available as an answer by adding to the form schema via the .

When this is pulled into your form from the System Library, you can template the responder UUID into redirects, API calls, and even the form itself if necessary. See for more information on that process.