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.