All Collections
Public | ENGAGEMENT HUB
Language Translation
Creating a survey or meeting in another language (with language-specific link)
Creating a survey or meeting in another language (with language-specific link)

Translate any survey, page, or meeting using Google translate, with the option to manually translate or modify specific language.

Jay Dawkins avatar
Written by Jay Dawkins
Updated over a week ago

Any project can be translated to another language using any of Google Translate's supported languages, and the tool has a powerful "last mile" translation option where native speakers can modify the auto-translated survey.

Note: It is important to finalize your survey in English before creating the translation. Otherwise, you'll need to make edits to each translation of the survey each time you make edits to the original. Changes made to the survey in English will not automatically update in the translated version and will require last-mile translation.

To create a custom link, you'll need to do one of the following:

1. Click the Settings tab. 

OR

2. Click the arrow to the right of the View Live Site button in the top right corner. You'll then select Custom Language Links from the drop down menu, which will take you to the Settings tab.

In either case, you'll see the Build Custom Link section on the right of the page. Here you can create custom links for content, e.g. surveys, in different languages. 

Note: When you create a custom link, it is a new link for a translated survey; the original link is not modified.

Step 1: Enter a unique shortcode. It is helpful to include the language your survey is translated in, in this case, Spanish.

Step 2: Ensure your shortcode:

  • does not contain spaces

  • is at least five characters

  • is not currently be in use

If any of these criteria are not met, the system will alert you. In the example below, the three green checkmarks indicate all criteria have been met:

Step 3: To create a custom link for a translated survey, select a language from the Default Language drop-down, e.g. Spanish.

*Optional: You can assign people who arrive at this link to a specific segment (audience group). You can assign them to an existing segment, or create a new one. This is helpful if, for the purpose of our example, you wanted to create a segment of Spanish-speaking users for a campaign. You can later filter results by your "Spanish Speakers" segment, or, reach out to your Spanish-speaking audience in their native language. 

To create a URL-specific segment, select Create New Segment from the Add visitors to segment drop-down menu. Type the name of your segment in the Segment Name text box that appears below.

Note: You cannot go back and create a custom link segment later! This must be done when you're creating your custom link. Be sure to do this before you launch your survey.

Click Create Link!
This will create a custom URL, (as well as a QR code) to which you can redirect those users who want to view your survey in Spanish. You'll see the URL + QR code below. 

Tip: Click the Gears icon (circled in green above) to edit or tweak the automated Google translation, ensuring it is in line with what native speakers would expect. 

Now you can use this custom link to direct participants to a language-specific version of your survey. You can do this multiple times for as many languages as you need. French, Russian, Japanese, you name it!

Note: Once any content blocks or questions are manually translated, these content blocks and questions will not automatically receive updates when the parent English survey is modified. As a result, it's best to finalize your parent English survey before customizing translations

Note: Once any content blocks or questions are manually translated, these content blocks and questions will not automatically receive updates when the parent English survey is modified. As a result, it's best to finalize your parent English survey before customizing translations.

You may also modify the automated translation using our "last mile" translation tools:


Did this answer your question?