Panelist mapping

headerlogo.jpg

 

FeedbackServer let us connect a panel to a survey in order to show the panel structure and values to the survey respondents.

In order to show the correct information to the correct respondent we need a way to map the information we have about a panelist and the person who is actually taking the survey that has the panel linked to it.   

 

As a concrete example lets say that we've created a panel and filled the panel with our customer information (name, email, age, country etc..). FeedbackServer allows us to easily show the information we have about a panelists as a question inside a survey. We can then directly send the survey to the respondent to be filled out and have the updated information directly from the "source" which is actually the customer we have in our panel. No more long stressing phone calls, emails exchanges to know if the information we have in our systems is correct or not.

 

Its also interesting to know that we can map any number of panelists from different panels to the same FeedbackServer User. This is very useful to present a consolidated view to the respondent for a panelist for which data comes from different data sources.

 

Mapping Choices

FeedbackServer provides us with several ways of doing the mapping from the panelists to the respondent.

 

  1. Manual Mapping
    Using the panelist editor we can map a panelist to any existing FeedbackServer user. This method can be cumbersome as you need to assign for each panelist its FeedbackServer user and also the user must be logged inside FeedbackServer to allow the mapping.
  2. Automatic Mapping
    Using the user provider panelist mapping tool we can ask FeedbackServer to try to map the current logged in user to one of our panelist. The user provider panelist mapping tool provide us with several mapping option ranging from mapping the current logged in username to a panelist attributes or id. If you know that one of your panel attributes matches a FeedbackServer user id or user name this is the way to go. Note that the user must be logged inside FeedbackServer to allow the mapping.
  3. Security Add in Mapping
    We can use any security add in that supports the panelists mapping architecture to automatically map the current respondent to a panelist. As mapping depends on how the security addin features set are actually managing the mapping. Main advantage is that some security add in will do mapping without having the user to be logged in, e.g.: using an external querystring variable that will hold the panelist id.

 

 

(c) 2011 Data Illusion Zumbrunn. All Rights Reserved