This article is designed to highlight setup and customization of several key features before your survey launches. While this training guide is not meant to be comprehensive, it does include links to individual articles providing more detailed explanations on how to use specific features. Be sure to review these articles as well when setting up your survey.
When a survey is first created, you will have the option to customize the survey properties. This includes global settings as well as error messages and external services. The Survey Properties page contains a detailed list of all options available, but the items below are ones you will want to be most familiar with.
1.1: Access methods
Perhaps the most important property (and the one changed most often) is the survey access method. This allows you to control how respondents are able to enter your survey. By default, all surveys are created with public access. This setting is most friendly for the programming and testing period, but will most likely need to be changed before the survey goes into field. Please note that you can run a single survey with multiple access methods.
What access method should I select?
- Kinesis Panel: This method is available for panel customers and allows for the seamless passing of data inbetween the survey and panel installations. If you are managing a panel and will need to launch this survey to your panelists, this method is recommended.
- Public: This method does not require any identifying information about the panelist. It is generally used for placement on websites or in situations where automated capture and storage of unique identifiers is not necessary or feasible. Cookies are used to track the authentication process and control for the allowable number of responses. Note that this means that multiple individuals attempting to take the same survey from the same computer (such as household members or employees) will be unable to access the survey unless settings allow for this. Kinesis does not recommend the use of public links if it possible to use another access method.
- Invitation: This method is the most widely used and is required if the survey is being fielded with an outside sample vendor. Either a unique identifier or email address to be passed through on the incoming URL for the respondent to be allowed to enter the survey.
- Verfied: Verified mode is identical to Invitation mode, but identifiers are preloaded into the Kinesis system as an extra safety precaution so that respondents who are familiar with url structures cannot create additional URLs. Because identifiers must be preloaded, you must know in advance who is and is not allowed to enter your survey.
- Login: This method requires that all respondents log into the survey with a username and (optional) password. As with verified mode, logins and passwords must be preloaded. Aside from security benefits, all respondents use the same URL to access the survey.
- Secure Invitation: Similar to verified mode, but also requires a unique MD5 hash on the incoming URL.
1.2: Device Support
Because different devices and browsers have different capabilities, you have the ability to select whether or not you want to render your survey for desktop and/or mobile devices. In v5.7 and below, you may support desktop, smartphone, tablet, and feature phone (WML) devices. Beginning in v5.8+, only desktop/laptop and mobile/tablet devices are supported (feature phone devices are no longer supported). You may also terminate unsupported devices.
Kinesis recommends programming all surveys with mobile devices in mind. This entails adhering to mobile survey progamming best practices, creating clean themes, and keeping survey length short. If it is not possible to design a survey so that it is optimized for mobile (as may be the case with a very long survey or one that include conjoint exercises), it is best to field the survey in desktop/laptop mode only.
ViewProtect® provides watermarking for ads and concepts that are displayed to respondents. The respondent's email address or other identifying data can be added to the image as an overlay, which can assist in identifying respondents who violate an NDA and release sensitive assets. ViewProtect® offers several layers of protection including authenticated image download, lock mechanism, and temporary image URLs that expire after use.
Please note that ViewProtect® cannot prevent the respondent from right-clicking and saving the image or from taking a screen shot of the survey.
1.4: External Services
You can connect your survey to TrueSample or Facebook via the External Services tab. Most surveys run with both of these features disabled, but you will need to enable them if you wish to launch your survey to Facebook or use built-in respondent validation.
Respondent Validation is integrated third-party digital fingerprinting technology within Kinesis Survey. With the rise of online research, the need to identify suspicious respondent behaviors (duplications, speed-through completions, unauthorized access locations, etc.) has become crucial to data credibility. TrueSample™ is a paid user subscription service that identifies suspicious respondents in real-time through digital fingerprinting, as well as other validation techniques. It ensures that respondents are: real (using third-party databases to identify fakes); unique (removes duplicates and overlaps); and engaged (removes speedsters and straight-liners).
Before TrueSample™ can be enabled, you must set up a TrueSample™ account. This can be done directly with TrueSample™ or you may contact your Kinesis account manager to help with setup. Working through Kinesis is recommended as special pricing can be obtained.
This feature allows for recruitment to a survey directly from a Facebook page. When Facebook users access the survey in this way, additional Facebook profile details for the user can be passed directly into the survey. Please note that this feature does not allow for launching to a sepcific sample. Any survey launched through Facebook will be available to anyone who views your Facebook page.
Info and system pages are landing pages that respondents may see as they move in and out of surveys. All pages are fully customizable and can be found within the Info Page Manager. The most commonly viewed pages are:
- Login Page: This page is presented for surveys using the "Login" access mode before a respondent enters the survey.
- Profile Terminated Page: This page is shown for respondents upon terminating from a profile quota (limit of 0)
- Quota Terminated: This page is shown for respondents upon terminating from a quota that is full.
- Resume Survey page: This page will be shown to anyone who has dropped out of a survey and is trying to reaccess a previously started session.
- Thank you page: This page will be displayed immediately upon completion of a survey.
- Language selection page: This page is presented for surveys with multiple languages before a respondent enters the survey. (May be bypassed if the language code is included on the incoming URL)
- Invalid survey invitation: This page will be shown to anyone who tries to access the survey with an invalid URL, most likely the result of missing parameters that are required or copying/pasting the link into the URL incorrectly.
3: Exit Pages
Exit pages are used whenever you need to redirect respondents to another website upon survey completion. These can be setup at any point during the survey programming process via the Exit Page Manager tool. If working with multiple sample sources, you may set up different exit pages for each sample. Please note that exit pages are triggered by the pcid parameter at the end of the URL; if this is not included, respondents will see the survey info pages upon completion.
The Kinesis Language Manager allows for easy creation of multilingual surveys. All UTF-8 languages are supported. The tool works by creating a downloadable XML file containing all survey question and answer options, info page texts, error messages, and invitation texts. XMLs are a translation industry standard, making it very easy for you to find a vendor of your choice to translate the file into another language. Once the file has been translated, it can be uploaded into the Language Manager, automatically creating a multilingual version of your survey.
Once the XML is in place, you have two options for routing respondents into your survey:
- Let respondents select the language they want to take the survey in. This is done automatically if no lang code is appended to the survey URL. Respondents will be directed to the Language Selection info page, where they will select their language and will proceed to the first survey question.
- Force a language on your respondents. This is done by appending the lang code onto the survey URL and is most commonly used when fielding in non-US countries. To append a lang code, use the parameter "&lang" followed by the language [ex: &lang=es (to force Spanish)].
Kinesis recommends that no translations be made until the original version is finalized. Any changes made to the original version of the survey will also need to be made to other languages.
5: Admin Tools
Several admin tools are available during the survey build process that may be useful. The most important are listed below.
- Users and Privileges
This allows you to create user and admin logins for other members of your team. Users can be restricted to data exports and viewing, while admins have access to all tools on an install.
- User Audit Log
The User Audit Log shows all changes to the survey made by any user. This feature is extremely helpful for tracking changes to a questionnaire, quotas, or data cases, and is often used by our support department in troubleshooting.
- Authentication Error Log
The authentication error log collects all failed attempts to access a survey. The log is global and contains attempts from all surveys on the installation. This tool is particularly useful when troubleshooting failed survey access attempts from surveys set in login mode or surveys being fielded to outside sample vendors. If a respondent is repeatedly attempting to log in with a bad username or password, you will be able to find records of that in the log. Similarly, any URL that has a typo or other error sent by a sample vendor will be easily visible.