In editing your survey, you may want to ask questions with logic based on previous answers or redirect to a question based on how they answer a certain question. Adding QUESTION LOGIC, allows the user to control the questionnaire flow/routing in the Question Builder.
There are two types of logic -
PRE-CONDITION can be used to create a survey that is customized to each participant. When a specific question pertains only to certain participants, you can set a Pre-condition on it so that it shows conditionally, based on previous information. The ability to conditionally display questions allows you to create a survey that dynamically adapts to your participant’s answers.
POST CONDITION allows you to send participants to a future point in the survey based on how they answer a question. Please note that Post-condition can only be used to send participants forward in the survey, not backward.
HOW TO SET UP A PRE-CONDITION
1. In the Question Builder Page, select the question in which you will apply the logic then click the Question Logic tab then click + Add Condition
2. Select/Tick PRE-CONDITION
3. Click +Add rule
4. Select the SOURCE question (labelled in the box as IF SOMEONE ANWERS TO). When applying pre-condition to a question, you can only choose the SOURCE question that comes before the question to which you will apply logic.
(For example, Question 4 is where you will apply pre-conditions, so the condition logic will only work if the SOURCE question is from any of the Question 1, 2, 3)
5. Then select the CONDITION you want to apply then click ADD RULE.
Note: The conditions vary per question type. (See further below for the different conditions).
6. If you are going to add another rule, click ADD rule again, if not click DONE. Once you've confirmed your condition, a LOGIC icon will appear at your question.
7. If adding multiple rules in one Pre-condition, then the relationship between rules is AND. Each condition is independent, so now, if we have two Pre-conditions, then the relationship between those two Pre-conditions is OR.
For example:
You want to ask a concept or Image Hotspot question among those are who most often users of mobile wallet apps and have tried using Brand A, but you also want to ask those who haven't tried Brand A but are willing to try.
PRE-CONDITION 1: Those who are most often users of mobile wallet apps AND have tried using Brand A
PRE-CONDITION 2: Those who haven't tried Brand A but they are willing to try
In this case, the Image Hotspot question will be asked if...
Pre-condition 2 is satisfied
OR
Both conditions in Pre-condition 1 must be satisfied (even if Pre-condition 2 is not satisfied)
HOW TO SET UP A POST-CONDITION
1. In the Question Builder Page, select the question in which you will apply the logic then click the Question Logic tab then click + Add Condition
2. Select/Tick POST-CONDITION
3. Click +Add rule
4. Select the SOURCE question (labelled in the box as IF SOMEONE ANSWERS TO) you will apply the post-condition
5. Then select the CONDITION you want to apply then click ADD RULE.
Note: The conditions vary per question type. (See further below for the different conditions).
6. Select the question to which the participant will be redirected (labelled in the box as Then, jump to).
For example, you want to ask a question on category usage of dental care products in the past 7 days. In between, you have questions like conditions experienced, concept and likeability of concept. And lastly, you want to ask the reason for not using mouthwash among the non users in past 7 days, but would like to skip the in-between questions.
To do this, use Post-Condition logic in the first question (category usage of dental care products in the past 7 days) then set your condition (does not include mouthwash) then select the question it will jump to (reasons for using mouthwash)
7. Similar to the Pre-condition, if adding multiple rules in one Post-condition, then the relationship between rules is AND. Each condition is independent, so now, if we have two Post-conditions, then the relationship between those two Post-conditions is OR.
For example, we have Q1 Gender and Q2 Customer of Brand A or not, and Q2 is where we will decide which question to be directed to based on some rules from Q1 and Q2. In between, you have questions for male customers only (Q3 to Q5); while questions Q6 to Q9 are for both male and female customers. And lastly, questions Q10 and beyond are for ALL respondents.
In this case, if Q1=Female&Q2=Customers, we want to skip Q3-Q5 and jump to Q6, OR if Q2=Non Customers, we jump to Q10.
POST-CONDITION 1 IN Q2: Those who are female AND customers of Brand A, then jump to Q6 OR
POST-CONDITION 2 IN Q2: Those who are not customers of Brand A, then jump to Q10
CONDITIONS PER QUESTION TYPE
a. If the source question is a Single Choice and similar questions, then the default conditions are:
Single Choice Also for Rating / Scale / Map / Single Choice Popup Cards / Tradeoff Ranking / Treeman / NPS Plus | LOGIC |
INCLUDES | If choosing the defined options from the source question |
does not INCLUDES | If NOT choosing the defined options from the source question |
is Displayed | if the question is displayed/asked |
is NOT Displayed | If the question is NOT displayed/asked |
Please note in Tradeoff Ranking Question, INCLUDES and does not INCLUDE applies to the Top Choice only. For example, user can set up a logic where a Tradeoff Ranking Question INCLUDES Idea 1 or Idea 2 in the Top Choice.
b. If the source question is an Multiple Choice and similar questions, then the conditions are
Multiple Choice Also for Rank Order / Multiple Choice Popup Cards / Virtual Question / Image Hotspot | LOGIC |
INCLUDES | If choosing the defined options from the source question |
does not INCLUDES | If NOT choosing the defined options from the source question |
number of selected value GREATER THAN | If number of selected options is greater than the custom value |
number of selected value EQUALS to | If number of selected options is the same as the custom value |
number of selected value LESS THAN | If number of selected options is less than the custom value |
is Displayed | If the question is displayed/asked |
is NOT Displayed | If the question is NOT displayed/asked |
Please note in Rank Order Question, user can specify a specific rank order after INCLUDES and does not INCLUDE the options. For example, user can set up a logic where a Rank Order Question INCLUDES Option 1 in the 1st rank. They can also set up a logic where a Rank Order Question INCLUDES Option 1 in ANY rank order.
c. If the source question is an Open-ended or Numeric mentions, then the applicable conditions are:
Open end / Numeric Question | LOGIC |
Contains [text] | If the answer mentions the custom word / value |
does not Contains [text] | If the answer do NOT mention the custom word / value |
Equals [text] | If the exact answer is only the custom word / value |
does not Equals [text] | If the exact answer is NOT the custom word / value |
Greater than [numeric] | If answer is greater than the custom value |
Greater than OR EQUALS [numeric] | If answer is greater than or EQUALS the custom value |
Equals [numeric] | If the exact answer is custom value |
does not Equals [numeric] | If the exact answer is NOT the custom value |
Less than [numeric] | If answer is less than the custom value |
Less than OR EQUALS [numeric] | If answer is less than or EQUALS the custom value |
is Displayed | If the question is displayed/asked |
is NOT Displayed | If the question is NOT displayed/asked |
d. If the source question is System Metadata (includes Language, Self-provided Panel, and Device Type), then the conditions are
System Metadata | LOGIC |
INCLUDES | If including the defined options from the system metadata |
does not INCLUDES | If NOT including the defined options from the system metadata |
e. If the source question is URL Metadata (please see more details about URL Metadata here)
URL Metadata | LOGIC |
Contains [text] | If the URL metadata mentions the custom word / value |
does not Contains [text] | If the URL metadata do NOT mention the custom word / value |
Equals [text] | If the exact URL metadata is only the custom word / value |
does not Equals [text] | If the exact URL metadata is NOT the custom word / value |
Greater than [numeric] | If URL metadata is greater than the custom value |
Greater than OR EQUALS [numeric] | If URL metadata is greater than or EQUALS the custom value |
Equals [numeric] | If the exact URL metadata is custom value |
does not Equals [numeric] | If the exact URL metadata is NOT the custom value |
Less than [numeric] | If URL metadata is less than the custom value |
Less than OR EQUALS [numeric] | If URL metadata is less than or EQUALS the custom value |
Please note that Piped options works the same as other options and can be included in the logic system.
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