Connect Mailchimp
Import Mailchimp campaign subject lines, preview text and content into transglot for translation.
Import only
Nothing is written back to Mailchimp. A Mailchimp campaign is single-language and has no per-language slot to write into. Take the translations out through the REST API, the transglot CLI or the CDN.
| Direction | Import only |
| Imported | Campaign subject line and preview text, and optionally the HTML and plain-text content |
| Written back | Nothing |
| Sync | Sync from CMS |
| Per sync | Up to 2,500 campaigns |
| Plan | Starter and above |
Before you start
Create an API key in your Mailchimp account's API key settings. It ends in your data center, for example -us21.
Connect
Open your project's settings, choose CMS, and pick Mailchimp in the CMS list. There is no URL to type: transglot reads your data center from the end of the API key.
| Field | What to enter |
|---|---|
| API key | Your Mailchimp API key, for example 0123…abcde-us21 |
| Content types | campaigns |
| Translatable fields | Any of subject_line, preview_text, html, plain_text |
Select Connect, then Test connection. A successful test names the data center, for example Mailchimp (us21).
What gets imported
transglot reads every campaign in the account. The subject line and preview text come from the campaign's settings. When you map html or plain_text, transglot also reads each campaign's content. If one campaign's content cannot be read (for example a campaign with no content yet), the sync still imports its subject line and preview text and moves on.
Troubleshooting
- The form refuses the key: it must end in a data center suffix, such as
-us21. Copy the whole key from Mailchimp. ... the credentials were rejected.The key is wrong or was revoked.... the campaign was not found, check the data center.The key's suffix does not match your account's data center.... Mailchimp is rate-limiting the request, retry.Wait and run the sync again.