Klaviyo and Transglot, bring email copy into your language workflow.
Choose Klaviyo 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 Klaviyo in the project’s CMS settings. Add a Klaviyo private API key.
connect
02
Choose the content and locale mapping
Select the types and fields you want to localize. The connector reads email templates: name, html and text. 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. Klaviyo remains an import-only source.
deliver
Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Klaviyo is not part of this connector.
傳輸內容
您可以翻譯並交付的內容。
電子郵件範本名稱及其 HTML 或文字內文。由於 Klaviyo 範本為單語，雖然存在更新端點，但指向該單一範本，發布將會取代原有內容而非新增語言版本，因此僅支援單向同步。
您可以翻譯並交付的內容。
表面
預期結果
來源與範圍
電子郵件範本：名稱、HTML 與文字
翻譯輸出
Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Klaviyo is not part of this connector.
注意事項
Import only. Your original Klaviyo content is read, and this connector does not write translations back.
