Tokens generated on request (user token) | Startquestion Help Center

If we want to automate the studies' process in our company, we need the ability to assign a token automatically, without first defining the respondent or importing a list of e-mail addressees to the system. In this case, the user token comes in handy, which means, a token that is not generated by Startquestion, but is given by the client. It has the same properties as the classic token (a blockade against the possibility of filling in several times and identifying the respondent's answers), but it can be, for example, the Customer's ID, which is provided in the link to the survey. In order to generate such a token, it is necessary to involve the IT department in building a simple script which generates unique links to the survey in the manner described below.

Description

The user_token added as a classic GET parameter to the survey's URL. The parameter can be used only when the survey has the option of individual links enabled for each respondent with enabled identification of respondents. Then the survey can be completed only once for a specific parameter value, and the added parameter will be attached to the completion, which will allow for the subsequent identification of the filling and linking it with a specific respondent.

Accompanied by the user_token parameter, you can also pass additional labels for this contact, so that they serve as additional information about the respondent (for example, customer segment, employee department, number of the attending consultant). The provision of this information allows the results to be further filtered and segmented according to the values provided in the labels.

Example URLs

https://www.startquestion.com/survey/123/satisfaction-study.html?user_token=123456 http://survey.mycompany.com?user_token=54123312&l1=vip&l2=uk45

Parameter descriptions

Name	Description
user_token	It is any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l1	First contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l2	The second contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l3	Third contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l4	The fourth contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l5	The fifth contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l6	The sixth contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l7	The seventh contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l8	The eighth contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.
l9	The ninth contact label. Any sequence of alphanumeric characters. The characters allowed are a-z, A-Z, 0-9, excluding diacritics.

The presentation and analysis of the results

If the user_token parameter will be provided in the link to the survey, this information will appear in the following places:

In the "Collect" -> "Offline (printing tokens)" tab as new respondents, where the label will be the user_token
Raw data export to the CSV
Raw data export to the XLSX
Export to the SPSS

In the case of the raw data and SPSS file (apart from the system token), it will be the appropriate column in Excel or an additional variable V at the SPSS.