Translating Email Content
Use Localize to help translate your email content.
There are a couple of ways you can use Localize to translate your email content.
Localize for Emails
With some of our subscription plans, you can use our Localize for Emails project type.
See our Quickstart for Emails guide for more information.
Static Email Content
For email content that doesn't change very much, you can use Localize to manage the translations of the content, using the Text Import method. You can read all about it here.
Semi-automated Email Content
You can manage translations of email content using our REST API, optionally with human translations.
Use Case:
- Send the contents of the email in separate phrases to Localize using the
Create phrase(s)
endpoint. - Use one of the various methods to get human translations for the phrases in the Localize dashboard.
- Human Translation Orders
- Invite translators to your Team
- Import/Export files for your translators to work in
- To get the translated version of the email contents, call the
Get Phrase(s)
endpoint for each phrase, sending in a hash of the source phrase. - You can then replace the contents in the email with the human-translated content.
"Real-time" Email Content
For emails that are created and delivered near-real-time, you can use our REST API to manage translations on-the-fly.
This method assumes you are using AI translations.
Use Case:
- Enable AI translations in your Project.
- Send the contents of the email in separate phrases to Localize using the
Create phrase(s)
endpoint. - Be sure to add the
label
"auto-approve" - this will auto-approve the translation of the phrase, generating a AI translation for the phrase. - To get the translated version of the email contents, call the
Get Phrase(s)
endpoint for each phrase, sending in a hash of the source phrase. - You can then replace the contents in the email with the AI-translated content.
Updated 2 days ago