Each field can be translated into multiple languages to provide a localized user experience. Translations apply to both the Label (Name) and the Placeholder of the field.
- Language – choose the target language from the dropdown.
- Name – the translated label that will be shown to the user.
- Placeholder – the translated helper text displayed inside the input before it is filled.
You can add multiple translations for the same field by clicking Add. Each translation can be managed individually, and existing translations can be removed if no longer needed.
Additionally, translations can be imported or exported in bulk using the Import and Export buttons. This is especially useful when maintaining large forms or when collaborating with professional translators.
The language of the form is controlled in the Form Settings and depends on the chosen form design. Once a language is set for the form, the corresponding translations for each field (Name and Placeholder) will be applied automatically.
What a translation does not change
The form language only changes the labels and placeholders shown to the user. Everything else stays the same:
- The system name of the field, which is what integrations map and what the API expects.
- The values behind Select and Radio options. Only their labels can be translated, so an advertiser receives the same value whichever language the visitor saw.
- Validation, Modify and AutoComplete, which run identically in every language.
That last point is the one that catches people out. A phone regex written for one country’s format does not become a different regex because the form is shown in another language, and an address service that only covers one country still only covers that one.
When a translation is not enough
If you need a form in a specific language with its own validation rules, its own scenarios, or different fields, create a separate form structure instead of relying only on translations.
A rough line to draw:
- Same fields, same rules, different words is a translation.
- Different rules, different scenarios, or different fields is a second structure.
A missing translation is not an error
If a field has no translation for the language the form is set to, the original label and placeholder are shown instead. Nothing breaks and nothing is reported, so a partly translated form looks finished from the admin side and mixed to the visitor.
Use the Export button to see which fields are still missing, rather than clicking through the form.
