Introduction to Automatic Translations

This feature is being progressively released and will be available to all customers soon. 

Our Automatic Translations feature allows researchers to automatically translate participant responses, study configurations, and exported data within the platform. This eliminates the need for manual translations, making it easier to review and analyze multilingual responses in a single language. Translations are available in real-time, ensuring that study data remains accessible and consistent across different languages.

Enabling Automatic Translations

Study Creation

Automatic Translations can be enabled upon study creation by toggling on Enable multiple languages. Analysts must define two languages for either of the following to enable Automatic Translations.

  • Languages for Participants: Defines the language(s) in which participants can view and submit responses.
  • Languages for Admin Review: Defines additional languages that Admins, Moderators, and Clients can use to review and analyze the study. Content in these languages is not visible to participants.

By default, a maximum of three participant languages can be selected, however, Admins can contact support to override this limit. 

Admin Menu

Once the study is created, the Automatic Translations toggle can be found in the Admin Menu under Study Settings within the Configuration section. If Automatic Translations were not enabled during setup, the option remains available until the first activity or discussion is created.

Study Configuration

Study content can be automatically translated, with supported fields indicated by a language picker in the bottom right corner. This language picker appears when creating activities, tasks, and discussions, showing the available study languages for both participants and Admins.

The input field is set to the user’s current language by default, and the input field is set to the user’s current language. Translations will automatically update for all supported languages whenever new content is added. Translations will automatically update for all supported languages whenever new content is added to reflect the latest changes.

If an Admin manually edits an auto-translated text, the system will not replace those changes with future translations. 

Viewing Translations

Once a study has received data from participants, admins can view the responses translated into their locale language by enabling the toggle labelled “ View translated content” located in the language dropdown from the navigation bar. 

When translations are enabled, all study content will appear in the selected language, creating a unified experience for reviewing responses.

Important Note: Certain platform areas do not currently support automatic translation:

  • Excerpting and Verbatims – Only original text can be excerpted to prevent translations from altering meaning when taken out of context.
  • AI-powered features such as Summaries, Themes, and Questions do not yet support translated content, ensuring AI-driven insights remain accurate.
  • Fill-in-the-blank task type – While translations are applied, additional language versions cannot be edited by the user.

Some visual elements like word clouds and charts remain unilingual, meaning translations are not applied to their text components.

Exporting Translations

When exporting study data, admins can select their preferred Export Language Preferences. 

The Language for Export will translate System-generated elements, including study configurations, task labels, and system messages.

User-submitted content such as participant responses and comments will remain in their original language unless the "Translate user-submitted content" toggle is enabled. This ensures flexibility in how raw data is shared and reviewed.

Note: AI-generated insights, Excerpts Reports, platform Messages, Word Data, and visual Charts remain in the original language to maintain their intended meaning, ensuring no loss of nuance during translation.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.