Mailchimp and Transglot, prepare campaign copy for more languages.
Choose Mailchimp in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.
Choose Mailchimp in the project’s CMS settings. Add a Mailchimp API key, which also names your data centre.
connect
02
Choose the content and locale mapping
Select the types and fields you want to localize. The connector reads campaigns: subject line, preview text and body. Map the source and target locales to your project.
map
03
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
审核
04
Deliver through your project
Pull the translated locale files through the API or CLI, or use the project’s CDN bundle. Mailchimp remains an import-only source.
deliver
Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Mailchimp is not part of this connector.
流动的内容
您可以翻译和交付的内容。
营销活动的主题行和预览文本,以及您映射的 HTML 或纯文本正文。由于 Mailchimp 营销活动是单语言对象,没有目标槽位,写入会替换您编写的副本,因此同步保持单向。
您可以翻译和交付的内容。
界面
预期效果
源内容与范围
营销活动:主题行、预览文本和正文
翻译输出
Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Mailchimp is not part of this connector.
注意事项
Import only. Your original Mailchimp content is read, and this connector does not write translations back.