This guide will walk you through how to setup visibility logic in a study.
Under Study Structure, find the question that should only show based on certain criteria.
Expand the question and go to the “Visibility Logic” section towards the bottom of the question editor.
By default, the question is “Always Shown”. Select this to open a dropdown to specify that the question is “Only Shown If..”
The logic constructor will open and prompt you to select a question from a list of questions that precede the current question. Pick the previous question that contains the response that determines whether the current question should be shown.
In this example, we only want the SmartphoneOS question to show if participants indicate that they own a smartphone.
After selecting the question, you will be prompted to specify which exact answer option(s) from that question apply to the visibility logic.
Depending on the question type of the selected question, you will be presented with different logical operators (i.e. =, ≠, <, >, ≤, ≥) and the option to select one or more of the options that may apply. For certain multi-selections, you may also be asked to specify whether they apply in conjunction (AND) or disjunction (OR).
For more complex logic, you have the option to add additional criteria and furthermore nest criteria into groupings at the bottom of the logic constructor.
Selecting the “+” button allows you to add another criterion to your logic statement.
Repeat the previous steps to specify another preceding question and corresponding answer option(s) that also apply to the visibility logic.
In this example, we furthermore want the SmartphoneOS to only show if the participants indicate that they currently have a phone subscription.
Note that once you start adding multiple criteria (or when you select multiple applicable answer options), you will have the option to specify whether these criteria apply in conjunction (“ALL of these apply”; i.e., criterion 1 “AND” criterion 2 “AND” criterion 3) or disjunction (“ANY ONE of these apply”; i.e. criterion 1 “OR” criterion 2 “OR” criterion 3).
Either one of these dropdowns will effectively modify the same AND/OR logic operation.
Selecting the “()+” button will allow you to add a nesting level to your logic statement.
The nested statements will now appear in blue containers. You can add additional criteria to each of the nested statements, add additional nested statements on the same nesting level “+”, or add an additional higher nesting level “()+”.
Note that you can also modify the AND/OR logic for the criteria within the nested statements as well as the AND/OR logic between the entire nested statements.
Once you have completed setting up your logic, select “Save” and the statement summary will appear in the Visibility Logic section of the question editor.
If you need to make any further changes or delete the logic, select the respective pencil icon or trashcan icon next to the statement summary.
Appendix: Updates
Visibility Logic is now located in the question header dropdown area.
By default, questions will be “Always Shown”.
To set conditional visibility logic based on previous response options, select “Only Shown If…”
The new Visibility Logic Filter Builder is now available for Post-Task, Pre-Condition, Post-Condition questions
For post-task and pre-/post-condition questions, you can now customize the logic filter builder by Task and/or Condition.
To revert the filter builder to apply across all tasks/conditions, select “Make All Tabs the Same as this Tab”.
New advanced logic operators for post-task or pre-/post-condition question selection.
When selecting another post-task or pre-/post-condition question, you can now further specify whether you need to select the question (i) “WITHIN the same Condition/Task” or (ii) “FROM specific Conditions/Tasks”.
“WITHIN the same Condition/Task” is the default option and means that the logic will only consider the question response from the same respective Condition/Task as the current question.
E.g., EaseComments would only show if the corresponding Ease question’s response “WITHIN the same Condition/Task” was less than 5. (However, since the example is customized by task, it would only apply to the Search task, but for all respective conditions)
“FROM specific Conditions/Tasks” allows you to set the filter on an exact pre-/post-task/condition question response across any specific Condition(s) and/or Task(s), regardless of the current question's Condition/Task.
E.g., EaseComments could be set to only show when participants answer less than 5 for any Ease questions on Best Western, regardless of how they responded to any Ease questions on Marriott.
For multiple selections of specific Conditions/Tasks, you can furthermore specify “AND/OR” logic:
- “ALL of these Conditions/Tasks apply” (i.e. AND-logic) means that the question must be answered exactly the same way for all selected Conditions/Tasks.
- “ANY one of these Conditions/Tasks apply” (i.e. OR-logic) means the question must be answered as specified for at least one of the selected Conditions/Tasks.
Keep in mind that question randomization settings might cause the logic to not apply as intended, as the previous response could now appear after the filter’s question.
New Visibility Logic confirmation screen and logic summary indicator.
After selecting “Confirm Logic” you will now be prompted to review your logic statement(s).
Any incomplete logic statements will be automatically reverted to “Always Shown”, so you have the option to go “Back to Edit”.
Once applied, the logic summary will now appear in the question header’s Visibility Logic section.
Bulk Add Editor interface updated to include summary of current items.
Adding new items via the Bulk Add window no longer replaces the existing items but will add the new items below the existing list.
This allows for better compatibility with the logic filter builder, as each of the existing items will now remain linked if they are used in any logic statements.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article