How to utilize tokens for email translations?

Question

I have heard people mention using tokens to translate emails instead of using the "dynamic" email functionality. How do you utilize tokens to do this? I have not found any documentation / guides on this subject.

SanfordWhiteman · Accepted Answer

In a nutshell:You set up a common Velocity token with your translation map, let's call it $translatedText.. (Obvs. the linguistic part doesn't happen automatically!)#set( $translatedText = {  "subjectLine" : {    "en-us" : "... something...",    "es-mx" : "... algo... "  },  "footerText" : {    "en-us" : "... something...",    "es-mx" : "... algo... "  }} )‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍You store the lead's preferred language in a lead field, let's call it $lead.PreferredLanguage.Tokens output the appropriate value from the map, like${translatedText["subjectLine"][$lead.PreferredLanguage]}‍‍

Alex_Gladding · Answer

Hi Sanford, thanks for the detailed answer! This is very helpful.

Just so I understand, so the translation map gets stored in an email script token name something like {{my.translatedText}}, and then the outputs would be stored in separate email script tokens named something like {{my.subjectLine}} or {{my.footerText}}?

Or does the entirety of the script get stored in a single email script token? And if so, how is the correct token referred to in the email?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded