Translate the MailChimp Embed Code

This feature requires Manager user level or higher.

Typically, the MailChimp signup form embed code is used as-is. After you build your signup form, you would copy the embed code and paste it into your site. To translate parts of the embedded form code, you'll change the code by hand.

This is an advanced feature and is recommended for users familiar with custom coding. Our Support Team won't be able to troubleshoot issues with your custom code, so we recommend that you contact your developer, or hire a MailChimp Expert if you need assistance.

Below, you'll learn how to translate the signup form embed code.

Translate the Embed Code

English is the default language for field labels, the subscribe button, and the form's title. Any field labels you translate in the Form Builder, however, will appear in the form embed code.

Form Title

To edit or translate the form title for your embedded form, follow the steps below.

  1. Navigate to the Lists page.
  2. Click the drop-down menu next to the list you want to work with and choose Signup form.
  3. Select Embedded forms.
  4. Under Form Options, update the form title in the field provided.

Field Labels and the Subscribe Button

To update field labels and the subscribe button, you'll have to make changes directly to your embed code HTML, and update the code on your website with the modified version.

After you've followed to the steps above to access your embedded form, follow the steps below.

  1. Click anywhere in the Copy/paste onto your site field and highlight all of the form code.
    Select embed form code
  2. Copy the code, and paste it into your preferred plain-text or HTML editor where you can make edits to it.

Translate Email Address field label

Search or browse your code for this HTML.

<label for="mce-EMAIL">Email Address <span class="asterisk">*<span></label>

Then, replace "Email Address" with the equivalent name in the translation language. For example:

<label for="mce-EMAIL">Dirrección de Correo Electrónico <span class="asterisk">*<span></label>

Follow these steps for every field label you want to translate.

Translate the Subscribe button

Search or browse your code for this HTML.

<input type="submit" value="Subscribe" name="subscribe" "id="mc-embedded-subscribe" class="button"></div>

Then, replace "Subscribe" in the value element with the equivalent label in the translation language. For example:

<input type="submit" value="Suscribirse a la lista" name="subscribe" "id="mc-embedded-subscribe" class="button"></div>

Translate Form Success and Error Messages

Super Slim Form

When a subscriber successfully signs up via the Super Slim form, they are directed to the Signup "thank you" page automatically. This page will appear in the language you set, or the language set in the subscriber's browser settings if you have the Auto-Translate feature turned on.

If there are errors on the form, however, subscribers see either the Signup form with alerts or they'll see HTML5 form validation messages. Either way, the subscriber will see the language you've set in the Form Builder or their preferred browser language.

Classic Form

The Classic Form utilizes a validation plugin to present success and error messages when someone fills out your form. The translations for the success and error messages are generated statically when the embed form is created. These default messages will appear in the Classic Form embed code only when your default language is set to a language other than English. The static messages can be translated manually within the form code.

We have translations available in the following languages (full files available here):

  • Arabic (ar)
  • Bulgarian (bg)
  • Basque (eu)
  • Catalan (ca)
  • Chinese (cn)
  • Czech (cn)
  • Danish (da)
  • Dutch (nl)
  • Greek (el)
  • Persian (fa)
  • Finnish (fi)
  • French (fr)
  • Georgian (ge)
  • German (de)
  • Hebrew (he)
  • Hungarian (hu)
  • Italian (it)
  • Japanese (ja)
  • Kazakh (kk)
  • Latvian (lv)
  • Lithuanian (lt)
  • Norwegian (no)
  • Polish (pl)
  • Portuguese- Brazil (ptbr)
  • Portuguese- Portugal (ptpt)
  • Romanian (ro)
  • Russian (ru)
  • Serbian (sr)
  • Slovak (sk)
  • Slovenian (sl)
  • Spanish (es)
  • Swedish (se)
  • Taiwanese (tw)
  • Thai (th)
  • Turkish (tr)
  • Ukrainian (ua)
  • Vietnamese (vi)

​When a subscribe attempt is passed along to our servers, additional messages are shown based on the default language you've set in our visual form builder or auto-translated based on the subscribers browser language setting:

Translate the Default Validation Messages

  1. Locate the following line in your form embed code:
    Default validation message
  2. Replace any of the text values within quotation marks with your own custom translations.
  3. Copy the complete, updated code to your website.

To translate the validation messages without setting the default language to something other than English:

  1. Download this file and copy the code.
  2. Paste the copied code before the /script tag at the end of the embed code.
    Edit translation errors
  3. Replace the validation messages within quotation marks with your own custom translations.
  4. Copy the complete, updated code to your website.

Just like the Super Slim Form, subscribers who fill out your Classic Form may see HTML5 validation messages produced by their web browsers before the form data is passed along to MailChimp's servers.

Translate the Success Message

  1. Log in to your MailChimp account.
  2. Navigate to the Lists page.
  3. Click the drop-down menu for the list you want to work with, and choose Signup forms.
  4. Select General forms.
  5. Click the Signup form drop-down menu, and choose Signup "thank you" page.
  6. Click the Translate it tab.
  7. Translate any desired fields. 
  8. Click Save Translation Settings.

Naked Form

Like the Super Slim Form, the Naked Form will direct to your hosted Signup Thank You page when the form is submitted successfully. If the form is not submitted successfully, subscribers will be brought to your hosted Signup Form with Alerts or see brower-based validation messages in cases when form information isn't included.

Was this article helpful?
What can we do to improve articles like this?

Technical Support