The translations page
The translations page is a dedicated workspace for everything language-related on a study. It is separate from the Build tab so you can focus on copy without changing structure or logic.
How to open it
Section titled “How to open it”- Go to Surveys, Usability Tests, or In-Product Surveys.
- Find your study in the list.
- Click Translations on the study card.
You can also add languages during the creation wizard; the translations page is where you maintain them long term.
Use Back (top of the page) to return to the study editor — you will go back to the page you came from when possible.
What you see on the page
Section titled “What you see on the page”The translations workspace is built around a few main areas:
| Area | Purpose |
|---|---|
| Language list | Languages attached to this study, with progress per language |
| Default language | Source text participants fall back to; usually the language you built first |
| Translation tree | Study title, pages, and questions organized like your study structure |
| Editor panel | Original text and translation side by side for the field you selected |
| Search and filters | Find strings quickly; filter by translation status |
| Import / export | Excel workflows for agencies or offline review |
| AI translation | Bulk or single-field AI drafts (see AI-assisted translation) |
Add a language
Section titled “Add a language”- On the translations page, click Add language.
- Pick from the language catalog (e.g. French, German, Arabic).
- The new language appears in the list with 0% progress until you translate content.
You can add multiple languages to the same study.
Set the default language
Section titled “Set the default language”The default language is the source of truth for structure and for any missing translations.
- One language is marked as default (often the language you used in the builder).
- To change default: use Set as default on another language — you cannot delete the current default until another is chosen.
Participants may see default-language text if a field is not yet translated (depending on study settings).
Translate in the tree view
Section titled “Translate in the tree view”- Select a target language (not the default) in the language list.
- Expand the tree — study header (title, description), pages, questions, answer options, thank-you messages, etc.
- Click a field that needs translation.
- Type or paste text in the translation panel.
- Changes save as you work.
The tree follows your study layout (including usability test tasks and prototype-related labels where applicable).
Translation status
Section titled “Translation status”Each string can have a status such as:
| Status | Meaning |
|---|---|
| Pending | Not started |
| In progress | Started but not finished |
| Completed | Translated, may still need review |
| Reviewed | Marked ready for participants |
Use status filters to focus on what is still outstanding.
Progress per language
Section titled “Progress per language”Language cards show how many strings are translated compared to the default language. Use this to prioritize before launch — e.g. “German 100%, Japanese 40%”.
Search
Section titled “Search”Use search to find text across questions and messages when you need to fix one term everywhere (e.g. product name spelling).
Excel import and export
Section titled “Excel import and export”For large studies or external translation vendors:
- Export — download an Excel file with original and translated columns
- Import — upload completed Excel to apply many translations at once
After import, review critical strings in the tree — especially legal text and scale labels.
Right-to-left (RTL) languages
Section titled “Right-to-left (RTL) languages”For languages such as Arabic or Hebrew, the interface supports RTL preview and direction so you can check layout before participants see it.
In-product surveys: language selection
Section titled “In-product surveys: language selection”On in-product surveys, the translations page may also include language selection settings — how the SDK or embed picks a language (browser language, URL, variable, etc.). Save those settings from the same page when shown.
Variables shown on the page
Section titled “Variables shown on the page”Some studies list variables (URL parameters, session data, etc.) that affect language detection for in-product display. These are the same variables you define under Logic & Variables.
What to translate (checklist)
Section titled “What to translate (checklist)”- Study title and description
- Welcome and thank-you content
- Every question title and help text
- Answer options, matrix rows, scale labels
- Legal / screener pages
- Error or validation messages participants might see
Before you publish
Section titled “Before you publish”- Select each target language and spot-check the first and last screens in Preview.
- Confirm progress is acceptable for every live language.
- If you use per-language links, copy the correct link from Distribute for each audience.