aytm supplies respondents from over 50 countries and 25 languages. If you plan to field the same survey in multiple countries you will need a separate survey for each country. If you plan to field a survey in multiple languages in one country, learn more in Building a Multilingual Panel Survey.
Start by programming your master survey and creating any necessary language clones. Once your survey structure is in place, you'll be able to use various on and off platform methods to program translations, (e.g., translating with a CSV).
Programming
1. Program a Master survey
|
Creating an English master version allows us, upon request, to merge your data from other countries into the English version post-fielding. Additionally, having an English version is an insurance policy; you always have a backup or reference point.
|
2. Using ISO Country Code Logic for Multi-Country Surveys
When designing surveys for multiple countries where:
- Answer sets differ by country (e.g., local retailers or brands)
- Certain questions are not relevant to all countries,
…but you still want to merge the data later, it’s important to retain the full answer sets and all questions in every version of the survey, keeping them in the same order.
Use ISO country code logic to control which questions or answer options are shown in each country version. This is done using bracket logic like: [show if country = "XX" or country =
"XX"].Note: Country codes automatically populate once you begin typing the bracket logic and define the country variable using [country =.
- Include the full list of answer options in each country version (e.g., all brands or retailers across markets).
- Apply country-specific logic to each answer or question using the two-letter ISO country code. Example: Apply country-specific logic to each answer or question using the two-letter ISO country code.
Example: Apply [show if country = "DE" or country = "ES" or country = "IT" or country = "FR"] to the relevant answer(s). When applied, this will show the relevant answer choices to respondents in Germany, Spain, Italy, and France. - Ensure consistency across all versions to simplify data merging and analysis.
Note: All logic should be implemented exclusively within the Survey Editor page. Do not add any logic to the Language columns in the Translation Table or CSV file. The platform will automatically add the logic to the Researcher Language column of the Translation Table, and into a dedicated Logic column. of the CSV.
3. Make Clones for each version of your survey
|
Once the master version of a survey has been created, create clones for each additional language.
Note: aytm recommends cloning a survey only after the master version has been launched or reviewed by aytm. This helps prevent the duplication of surveys that may contain unresolved errors. |
4. Select survey country and language for clones
Note: Some countries may offer more than one language; learn more about fielding a survey in multiple languages within one country using Multilingual Panel Surveys. If you do not see your desired language, please reach out to our support team, or your account manager for assistance. |
View the countries and languages we currently support.
Translations
Now that the core structure of your survey is in place, you're ready to begin translating it into additional languages. There are several flexible methods available, depending on your workflow and resources. Below, we’ll walk through each approach:
Choosing your Translation WorkFlow
-
Skipper Translate: If you have Skipper enabled for your account, you can use Skipper Translate to automatically generate translations directly within the platform. This keeps the entire process streamlined and centralized. You can then review and refine translations in the language table.
Note: Users also have the flexibility to choose how translation is handled—Skipper can fully translate the survey, or you can use Skipper to generate the initial translation and then collaborate with a human translator to review and enhance the final output. -
Working on the Platform: If you're collaborating with a translator—either with or without using Skipper Translate first—you have two ways to share the survey content:
-
- On-Platform Collaboration: Invite the translator to access the platform and make manual edits directly in the Translation table. This is ideal if the translator is familiar with the platform and can work in real time.
-
Offline Collaboration: Export your survey content and send it to the translator for offline editing:
-
.CSV File: Best for structured translation workflows. Keep in mind, if sending out a CSV file for translation, advise the translator to:
- Only edit column D, the non-English Column.
- Only edit the column with text, never Logic.
- Example CSV
-
.CSV File: Best for structured translation workflows. Keep in mind, if sending out a CSV file for translation, advise the translator to:
-
Translating on Platform
|
By cloning the Master English version, and changing the country/language, you retain the original survey structure, while creating an independent survey for each additional language to share with a translator on your team. They will be able to translate the survey directly in the platform, but will not have the ability to change the structure of the survey.
Once the Translation link has been sent to your translator, they can begin translating within the translation table. Note: If you need translation services, please contact your account manager for a quote. |
Translating with a .CSV File
When a study is to be fielded in a language other than English, and the person or supplier completing the translation is not an aytm user, we recommend using the aytm platform's CSV export feature.
1. Exporting a CSV from the Translation Table
- Click the Languages icon in the survey editor page to open the translation table.
- Select Download CSV.
- Share the exported English Master CSV file with your translation team on your preferred communication platform (email, Slack, Teams, etc.). Advise your translator to add translations to column D. They do not need to include any [bracket logic], just the text translations.
Note: Please ensure they do not delete any rows or columns, and they only add translations to column D.
Uploading a .CSV File
Once the translation is complete and saved to your device, you are ready to upload your translated .csv file.
- Click on the Translation Table icon at the top right of the Survey Editor.
- Click Upload CSV.
- Select the correct file from your hard drive, and your survey will populate within a few minutes.
A few notes if working with a translator and/or translating with a CSV
- Any text in the Reference or Logic columns should remain unaltered. If translated, it will disrupt the survey upload process.
- Leave the English column completely untouched.
- Only translate the question text in the non English column(s) (e.g., Spanish).
Requesting and working with Merged Surveys
|
If your surveys have the same structure (same number and order of questions, same number of answer options; as when you cloned the Master English Version), after all surveys have completed fielding, reach out to your account manager with the survey IDs to request a merge. The merged survey Results page will provide you the ability to filter by country (look for source_survey_id in the Filters menu, and/or set up a Virtual Question (VQ) by country. |
Want to learn more about translating surveys? Check out our course in Lighthouse Academy!