Branch logic, also known as ‘routing’ allows you to direct respondents around your SurveyMR 2.0 based on a number of different factors. These factors can include their previous answers given in your survey, their existing custom user field data in t
How do I setup branch logic and piping?
Branch logic can be accessed within your SurveyMR 2.0 by clicking and dragging one of the options onto the canvas as shown in the screenshot below:
What Branch logic is available?
Previous Answers branch logic allows you to route respondents around your survey based on their previous answers to your questions.
> To route participants out of the survey based on their previous answers.
> Routing past questions which don’t apply, based on previous answers.
- Drag a previous answers branch logic box onto the canvas
- Select the question which determines which respondents should take the alternate route
- Select the answer option(s) which determine which respondents should follow this route
- On your survey canvas, insert the alternate destination – this could be a ‘disqualified’ exit node or another form of questions
- Connect the last form’s outport to the previous answers branch logic box in-port
- Connect the previous answers branch logic outports to the desired outcomes (e.g. one outport to the disqualified exit node, the other will continue to the next location in the survey)
A/B Splits are a way of randomly splitting out your respondents into different routes. An A/B split setup allows you to assign the desired number of paths and the % of respondents who should see each path. The system will then automatically split the respondent across the paths you have set.
A/B Splits can be used for testing different concepts where you have a form for each different concept, and only want respondents to test 1 concept each.
User field branch logic allows you to route respondents around your survey based on their existing customer user field data within the database. You are able to choose a field from your custom user fields list, then choose a predefined ‘value’ within that user field to base the routing on.
This can be used, for example, where you have questions which only apply to certain users and you want to route others past these questions, based on data that you know about them.