Creating and Using an Embedded Unique Identifier to Prevent Repeat Survey Taking | XM Community
Skip to main content
Hello!



I'm looking to design security features for a large survey distributed via anonymous link with URL-set embedded variables (SchoolID) and (ClassID) that uses a unique identifier to prevent repeat survey takers. Here is where things get tricky -- some of the devices may be used by multiple survey takers via school computer labs using the same login information, so we can't use a straight "Prevent Ballot Box Stuffing" function. However, we will have unique URLs containing specific Class IDs, so I created an embedded variable using java which is a concatenation of the SchoolID, ClassID, and IP Address called ipID.



Is there any way to use ipID as a unique identifier to prevent a student from using the same URL on the same computer from taking the survey multiple times, but will allow another student to take the survey using a different URL? I was thinking this may involve creating a "contact list" of these unique identifiers using the "import from survey" option and then adding an authenticator in survey flow, in but this has not been successful.



Unfortunately we have to be able to prevent students from taking the survey twice, rather than writing SPSS syntax that identifies duplicates of ipID and having to decide which (if any) responses are valid.



Thanks!
@CatherineO,



_"I was thinking this may involve creating a "contact list" of these unique identifiers using the "import from survey" option and then adding an authenticator in survey flow, in but this has not been successful."_



I would authenticator+contactlistoption.



the typical project flow would be:

1. authenticate respondent based on unique ID

a. Doing so check if survey status is completed, if yes, end survey right there and make sure to tick "Do not record" check box end of survey element

3. upon survey completion (i.e. if they successfully compled the survey), update survey status as completed using contactlist trigger.



This approach should work, the only thing is to place the element at right place.

Leave a Reply