If we want to automate the process of conducting the research in our company, we need the possibility of sending the token automatically, without first defining the respondent or importing the list of e-mail addresses to the system. In this case, it comes with the help of a user token. This is a token that isn’t generated by the Startquestion system, bit is transmitted by the client. It has the same properties as the classic token (blocking the possibility of filling several times and identifying the respondent’s answer), but it can be much more than that: for example, the client’s ID, which is passed in the link to the questionnaire. To generate such a token, it is necessary to involve the IT department in you company to create a simple script with unique links to the survey in the manner described below.
How to generate user token?
user_token is added as a classic GET parameter to the survey URL. The parameter can be used only when the survey has the highest security level set with the respondent identification enabled. Then the questionnaire can be filled only once for a specific parameter value, and the completed added parameter will be included to answer, which will allow for subsequent identification of the completion and linking it to a specific respondent.
Together with the user_token parameter, you can also provide additional labels for each contact, to get more additional information about the respondent (eg customer segment, employee department, number of the consultants). Providing this information allows further filtering and segmentation of results according to the values provided in the labels.
Examples of URLs
https://www.startquestion.com/survey/123/satisfaction-survey.html
=>
https://www.startquestion.com/survey/123/satisfaction-survey.html?user_token=123456
http://survey.mycompany.com/
=>
http://survey.mycompany.com/?user_token=54123312&l1=vip&l2=uk45
Description of parameters
user_token | It is any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l1 | The first contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l2 | The second contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l3 | Third contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l4 | The fourth contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l5 | The fifth contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l6 | Sixth contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l7 | Seventh contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l8 | Eight contact. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
l9 | The ninth contact label. Any string of alphanumeric characters. Permitted characters are a-z, A-Z, 0-9, excluding diacritics. |
Presentation and analysis of results
If the user_token parameter is passed in the link to the survey, this information will appear in the following places:
„Collect” tab
Export of raw data to CSV
Export of raw data to XLSX
Export to SPSS
In the case of raw data and the SPSS file (in addition to the systemic token), this will be the appropriate column in Excel or additional change V in SPSS.