Skip to main content
Participant Experience Language controls the language of the system-generated text on the pages your participants see. Set it once per study and Great Question shows its built-in interface, booking flows, screener and survey UI, consent forms, opt-out pages, and confirmation screens, in that language, without you translating any platform text yourself.
This is available on Enterprise plans (and trial accounts) — contact your Customer Success Manager or support if you’re on a different plan and need it enabled for your account. It’s also a separate feature from transcript or recording translation: this only affects the language of Great Question’s own interface, not the content of interviews you conduct.

What it controls

The setting changes the language of Great Question-hosted, participant-facing pages: the booking flow, the screener and survey interface, consent forms, opt-out pages, and confirmation screens.

Supported languages

  • English
  • French
  • German
  • Italian
  • Spanish
  • Brazilian Portuguese
  • Turkish

Setting the language

  1. Open your study settings.
  2. Under additional setup, go to Participant experience language.
  3. Select a language from the dropdown. It defaults to English.
  4. Save your changes.

What does and doesn’t get translated

Great Question translates the parts of the experience it generates — the survey and screener interface, booking pages, and confirmation screens. It does not translate the content you write yourself.
Researcher-created content, study titles, survey questions, landing page copy, and email text — stays in whatever language you write it in. It is not translated automatically.
Match your content to your system language. If you set the participant experience language to French, write your screener questions, landing page copy, and emails in French as well.

Troubleshooting

IssueWhat’s HappeningHow to Fix
Some pages show a mix of English and my chosen languageA handful of interface strings are missing a translation for certain languages and silently fall back to English when that happens.This is a known gap for those specific strings today — there’s no setting that forces full coverage. Let support know which strings you’re seeing so they can be tracked for translation.
A participant’s opt-out or manage-preferences page shows an unexpected languageThat page isn’t tied to any one study’s language setting — it resolves from the candidate’s own preferred-language attribute, or otherwise the language of their most recently created study, defaulting to English.If you need this page to be consistent for a candidate regardless of which study they came from, set their preferred-language candidate attribute directly.
Participants in the same study seem to be seeing different languagesChanging a study’s language only applies going forward — participants already invited keep whatever language was current when their emails and pages were generated.Decide on a language before sending invitations. Treat a mid-study change as forward-only, not a re-translation of communications already sent.
A study created via API or import shows a language-related error on participant-facing pagesStudy language only accepts one of the seven supported values; a value outside that list can surface as an error instead of a clear validation message.Set language from the dropdown in study settings when possible. If setting it via the API, confirm the value is one of the supported language codes first.

Still need help? Contact us at support@greatquestion.co — median response time is 19 minutes during support hours.