Using localization with Appcues means you can use a single Appcues flow to reach a multilingual audience.
- Define the languages you support once
- After a flow is built, tested, and ready for the big time, export the content (via CSV or JSON) for your team to translate.
- Once the content is translated, re-uploaded it into Appcues, and it will be displayed for speakers in their preferred language.
In this article we'll cover:
To get started, head to Settings, and choose the Localization tab.
To enable localization for your content:
First, define the languages your platform supports. This is set on the account level and only needs to be done once. Appcues will use these settings when targeting your content to end-users.
To set each language, type the name of the language you'd like to support (ie. German). Then select the targeting criteria you'd like to use to identify those users. You can use our default property `Last Browser Language`, which Appcues automatically tracks or you can use any property sent in via your installation. We will use these conditions to determine which translated content to show to your users.
Browser languages are set by your end users and can be as broad as French (FR) or as specific as French - Canadian (FR-CA). Appcues will target specific codes set by the browser, so in order to cover all variations, we encourage adding all them to your language definition. If you plan to support a different version for a given language, keep them as a separate line.
Note: Any users with languages not defined on this list will fallback to see the flow in the original authored language.
Localizing your content
Once you've defined the languages you'd like to support, find the area labeled Localization in your flow settings page.
To retrieve your flow's contents for translation:
Click " Download Content". We'll send you a zip file (either CSV or JSON, with a corresponding file for each language in your locales list).
Once exported for translation, the content for the flow will not be editable. You will only be able to edit styling and positioning. We recommend only localizing content once it has been finalized.
When the translations have been completed (in whatever manner you translate content today), upload each file to the corresponding language. Once translations are uploaded and processed, you're ready to hit Publish!
Any users that are identified and do not have a corresponding translation file will see the flow in the original authored language. If you have a flow that you only want to show to 3/6 of your supported languages, be sure to target them appropriately via Audience Targeting.
Note: To best support as many languages as possible, Appcues flow localization uses the UTF-8 character set for all CSV imports and exports. Most modern tools (Google Sheets, Apple Numbers, LibreOffice) will by default handle these files. If you are using Microsoft Excel for your translations, you may need to take a couple additional steps to import and export translation steps. Learn more here.
Previewing your translated content:
To preview your translated flows prior to publishing, click View next to your uploaded translation.
Why is the Localization section disabled on my flow settings page?
When your flow is published, you cannot edit the localization section. If you'd like to make changes to your translations, you'll need to first un-publish the flow.
How do I edit a flow that's already been localized?
Once your flow has been localized for translation, you cannot edit the contents of the flow, you can only edit the styling and positioning of content. If you'd like to make changes to the flow content, you'll need to clone the flow and then edit the new copy.
How can I test my translated content?
Because of how our flow test mode works, the test mode version of a flow with localizations may not show accurate content. The best way to test your flow and any translated content is to publish it live to just your user account, then change your browser's language.
Should I change my content's format to account for localization?
Yes, we recommend using the 'X' button instead of 'hide these tips' for tooltips and hotspots. When working with translated content, you will find that the character count will vary and can result in a poorly formatted tooltip. For example, 'hide these tips' in Spanish is 'esconde estos consejos'.
Do you support translation of the "Next" and other custom buttons?
Why are some pieces of text on a different row in my CSV?
If you've applied styling to a single line of text, Appcues will break it out onto it's own row to maintain the styling. For example, on the below tooltip, favorite is italicized.
Here is what that looks like in your CSV:
It's important to note here, that because of the line breaks, there will be spaces included in the CSV lines. Be sure to include those in your translated column as well to ensure correct spacing.
Does this work for NPS?
NPS must be localized separately. To change the language of your NPS survey, please reach out to us at email@example.com. Please note that we don't currently support multi-language NPS surveys, so only one language will be displayed.
Can you localize flow titles in Launchpad?
Unfortunately, no. Right. now we do not support localizing flow titles in Launchpad.
Can you localize Checklists?
While the flows themselves will be localized, the checklist is not able to be localized at this time.
Do I have to unpublish flows to localize them?
Yes, you do have to unpublish your flows in order to localize them. What we recommend is cloning the flow, leaving the old version live, localizing the new cloned version and then publishing it for minimal downtime.
How do you handle the CSV and JSON exports?
There is one download per flow, and within that download are individual files for each language. When you upload, you upload each individual language file.
What languages does Appcues support?
Please note that we do not support styling for right to left languages (i.e. Hebrew and Arabic), so content will be displayed like all other content, left to right.