Quota | XM Community
Skip to main content

I want to assign two conditional writing tasks to two different groups of respondents in the same survey, meaning. From a total of 100 participants, 50 participants should see the condition A question in the study, and 50 participants should see the condition B question in the same survey. how to do this? please note that questions from conditions A and B are in text writing format. 

Hey Priya,

You can create 2 quotas, with limit of 50 each. And then apply the same in the display logic for the conditions A and B for the questions.

Please see the below images.

Create 2 quotas A and B with a limit of 50 each.

 

Use the quota logic to display the question block. (Respective Question block will only be displayed only if the quota hasnt met)
Here, I have used Group A and Group B. Please use the embedded data as per your use case.

END!

​@omkarkewat I could not see group option in the embedded option (as we can see on your above screenshot), so using the question option instead of the embedded option in quota setting, is it okay?

 

 

The group is probably embedded data that omkarkewat created before setting up the quota.

For example, setting up a randomizer in survey flow, evenly present 1 of the two elements, then create 2 blocks of embedded element where Group=A and Group=B. 

Thats correct ​@Chee Heng_SZ .
​@PRIYABHARDWAJ  Define the embedded data at the start of your survey flow. Please note that its just an example. You should use the embedded data which is used in your contact/customer file and make sure its case sensitive.
If the group value is coming from a previous question then please go ahead and use the respective question in the logic instead of an embedded data.

 

​@omkarkewat / ​@Chee Heng_SZ can the following way work?-

 

​@PRIYABHARDWAJ please check your second branch logic, it should be ‘Quota - Non lonely writing has not been met’.
Can I ask, how is the group assignment happening? and is there a ‘group’ display logic assgined to the question block?
Once done, please test this setup using the preivew link.

​@omkarkewat I have just created two groups under the randomizer and named them as per desired block names from the survey, then I added the respective question blocks to each groups. I did not do anything with the group display logic. But I have added different questions under each group. is that what you were checking? 

Please correct me if I am wrong. and where should I add this?- please check your second branch logic, it should be ‘Quota - Non lonely writing has not been met’. I was thinking that the quota cap in the following setting will suffice?-

 

​@PRIYABHARDWAJ 

  1. You need to define how are the groups assigned to your respondents. If you want you can copy the below setup as is.
Firstly, any one group will assgined to the respondent randomly.

 

Create branch logics to display the respective question block.
(Branch 1 - If group is equal to A and group A quota hasnt been met then the block 1 will be shown. Similarly, Branch 2 - If group is equal to B and group B quota hasnt been met then the block 2 will be shown.)

 

  1. Next step is Quota setup. You need to check your current Quota setup. You have already set the quota limit to 50 on the top right corner (referring to your screenshot). Now, in the condition, you need to define what will increment the quota count. For example, see below image.
    Group A quota count will increment/increase if the following condition is met (i.e., If a respondent is assigned to group A, quota count will increase by 1. You can see at the top right corner 1/50, meaning 1 respondent is assgined to group A. Now this will keep increasing upto 50 and once it hits the number 50, it means that the quota has been met so according to the display logic in the survey flow, group A question block wont be displayed.)
    Same is the case for group B.

    This is my setup. You can take inspiration and create your own version. Hope this detailed explanation helps.

Got it, thanks ​@omkarkewat 

Terms & ConditionsAccessibility statement