Knak AI and Manual Translations

There are two types of translations that can be used in Knak - Manual and Automatic translations For each language selected to translate, you are able to select if they want to use “Automatic” or “Manual” translation.

You can create variants of the email with an assigned language but not changing any text.

You can send an asset for automatic translation

You will receive notification when a translation job is completed for both manual and automatic translation.

Translation variants have a parent-child relationship. If a design element is changed in the parent, you can push the changes down to the child. This mean less manual updating between variants for you - and that you can make design changes in the email and it will flow to the all the language variants.

However, this is not forced. Users can choose to do it or not.

When adding merge tags into translations, we have handling for knak merge tags added through the text editor dropdown that will ensure the translation service ignores those tags. An error will appear if the tags are copied directly into the asset. Therefore we won't know which parts of the text are tags that need to be ignored by the translation.

When you add dynamic content to your base asset and push changes to a translated variant, you may notice unassigned dynamic content. This happens because:

- Local segments created in the base email are specific to that email only

- When pushing content to translated variants, only the content itself is updated - not the segments

You have two options to resolve this:

1. Create and assign new segments in the translated email

2. Use global segments instead (learn more here), which lets you reuse segments across emails without rebuilding conditions

Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com