In order for Access and Access Pro to track respondents, a unique respondent identifier is automatically generated and appended to every live link. The system knows where to place the respondent identifier in the link by the tag [ID] that is inserted in the link. This ID is commonly referred to as the GUID or code, which contains 36 digits, numbers and letters. (i.e. 00789c4f-1808-41e3-be79-ef4f1682ab48).
The GUID or code identifies what survey the respondent participated in and what status they received when they return to the system. It then allows the system to automatically credit incentives to respondents with status “complete” based on the incentive models used for each panel.
Copy the survey link template from your survey tool and paste it in Cint Access in the “Enter Link Template” box.
Survey link example:
Add the [ID] tag after the link and a variable name that your survey tool can store. The variable name is determined by your survey tool. In case of doubt, please check their documentation.
Each time a respondent is invited to a study, Access/Access Pro will use the link template to generate a unique survey link by assigning a unique GUID
As long as the project is active it is possible to change the link template and next invitations will be sent using the new template; but please make sure to inform Cint of your change.
Example Variables for different Survey Tool
Please contact your survey tool support to verify this information or for support:
|Survey tool name||Variable|
|Netigate||CPXID = [ID]|
How the variable looks is different between survey tools, please find guides to common survey tools here or ask Cint Support for help.
Other optional “tags” or codes are available if you would like to identify respondents by either: gender, panelist ID, member ID, year of birth or postal code. These tags are identified with [P], [M], [S], [PC], and [YOB].
For example, a link could look like below
Url not longer than 1000 characters
Url starts with http:// or starts with https://
Url contains required [ID] tag
Url is correctly formatted, as per Microsoft's built in method, based on RFC 2396 and RFC 2732 standards