Community Groups are officially here!
We've released Groups, a new feature that enables us to connect community members of similar industries and interests in a shared, private space. You can check out all of the details here, including information about who can join, how to join, and what Groups are currently offered. Please leave your feedback through this Community Groups Feedback Survey.

Authorization and creation of empty contacts

Ken_BHCC1 Qubie ✭
edited June 23 in Survey Platform

I work for student support services and we have created a online form that a student would use multiple times throughout the semester. I have successfully created a contact sheet and identified embedded data. In using the students ID code as part of the embedded data reference category of the contact list. I have been able to successfully login the student account. The student will use the same form for each class the student takes. I was successful in using the loop merge feature successfully.

Here's the problem: if you log in with the same student ID number twice or three times and fill out the form. I received a new contact added to the contact list that is blank. I'm making an assumption that this is a setting issue and I'm not sure how to fix this.


Best Answer

  • [Deleted User]
    [Deleted User] Qubie ✭
    Accepted Answer

    Hello @Ken_BHCC1

    Assuming you are creating or rather adding contact to contact list using contact list trigger, make sure you have checked "Update existing list members"
    Please see the below notes:

    Qtip: Update existing contact list members will only update if the Individual Link or Multiple Completes Link were used in a survey invitation, or if an Authenticator is used.
    If you do not have Deduplication enabled or have Research Core Contacts, the emailed/authenticated contact list must be the same one in the trigger. Otherwise, a new contact will be created in the contact list instead. If you do have deduplication enabled in XM Directory, the contact list does not need to be the same.

    Resource: here