Deepfield supports multilingual surveys, allowing you to reach participants around the world in their preferred language. This increases response quality and broadens your research reach.

Why Multilingual Surveys?

Higher quality responses - Participants understand questions better in their native language
Broader reach - Access participants in different regions
Cultural accuracy - Adapt content for local context
Better completion rates - Reduced drop-off from language barriers

How It Works

Language Selection

When participants access your survey:

The system detects their browser language preference
If available, shows the survey in that language
Participants can switch languages if multiple are available
All responses are tracked with language metadata

Translation Management

Your survey has a primary language (the one you create it in). Additional languages are added as translations of the primary version.

Primary Language: English
├── Translation: French
├── Translation: Spanish
├── Translation: German
└── Translation: Japanese

Supported Languages

Deepfield supports surveys in many languages including:

Language	Code
English	en
French	fr
Spanish	es
German	de
Portuguese	pt
Italian	it
Dutch	nl
Japanese	ja
Chinese (Simplified)	zh
Korean	ko

Contact support for additional language requirements.

What Gets Translated

Survey Content

Element	Translated
Question text	Yes
Answer options	Yes
Matrix row labels	Yes
Section titles	Yes
Instructions	Yes
Stimulus captions	Yes

System Text

Standard interface elements (Next, Submit, etc.) are automatically localized based on the selected language.

Setting Up Multilingual Surveys

1. Complete Primary Language

Before adding translations:

Finalize all questions and logic
Complete screening questions
Add all answer options
Test thoroughly

Changing the primary version after translation creates extra work.

2. Add Languages

Navigate to the translations section
Click Add Language
Select the language to add
Begin the translation process

3. Translate Content

For each language:

Review auto-translations (if available)
Edit for accuracy and cultural fit
Test the translated version
Validate all paths work correctly

4. Review and Publish

Before launching:

Have native speakers review translations
Test each language version completely
Verify screening logic works in all languages
Confirm quotas are language-appropriate

Translation Quality

Auto-Translation

Deepfield can auto-translate survey content as a starting point:

Saves time on initial translation
Requires human review for accuracy
May miss cultural nuances
Best for straightforward content

Professional Translation

For high-stakes research:

Export translation files
Send to professional translators
Import completed translations
Have native speakers verify

Review Guidelines

When reviewing translations:

Accuracy - Does it mean the same thing?
Naturalness - Does it sound native?
Context - Does it fit the survey context?
Length - Does it fit the UI? (especially buttons/options)
Cultural fit - Is it appropriate for the audience?

Analysis Across Languages

Response Aggregation

By default, responses from all languages are combined in analysis. You can:

Filter analysis by language
Compare results across languages
Export data with language identifiers

Reporting

Reports can include:

Overall findings (all languages)
Language-specific breakdowns
Cross-cultural comparisons

Best Practices

Survey Design

Keep questions simple - Easier to translate accurately
Avoid idioms - They don't translate well
Use universal concepts - Some ideas don't exist in all cultures
Be consistent - Use the same terms throughout
Allow for text expansion - Some languages need more space

Translation Process

Translate, don't transcreate - Unless cultural adaptation is needed
Maintain meaning - Accuracy over elegance
Test with speakers - Have native speakers review
Document decisions - Note any cultural adaptations

Recruitment

Set language-specific quotas - If you need balanced samples
Use appropriate panels - Some panels specialize in certain regions
Consider time zones - For global launches
Account for costs - Some languages/regions cost more

Troubleshooting

Text Doesn't Fit

If translated text is too long:

Rephrase more concisely
Adjust UI elements if possible
Consider using abbreviations where appropriate

Logic Issues

If conditional logic behaves differently:

Verify translation of trigger values
Check that option values match
Test all conditional paths in each language

Missing Translations

If some content isn't translated:

Check for newly added questions
Sync translations with primary version
Review the translation status dashboard