Set up multilingual messaging
Last update: June 24, 2025
- Topics:
- Multilingual Content
CREATED FOR:
- Beginner
- Admin
The Adobe Journey Optimizer multilingual message feature allows you to effortlessly create content in multiple languages within a single campaign or journey. You can switch between languages when editing your campaign or your journey, streamline the entire editing process and improve your capability to efficiently manage multilingual content.
Learn how to set up translation projects for automated translation and the required language setting for manual translation and automated translation projects for multilingual messages.
Transcript
Hello, and welcome to our tutorial on how to set multilingual messages in AJO. Today, I’m going to walk through two different flows on how you can accomplish multilingual messaging in AJO, one being a more manual flow and one being a more automated flow that will allow you to connect to third party translation providers to provide your translation. Let’s jump in. As long as you have the correct permissions mentioned in the documentation, you should see this Translations option under the Content Management area. Let’s start here. The first thing I want to show you in this translations area is our locale dictionary. The locale dictionary lets you set up whatever type of locale region combination you may need. What’s important to note is that your locale region combination here that you add to your language dictionary should match how your language codes are stored in your profiles. So if your brand only stores language codes, for example, English, EN alone, then you would want to make sure you have all of your languages with just the first two letters of that code stored in this locales dictionary. I already have English added here. If I did not, it would allow me to save this here. However, if your profiles have multiple pieces of your language code, for example, if we wanted to do English in Canada, Then I would need to add those separately so that my language codes in my locales dictionary will match exactly to what they are as they are stored. On my profiles. So back to my locales dictionary, a lot of these language codes will come out of the box ready to use. But you’ll want to make sure you have all of the locales you need to set up your language settings in the first place. Now, if I’m going to use an automated translation flow, Where I am going to connect with a provider to do my translations, I’ll do some additional setup in this translations area of AJO. First, I’ll take a look at my providers. So here you can see that my instance has machine translation with Bing enabled. I’ve got a CSV upload flow enabled here. And I’ve also got a connection with the language provider RWS. So as long as I have these enabled, I will be able to send them to any of these options for translation at a later point. If I am going to use one of these providers, there is one other thing I need to look at in this translations tab for my setup, and that is creating a translation project. You can think of these translation projects as a grouping of communications that you may want to use the same language settings for. So for example, if I have a summer ad campaign that I am creating multiple messages for, I know I’m translating them all into the same languages. So I’m going to start mine in English. I’m going to have a target language of French and Japanese. Then I can create a translation project that will encapsulate all of those different communications and then I’ll be able to reuse that project. In order to create a project, I will hit Create Project. I’ll give it a name. I can give it a description. And then I will choose my source locale. So the source locale is whatever I am going to enable authoring for at the campaign level. So if I want to author my content in English, I will choose English. Additionally, the source locale here that you pick will be your fallback option. So in the case that a condition is not met on a certain profile, whatever you choose as your source locale here in your translation project will be what the fallback is for your communications. So I can also enable a review workflow by checking this box and or I could choose to automatically publish approved translations, whichever I prefer. Then I’m going to add my target locales and this will allow me to select a locale that I want to translate to and send it to whichever provider supports that. So if I do Spanish, once I click on it, it will highlight the provider that supports that language will appear here. So it may be multiple, it may be one. But since here I’ve got Spanish, it looks like Bing machine translation can do that. I’m going to say that’s the provider I’d like to use for this locale and then go ahead and add that locale. Let’s also do French. And it looks like I will be good to go. I’ll add that locale and press Save. So once I’ve completed my setup on my translation project for my automated flow, looks like I will be using our Bing machine translation for this example. I will go ahead and press Save. And then we can continue our setup in the admin section. So once you’ve created all of your locales and configured providers and projects if you were using an automated flow, you can then go down to the admin section and go to our channels option. Language settings, and then we’re going to do some additional configurations here. So language settings are what you need to configure to connect the profile preference that you’re using to the languages that you would like to execute. So when I create a language setting, I’m going to create two different ones for the different flows that I’m demonstrating. So let’s start with manual translation. This means that I’m not going to send my translations to a third party translator. And I am just going to copy paste out the details of each translation that I’m doing between the different messages and different locales. So I’m going to call this one July ad campaign manual. One thing to note is you can’t do spaces in this name. So if you get that error, check that. And then I’m going to do a similar exercise I did for my translation project. But this, since it’s manual, we just have to tell it which locales we want to use. So I’m going to choose English as my main locale. That’s going to pop up with a tag noting it is the primary version. I can delete it here or I can add others and change the primary there. Let’s also add Spanish. Let’s do Spanish for Spain and French. French. So if I wanted, for example, to make French my primary authoring in fallback, I would use these three dots and press Define as Primary. And it would then switch it and mark it as your primary authoring, which also means it would be your fallback language at this point. So I’m going to go and switch that back to English. And then this is the part that makes the language setting important. This sending preference is where we identify what preference attribute on our profiles is going to be compared to these languages that we have set up here. And at runtime, that means if my profile, for example, has French as my preferred language, then it would send the version of French that I author. So you can select any preference or profile language preference from any field in your profile. I am going to use preferred language. And go ahead and press Select. So now at runtime, it will look to that preferred language option and execute these that I author. I’m gonna save this and also create one for my translation project. You’ll see it will be very similar process. When I create my language setting, I’ll have the translation project. And here you’ll see that now I have the option to select my translation project. So since I just created that translation project, I am going to select it, this July ad campaign is what I called it. And you’ll notice once I select that, all of these locales down here are pre-populated since I’ve chosen them previously. And all I have to do is select my profile preference as I did in the manual flow. So I’m gonna use preferred language for this one as well. And we should all be good. I’m gonna press Submit. And now I am ready to start authoring my content in AJO. Thanks for joining this tutorial. We hope you have a great day.
Previous pageLock content in templates
Next pageCreate a multilingual message
Journey Optimizer
- Journey Optimizer Tutorials
- Use Cases
- Use Case Playbooks
- Introduction to Journey Optimizer
- Campaigns
- Journeys
- Journey Designer - Overview
- Discover the new Journey Designer
- Introduction to building a journey
- Use case - Transactional journey
- Use case - Business event
- Use case - Read audience
- Use case - Audience qualification
- Create a test profile
- Publish a journey
- Update content in a live journey
- Copy a journey to another sandbox
- Trigger daily journey runs after batch segmentation
- Troubleshoot inbound actions in journeys
- Conflict management
- Profiles, audiences, and subscriptions
- Channels
- Content Management
- Personalize content
- Personalization editor - Overview
- Profile and audience membership-based personalization
- Add offers as personalization
- Use contextual event information for personalization
- Use helper functions for personalization
- Use and manage saved expressions in the personalization library
- Create dynamic content with the condition rule builder
- Personalization editor playground
- Decision Capabilities
- Data Management
- Report and monitor
- Configuration
- Access Control
- Data Governance and Privacy
- Exercises and challenges
- Experience League Live show recordings
- Summit Labs