When targeting a survey to people with more than one native language, you can provide translations of the questions, response options, and other interface copy to provide your survey respondents with a survey experience tailored to them.
Overview
To create a survey with translations, you'll:
Create your survey in the primary language
Provide translations for the various copy elements of your survey, either using Iterate's translation interface, or by uploading a CSV with the translated text
Deliver your survey, and either rely on automatic detection of the user's preferred language, or specify the correct language via user properties
Creating your translated survey
Begin by creating your survey in your primary language (i.e. the spoken language of the survey creator, or the primary audience of the survey).
When you're finished, go to the Customize tab, where you'll find a section called Language & Copy. Here, you can add an additional translated language to your survey. Click Add a language to begin.
First, specify the primary language for survey - i.e. the language in which the questions and response options were originally written.
Then, add the languages for which you'd like to provide translations.
Once you've selected your languages, there are two options for providing translations:
Enter translations manually by clicking Edit translation copy on each language. A window will appear that shows all the text from your survey in the primary language, and allow you to provide translations for each item.
Upload a CSV file that contains all the translations. First, click the link to download a template CSV which will have rows for each piece of text that needs translating, and columns for each of the languages you've selected. Once you've entered translations, click Upload CSV to finish.
Preview your translated survey
Once you're done providing translations, you can preview them in your survey by choosing a language to preview from the menu in the top right of the preview area.
Delivering your survey
The way Iterate chooses the correct language to show to a recipient of your survey depends on the platform.
Website surveys
By default, the Iterate SDK will choose the correct language of the available options based on the user's browser language preferences. If the user's preferred language(s) are not available, the survey's primary language will be used as a fallback.
This behavior can be overridden by setting a custom user property called language with the two-letter code for the language you wish to show a given user.
Mobile surveys
By default, the Iterate SDK will choose the correct language of the available options based on the user's device language preferences. If the user's preferred language(s) are not available, the survey's primary language will be used as a fallback.
This behavior can be overridden by setting a custom user property called language with the two-letter code for the language you wish to show a given user.
Link surveys
By default, the Iterate SDK will choose the correct language of the available options based on the user's browser language preferences. If the user's preferred language(s) are not available, the survey's primary language will be used as a fallback.
This behavior can be overridden by adding a query parameter called language with the two-letter code for the language you wish to show a given user.
Email surveys delivered by Iterate
When manually adding recipients to an email survey, there will be a dropdown to select the user's preferred language. If you're uploading a list of recipients via a CSV, you can add a column called language and provide the two-letter language code for that recipient.
Embedded email surveys
For surveys embedded in email campaigns sent via one of our integrations or another email provider, there will be a dropdown menu next to the provided embed code where you can choose an embed code specific to a given language to paste into your email provider. The method of distributing multi-language surveys will vary by provider.
In-app message surveys via integrations (Braze, MoEngage, Airship)
For in-app message surveys, Iterate will use the language property for users defined by the integration partner platform (for Braze and Airship, the language property). For MoEngage in-app message surveys, there will be a dropdown next to the provided embed code where you can choose an embed code specific tro a given language to paste into your MoEngage campaign.