To put it briefly, I'm running a two-part study. In the first survey, participants make a choice or are assigned one of eight options of a stimulus. In the second survey, a week later, participants will need to see manipulations/questions related to that specific stimulus. So I need to let Qualtrics know "hey, the person who enters ID number XXXXX sees stimulus A, the person who enters YYYYY sees stimulus B, etc.". I thought that maybe this can be either built into one survey, where one of eight blocks is presented depending on the ID they enter, or perhaps they could be re-directed to one of eight separate surveys after entering their ID, but in either case I would have to somehow be able to have Qualtrics refer to a list of participant IDs and corresponding 'conditions'.
The issue is that I can't use the contact list to carry over embedded data because I am unable to collect participant's email addresses (I'm not distributing through Qualtrics). I tried this method but the action task would not complete without a valid email address. The only 'identifier' connecting the two surveys would be a pre-assigned participant ID that the respondents enter at the start of the each survey.
Is there a way to do this without having to manually enter each and every participant ID into the Branch logic in Survey Flow?
Many thanks in advance!
If you are in charge of distributing, then you can use values in the URL possibly to trigger the proper branches. As you have the pre-assigned participant IDs, you could build a url to set embedded data in the second survey.
Embedded Data (qualtrics.com)
Also, look at the longitudinal docs: Pulling Data Into a Second Survey (Longitudinal Surveys) (qualtrics.com)
Thank you for your response!
Unfortunately, my distribution channel does not allow for custom survey links. All of the participants will access the survey though the same link, so the customization has to happen within-survey.
If you have a web server or another API server like postman.com, you could stand up a request or web service each time a respondent logs in to query your server to return a response that you could then set as embedded data. Or you could hardcode a javascript array that you could use to logically set the embedded based on the participant ID as a key.
Leave a Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.