priority pick in Randomization

Hi Elaine,

If you want to use qualtrics logic and keep it simple, you can manage your categories with a variable, a randomizer and some conditions.

First, you have your multiple choices question like :

For every possible choice, you have a block with your set of questions.
In your survey flow, just initiate a new embedded data to be able to limit your random blocks below.

Then add your conditions :
As you can see, the randomizer will loop over every condition, but when your counter wil reach your maximum, no more conditionnal block will be displayed.

Hi Elie! It is my understanding that the randomizer does not take into account any display logic in the branches that follow. For example, if the branch for 1 is chosen by the randomizer but then not displayed to the respondent because 1 was not selected in the initial question, the randomizer will nevertheless count that as one of the three randomized elements (despite the respondents not actually seeing the question). Is that not your experience? I run into this situation frequently and would love some additional insight. Thanks in advance! -Jenn

https://community.qualtrics.com/XMcommunity/discussion/comment/53086#Comment_53086That is NOT the case. If a branch condition is false, the branch is not chosen by the randomizer.

Thanks so much for the quick reply, Tom! In a survey I am testing right now, there are blocks with one question each in the randomizer and the display logic is set at the question level. This currently isn't working as intended, but I will try pulling the display logic out in a branch instead.

Hi Elie, Your solution is BRILLIANT! I am facing the same situation and what you suggested (using counter & conditions) to limit the number of blocks to display works perfectly. The only thing I want to add is that the embedded data should be nb_count = $e{ ${e://Field/nb_count} + 1}

And Tim is right, the randomizer does not increment the count if a condition is not met.

Thanks to both of you!

Best regards,

Philip