LogoLogo
Back to studio
  • 🧠Core Concepts
    • Introduction to Formsort
    • Formsort quickstart guides
      • Add content and collect answers
      • Capture demographic data
      • Add informational content
      • Template your variables
      • Add conditional logic
      • Using conditional logic with Calculated and API variables
      • Add a scheduling option
      • End the flow
      • Review your variable schema
      • Set up integrations
    • How data works in Formsort
      • Responder UUIDs
    • Understanding flows
    • Versioning in Formsort (Deploying)
      • Variant revisions
      • Managing revisions
  • ✨Creating Flows
    • Building a new flow
      • Groups
      • Steps
      • Copy-pasting form content
  • Adding questions and content
    • Questions
      • Select
      • Text
      • Address
      • Comparison
      • Confirmation
      • Date
      • Date & time
      • Email address
      • File upload
      • Grid choice
      • Iframe
      • Image upload
      • Number
      • Payment
      • Phone number
      • Postal code
      • Question group
      • Region
      • Signature
      • SSN
      • Yes/No
    • Content
      • Statement
      • Image
      • Next button
      • Video
      • Divider
      • Map
  • Controlling the flow with conditions and logic
    • Advanced logic
  • Variable templating
  • Redirects and endings
  • Field validation
  • Flow and variant management
  • Content library
  • 🧬JSON Form Definition
  • JSON schemas
  • Validating flow schemas
  • Events subscriptions
  • Flow content data format
  • šŸŽØStyling
    • Customizing appearance
      • Content area & form layout
      • Buttons
      • Typography
      • UI states
      • Color and dimension variables
      • Question containers
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
      • Animations and transitions
  • CSS & Advanced Styling
    • Custom CSS overrides
    • Step styling
    • CSS reference
  • šŸ”Form Behavior Settings
    • Variant settings
      • Form behavior for returning users
      • Group ranking API
    • Navigation sidebar
  • āš™ļøResponse Data Collection & Management
    • Schema (variables)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
  • Saving & retrieving responses
  • Importing Data
    • URL parameters
    • POST body
    • Embed query parameters
  • šŸ“ŠAnalytics and Attribution
    • Built-in analytics
    • Split testing
  • šŸš€Publishing and Deployment
    • Live preview overview
    • Environments
      • Loading different environments
    • Embedding
      • Web-embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Pre-deployment checklist
  • šŸ“Workspace Management
    • Accounts
      • Roles and permissions
    • Custom domains
    • Workspace domain detection
  • šŸ› ļøFormsort Admin API
    • Admin API
  • šŸ”ŒIntegrations
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
    • 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
Powered by GitBook
On this page
  • Options
  • Start at furthest point
  • Start at beginning, discard answers
  • Start at beginning, keep answers

Was this helpful?

  1. Form Behavior Settings
  2. Variant settings

Form behavior for returning users

What happens when visitors return to a flow they already started on?

PreviousVariant settingsNextGroup ranking API

Last updated 8 days ago

Was this helpful?

When a user returns to a form they previously started but didn’t finish, you can control where they re-enter the flow. This behavior applies to both standalone flows and those embedded into your sites.

By default, Formsort stores a responder’s answers for about 3 weeks. After that, stored data associated with their responder_uuid is purged, and they will start fresh on their next visit—unless you've changed configuration of the settings below.

Go to the Settings tab in any variant and look for Returning responder behavior to find the configuration menu.

For more information about answers storage, see our .


Options

Start each session as a new responder

When enabled, every visit is treated as a brand new session:

  • No previous answers are restored.

  • A new responder_uuid is generated on every visit, including page refreshes.

  • The user is not pinned to a variant they previously saw.

This setting is useful if you want users to always start fresh. For example, they can restart the form by simply refreshing the browser or opening it in a new tab.

If this setting is disabled, Formsort stores the responder’s UUID in browser cookies. When they return to the form using the same browser, their previous answers are restored.

Start at furthest point

(Default behavior) Responders will resume the form from the furthest step they previously reached. All previous answers will be restored.

This allows users to continue where they left off, even after refreshing their browser.

Start at beginning, discard answers

Responders will restart the flow at the beginning, and previous answers will be discarded. However, their existing responder_uuid will still be used.

This is useful when users should start over, but you want to retain their responder identity for tracking or analytics purposes.

Start at beginning, keep answers

Responders start at the beginning of the form, but their previous answers are restored into the fields.

This is helpful when you want users to review or revise their answers during a second pass through the form.

Any Formsort-related cookies are cleared, including cookies.

If you manually via URL, answers from previous sessions won’t be restored.

Learn more about and how Formsort tracks responders.

Want to learn more about other behavior settings? Go back to the overview section.

šŸ”
external variable
responder UUIDs
Settings
data retention policy
force-set a responder UUID