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
  • How to do it
  • Disqualifying Responders (Example)

Was this helpful?

  1. Core Concepts
  2. Formsort quickstart guides

Add conditional logic

PreviousTemplate your variablesNextUsing conditional logic with Calculated and API variables

Last updated 1 day ago

Was this helpful?

As a responder is going through your flow, you’ll likely learn information about them that will prompt you to show them a different experience. You can take responders through different paths of your flow by applying conditional logic at the question level, the step level, or the group level.

How to do it

In Formsort, you add conditional logic to the question, step, or group that you want to be displayed to the responder who matches that criteria.

Take this design below. I want cat and dog owners to be shown the green step because they are eligible for my services, but other pet types to be shown a disqualification screen.


Disqualifying Responders (Example)

Sometimes, you’ll need to determine whether a responder meets your eligibility requirements—and if they don’t, stop them from proceeding through the rest of your flow. This is a common use case for conditional logic, and it allows you to tailor the experience for ineligible responders while collecting only the information you need.

Before building your disqualification logic, consider the following:

  • What are the qualification criteria for my service?

  • What information do I still want to collect from disqualified responders who may qualify in the future?

  • Where should disqualified responders go next—should they be redirected, emailed, or shown a custom message?

How to Disqualify Responders

  1. Determine your qualification criteria. Common criteria include age, location, or specific answers to questions like medical history or income range.

  2. Collect the right data. Add the necessary steps and questions to your flow so you can evaluate each responder. For example:

    • Use a select question with a choice library to list all 50 U.S. states.

    • Ask a yes/no question to confirm a qualifying condition (e.g. “Are you 18 or older?”).

    • For more accuracy, calculate age from the responder’s date of birth using a calculated variable. Learn how to calculate age from date of birth →

  3. Add a disqualification step or group. Create the step (or group of steps) that disqualified responders will see. This might be a simple message ending the flow, or a series of steps to collect follow-up info or offer alternative next steps.

  4. Apply conditional logic. Add logic to the disqualification step or group so it only shows for responders who do not meet your criteria. Place this logic at the point in the flow where disqualification should occur.

    Tip: If you're redirecting responders at this point, make sure they won’t hit later steps unintentionally.

  5. Configure the end of the flow. Once responders reach the disqualification step, consider what you want to happen next:

    • Redirect to a help center or FAQ

    • Show a friendly message explaining why they aren’t eligible

    • Offer an email sign-up to notify them when they become eligible Learn more about finalizing flows →


Advanced Methods for Disqualification

If your eligibility logic is complex or subject to change, you can streamline it with more advanced tools:

  • Use a calculated variable Write a function that determines eligibility in one place, referencing multiple values (e.g. check if the responder’s state is in a list of eligible states).

  • Call your backend with an API variable Send responder data to your server and receive a response indicating whether the user is eligible. This allows you to centralize and update logic outside of the Formsort editor.

🧠