|
-
Enable save and return: Select this option if you want respondents to be able to save the survey and come back to finish it later.
-
Enable back button: Select this option if you want respondents to be able to go back and forward in the survey.
-
Maximum number of responses: Survey will be shown as closed if it is accessed after the maximum numbers of responses is reached. This feature is useful if only a limited number of responses is needed, and server/database resources are limited. Set this to 0 for unlimited responses.
-
Maximum upload size: Set the max allowed size per file for files uploaded by respondents. This is applicable only if the upload feature is enabled in the question screen. See Respondent upload.
-
Save responses on:
-
Completion. Saves the survey response when the respondent has finished the survey. This will often cause less strain on the database server, because the system does not have to make a new database connection between every survey page. The disadvantage is that the partially answered survey will not be saved if a server crash occurs.
-
Every page. Ensures that the answers are stored as the respondent goes through the survey. This will cause more traffic to the database server, but will keep partial responses after a server crash.
-
-
-
Server side: The validity of response values will be checked/verified on the server side. If the values are invalid in some way, the respondent will see the same survey page again, with warning messages included above the question text.
Example with server side validation:
-
Client side: The validity of response values will be checked/verified on the client side (in the browser, by JavaScript). It is always a good idea to turn this feature on, because it will cause less load on the server. Even when it is turned on, and the browser is incapable of performing the validation, the server will still do the validation, as a last resort. This has to be done, because incorrect values can not be stored in the database. The error messages are shown in popup-windows, rather than embedded in the page.
Example with client side validation:
-
If you choose no, select the method to prevent multiple responses.
- Yes: This means that the respondents may respond to the survey as many times as they want/need.
-
No: The respondent is restricted to respond only once. If this option is selected, also specify how you want Opinio to enforce this restriction:
- General check (start and completion): This is the standard checkpoints - Opinio will check if the respondent has responded more than once at the start of the survey, and at the end.
- Thorough check (every survey page): Opinio will check for multiple responses on every survey page. This means that Opinio will contact the client for cookie data on every page, for example (if cookies are used). This will reduce the chance that someone will be able to submit a response more than once, but will also cause more server/client traffic. If you are using IP check as type of multiple-response check, this option may cause more calls to the database.
You must also specify how to perform the restriction:
- Check IP-address: The respondents IP address will be stored along with the response. When a response is saved, the system will check if another response exists for this survey with the same IP address. If so, the user will get an error message.
- Cookies: are small data elements stored in the browser. When a survey has been responded to, the system will store a value in a cookie, indicating this. Opinio will then be able to verify and give an error message if the respondent has answered before.
- Invitations: This method is useful only if you use invitations and will prevent one invitee from entering multiple responses. If invitation anonymity is off or partly on, deleting an invitee's responses will allow him/her to answer again.
- This is the email from-name and from-address used for sending email messages associated with the current survey.
-
Language switch type: (this will only appear if the survey supports more than one language)
-
URL only: The default language switch type. The language to be used in the survey is determined by a parameter in the survey url only. If no language parameter exists the default language will be used.
-
In survey top: The language to be used in the survey can be changed by the respondent in the top of each survey page.
-
-
Redirect to address: Set a web address to go to after last survey page or after the thank-you note. For example, you can type in the address of a report, so that the respondent can view the results of the survey live. Respondents must be given access to the report first. Note that you have to write the full address. E.g. "http://www.objectplanet.com".
When you start typing the address, the section is expanded. This allows you to to include built-in Opinio parameters or incoming parameters in the survey URL (that start with 'opdata_'). You are also given a choice to notify the URL address instead of redirecting to it. In this case a "Thank you" screen is displayed as normal, while Opinio connects to the URL in the background. Notifications can be useful if you want to send some data from Opinio to another system (for example a CRM system) as soon as your survey is completed by a respondent.
You can choose a custom name instead of any of the built-in parameter names to use in the URL. As for the 'opdata_' parameters, you first specify which of the parameters you would like to add and then select a custom name for it. You can have as many 'opdata_' parameters as you need (rows are added automatically). If there is no such 'opdata_' parameter in Opinio at the moment of redirect, an empty value is used.
-
Custom survey id: The survey link contains an id that points to the survey. This is a number that is generated from a sequence of numbers. For example, the survey link may look like this:
- http://yourserver.com/opinio/s?s=54
It is easy to change the number 54 at the end link to access another survey. If your survey is confidential, you might want to set the custom id, to “mySurveyId”, for example.
-
Save URL parameters: It is possible to specify URL parameters to save with each respondent. By setting this survey attribute it is possible to turn the automatic saving of these URL parameters on/off. This is necessary, because it should be possible to let a plugin handle this data (if it is not going to be saved automatically). The default value is to save the parameters ("Yes")
The custom parameters must be specified in the survey URL like this:
- http://www.mydomain.com/s?s=999&opdata_name1=XYZ&opdata_name2=ZYX
In this example, the parameter "s" is the survey id. The "name1" part of "opdata_name1" is customizable. I.e. each custom parameter must start with "opdata_". Any number of custom parameters is available – the only limitation is the length of URLs, usually 2083 characters (Internet Explorer). The custom data will be available in the "single response" report, and raw data export. This, of course, only applies if the data is actually stored in the database.