How to stop duplication when randomising vignettes within randomised conditions | XM Community
Skip to main content
Question

How to stop duplication when randomising vignettes within randomised conditions

  • April 25, 2022
  • 2 replies
  • 33 views

Forum|alt.badge.img

Hello, I have 15 vignettes that participants will rate on a scale of one to 10. Each vignette is a block. I want the 15 vignettes to be randomly assigned to three accountability conditions (five vignettes per condition). Each condition is a block which is also randomised so all participants are exposed to all three conditions just in a different order.
Randomising the three conditions works fine – I randomise for all three conditions to be shown. However, I am not sure how to treat the vignettes. Currently I have all 15 blocks randomised under each condition block but this means I am getting duplicates across conditions because each set is randomly selected from the total group of 15 vignettes each time. I want each vignette to appear only once across all three conditions – randomisation but without repeats.  Is there a way to do this?
I also want to make sure I collect all data about the order and condition for each vignette per participant – so any tips on making sure I get this right would be a big help. Thanks in advance for any help you can offer.

2 replies

PraDeepKotian_XM
QPN Level 5 ●●●●●
Forum|alt.badge.img+21
  • QPN Level 5 ●●●●●
  • 230 replies
  • April 25, 2022

You can add the display logic to the survey flow for each block using the question whether it is displayed or not.


Forum|alt.badge.img
  • Author
  • 1 reply
  • April 26, 2022

Thanks so much for taking the time to respond to my question. I took your advice and looked at using display logic but it doesn’t seem to help prevent the question/vignette blocks repeating in the second and third conditions (or I was doing still doing something wrong!). A colleague came back and said he didn’t think it was possible within Qualtrics so has written some javascript to deal with the issue and it is now working.