Follow

Guide to populating Survey Translation Import templates


 

Overview

For surveys with multiple languages enabled where automatic translations may not be available, or if you'd like to make edits/adjustments to the existing translations, the survey configuration pages ("Questions" and "Communications") allow you to action these directly in the platform. Please refer to the following support guides for further information / instructions:

Enable multiple languages in Culture Amp

Customize your survey communications

Alternatively, if you have a large amount of translations to add or edit, Culture Amp offer a bulk import option.

There are two imports available; one for the questions (including Sections & Factors) and one for the email communications (including Welcome Screen & Reporting Rules*).

*Please note that the Reporting Rules of a survey are not editable. Where automatic translations are not available and you're providing your own, the translation must not vary from the English version in terms of context and meaning. 

How it works

Once you have completed your survey and email communication design in the platform, you will need to reach out to Culture Amp Product Support so we can provide you with the question or email communication template in Excel format.  This is exported directly from your survey and will be specific to the current state of your survey and email communication design.

The Excel templates will contain a separate worksheet for each language you have enabled on the survey always including "en" (English; the platform default).  You'll use the file to add/update the translated text in the relevant worksheet(s) according to your requirements, prior to sending it back to us for import:

question_translation_example_file.jpg

In the above question translation file example you'll see the additional languages enabled on the survey are French (fr), Dutch (nl) and Italian (it), hence the 4 worksheets (including English (en) the platforms default language)

 

Important:

  • The translation file templates ALWAYS need to reflect the current state of your survey/email communication design in the platform.  This means if you have made any changes to your survey/email communication design since receiving the exported file(s), you'll need to reach back out for an updated version prior to populating it ready for import. 
  • The translation files cannot be used to make general changes to your survey design; they are only available for translated text additions/updates.
  • The translation files should be sent back in their entirety. All worksheets and columns are required for import purposes.
  • The coding (variables) in the Email Communication translation files must be kept/incorporated in the translated text; further details below.

 

File Population (for Question design)

  • Add your translated text or update the existing translated text in Column D ("Translation")
  • If a translation is added/updated, a "Yes" value will need to be shown in Column E ("Translation Required")
  • Save the file in its entirety
  • Send it back to us for import

    Additional information relating to the file for reference
  • "en" worksheet - use for reference only (do not delete or edit)
  • Column A ("Type")  - use for reference only (tells you what the row relates to, eg. Factor, Theme (Section) or Question. Do not delete or edit)
  • Column B ("Code") - use for reference only/ignore; codes are specific to your survey (do not delete or edit)
  • Column C ("Text to translate")  - use for reference only (shows the English version of the text for reference. Do not delete or edit)
  • Column D ("Translation") - this is where you add the translated text or update the existing translated text (do not delete)
  • Column E ("Translation Required") - if a translation is added/updated, a "Yes" value will need to be shown. (Do not delete)
  • Column F ("Notes") - add your own notes and use for reference only (will not affect or reflect in the translations. Do not delete)

File Population (for Email communication design)

  • Add your translated text or update the existing translated text in Column D ("Translated HTML"). Be sure to keep/incorporate any existing variables, such as %{account name},%{recipient_name} etc in the translated text.
  • If a translation is added/updated, a "Yes" value will need to be shown in Column F ("Translation Required")
  • Take note of whether the content is editable or not (Column E "Editable", Column B "Section" = restricted_content.  "No" in Column E means the content is not editable and existing translations should not be updated.  If you're providing missing translations, you'll need to ensure the translation does not vary from the English version in terms of context and meaning. 
  • Save the file in its entirety
  • Send it back to us for import

    Additional information relating to the file for reference
  • "en" worksheet - use for reference only (do not delete or edit)
  • Column A ("Template")  - use for reference only (tells you which communication the row relates to, eg. capture.welcome (Welcome screen), confidentiality.combined (Reporting rules), final (Email Final Reminder), invite (Email Invite), reminder (Email First Reminder). Do not delete or edit)
  • Column B ("Section") - use for reference only (tells you section of the communication the row relates to, eg content (main text body), subject (subject line of the email communication), restricted_content (non editable parts of the communications - also see Column E "Editable"). Do not delete or edit)
  • Column C ("HTML")  - use for reference only (shows the English version of the current text for reference. Do not delete or edit)
  • Column D ("Translated HTML") - this is where you add the translated text or update the existing translated text (do not delete). Be sure to incorporate any existing variables, such as %{account name},%{recipient_name} etc in the translated text.
  • Column E ("Editable") - indicates whether the text is editable (also refer to Column B ("Section" = restricted_content). "No" in Column E means the content is not editable and existing translations should not be updated. If you're providing missing translations, you'll need to ensure the translation does not vary from the English version in terms of context and meaning. 
  • Column F ("Translation Required") - if a translation is added/updated, a "Yes" value will need to be shown. (Do not delete)
  • Column G ("Notes") - add your own notes and use for reference only (will not affect or reflect in the translations. Do not delete)
Example file:
Email_communication_translations.jpg

 

Need further guidance / support?  Contact our Product Support Team and we'll be happy help!



Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

Comments