I am responsible for my company’s Engagement survey. At my company, historically for salaried team members, they would receive a unique link to the survey through their email. For hourly team members, we would ask them to input their employee ID# to complete the survey so that we are able to collect meta-data on the back end tied to their employee ID# (i.e., location data, demographic data, hierarchy data, etc.).This year, due to changes in leadership, we will only be able to ask our North America employees to input their employee ID#s. I need a way to use the authenticator for just North American employees, and not any employees from any other country.I am trying to come up with workarounds to this so that maybe North America at the very least can still collect employee ID#s and allow us to analyze the data that we need. One method I thought of was to use the first question of the survey to identify what region a team member is from. If they select North America as their region and click next, they will be asked to input their ID#. If they select any another region they will be directed to the next item on the survey. In this approach however, we will need to use the authenticator to be able to tie their survey response to the meta-data on the back end.Typically for our surveys, the authenticator is at the very beginning before any other question. This will be a deviation from that. I tried this out and I did get a notification saying that because the authenticator is not the first question, it may not behave accordingly. When I tried this out, it does not allow me to input my employee ID# to continue with the survey.Does anyone know of any possible workarounds for this issue? We don’t want to lose the possibility of analyzing data we have always analyzed. Thank you!

Hi Stattar!I have a more typed out explanation that Qualtrics will not seem to upload (there are screen grabs, so that may be causing it to upload slowly). I built out a example to illustrate my response, but I’m getting the same issue you’re reporting (no authenticator fields showing in the survey) -- to be honest, that may be something worth escalating to Qualtrics Support since I have live surveys that utilize these same methods, and I am not encountering the issue with those.Here’s my response without screen grabs (sorry, I’ll try to send those again):First you'll want to have branching logic in your survey flow so that people who select North America as their location are branched to the authenticator.Then you'll want to select your authentication type. Here I selected Contact which works off of Qualtrics-based contact lists. (if you choose SSO, you'll want to work with your tech department to assist with access/configuration selections). Once I pick Contact, I can select a specific contact list from my Library (or other group libraries for which I have access). You'll want to have a list of North America employees stored as a contact list in Qualtrics -- importantly, you should map the EmployeeID to the External Data Reference field when you import the list.Once you've selected your list, then you can pick which fields from that list will show up for the Authenticator. Unfortunately, those are only limited to what you see here (name, email, external data reference). This is why you should have EmployeeID mapped to External Data Reference! Then you can rename the field as "ID#" or "EmployeeID" in the box to the right of the field selection - this is how the field will display to employees when they reach the Authenticator screen in the survey. You can also add an Embedded Data element (green box) below the Authenticator in the survey flow if you want to pull in any contact list fields into the survey. If you select Add From Contacts, you can pick your contact list then select specific fields that are in that list, OR you can just manually type them out (but they're case sensitive and must match the field name exactly in order to pull in the data). I added some random fields here to illustrate what it would look like if I wanted Favorite Color, Supervisor Last Name, and Years of Service associated with the employee's responses.Lastly, you can change the Authenticator prompt text by selecting Options within the blue Authenticator box in the survey flow. From there you can change the prompt text from the default "Please log in." to something more specific to your needs. This message can also be saved and managed in your Library.

Do your North American Team members have a specific IP address (taking survey on a VPN)? If so, you could potentially pull it in as embedded data then use display logic in the questions to only ask for the employee IDs for North American Team members that match the range of IP addresses?

Using Authenticator for Some Users and Not Others

Using Authenticator for Some Users and Not Others | Experience Community

Sign up

Login to the Community

Scanning file for viruses.

This file cannot be downloaded