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!