We have been hosting a survey where upon opening the link the following occurs:
- A user is given an ID using embedded data, we’ve used two ways - using ID${piped text for quota count} OR ID${random number between 1-10000}
- In this survey, the user authenticated based on that ID and contact list within the XMDirectory includes a unique passcode
- After participants take the first survey, their contact information is saved to a new directory list and that list includes a passcode. For the “second” survey, participants are authenticated using the ID and passcode (at a later time point)
The above system has been working very well, except when we send out “blasts” to thousands of new participants. When this happens, multiple participants open the survey at the same time and end up with the same ID. This means for the subsequent survey, everyone gets “locked out”. I’ve tried moving the authenticator in the survey flow and adding “dummy pages” (e.g., a brief intro page where they have to read the information) and then it goes to the first question where the embedded data/authentication happen.
Does anyone have any advice or experience in this situation and how to handle large influxes of participants while using embedded data to give an ID and authenticator?
