How to use Conditional logic
Updated this week


Conditional logic lets you jump participants to different steps based on their answers or actions. This means that you can ask targeted follow up questions and tasks, or take users through entirely separate branches of your project.

Using conditional logic shows participants only relevant steps, leading to higher quality responses, a better experience for participants and deeper insights for you. Almost any step supports conditional logic rules.

Conditional logic is currently in open beta on all plans. We’re working to add more features and improvements. We would love to hear your feedback and suggestions.

How to use

To get started, add a series of different steps to your Ballpark project and enter your questions or prompts to them. Once you have your steps set up:

  1. Press Conditions on the top-right hand corner of the step:

  2. Each step supports multiple rules, each rule can jump users to a particular step later in the project:

  3. To be more specific, you can add multiple conditions to a rule, linked by AND or OR clauses:

  4. At the bottom, you can also set users to otherwise go to a particular step

The otherwise go to and always go to options are important when structuring your project in branches. See the Default next step section later in this article to learn more.

Note: If a user's answer can match multiple rules you have added to a step, then they will only be routed against first rule that they match.

List of conditional logic rules available

Step name

Rules available

  • Multiple choice

  • Yes or no

  • Tagline copy test

  • Image preference

  • is equal to

  • is not equal to

  • always go to / otherwise go to

  • Prototype task

  • hit the goal successfully

  • did not hit the goal

  • always go to / otherwise go to

  • Number

  • Rating scale

  • Date

  • is equal to

  • is not equal to

  • is less than

  • is greater than

  • is less or equal to

  • is greater or equal to

  • always go to / otherwise go to

  • Text question

  • Email

  • is equal to

  • is not equal to

  • contains

  • does not contain

  • always go to / otherwise go to

  • Legal step

  • Yes, I accept must be selected to proceed, no other rules are available

  • Instruction

  • Website task

  • 5 second test

  • First click

  • Prototype free roam

  • The always go to rule can be used to route all users to a specific step

Note: Conditional logic rules can only jump users to later steps in the project. This prevents circular logic, where participants are unable to reach the end of the project.

Default next step: the always go to and otherwise go to options

By default, steps without conditional logic rules take users to the next step in the default order. You can set a different next step for all users to be taken to using the always go to option at the bottom of a step's conditions.

The always go to option enables you to keep users in a branch of follow up steps, instead of them being taken irrelevant steps that they don't need to see. This option can also be applied to steps that don't support any other conditional logic rules, except for the legal step.

Example: the otherwise go to option is great for sending someone to the end of the session if you don't need to ask them any follow up questions.

If a step already has conditional logic rules added, then this option is labelled as otherwise go to. This acts as a fallback, so you can set the default next step for any users who don't match the other rules to be taken to.

Did this answer your question?