At Knak we have noticed that users are using Dynamic Content to translate their emails instead of creating a net new email for each target language. In other words, they build a single email and use dynamic content to create variables for each language they want to send to. This is not recommended as a best practice by our team here at Knak, and here are some reasons why:
1. Having all languages under a single email can cause additional delay to launch
For example, the entire global campaign could be held up because a particular language is still being reviewed within the master email.
2. Generating separate emails for the various languages is less risky.
The surface area if something goes wrong with the email is less if it is broken apart.
3. Using dynamic segmentation to translate an email makes utilizing dynamic content for other segmentation exponentially complex.
For example, if you have 10 languages, that’s 10 segments under the same email. But then if you also want to segment by industry, country….etc. You will need 50+ versions under the same email.
FAQ: It may not be considered a "best practice" but do I have to change my current workflow of translating individually through Dynamic Content if it's working well for me?
Not necessarily! If you want to translate using dynamic content you can achieve this via our dynamic content feature for Marketo or SFMC. If this process is something you are inherently comfortable and familiar with, go right ahead! We just want to educate new Knak users about the differences between translating a full email compared to translating through Dynamic Content.
FAQ: I would like to learn more about Translations from Knak, how can I find out more information?
You can learn more through these Help Documents here:
Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com