How to Build a Multilingual Mailchimp Sign-Up Flow With WPML

MailChimp Multilingual translates the form your visitors see. ibericode’s separate free MC4WP: WPML Integration plugin handles the per-language routing. Both are needed today; a single unified add-on is on the way (see the note at the bottom of this page).

Before You Start

Install and activate these on the same WordPress site:

• WPML core, WPML String Translation, and the MailChimp Multilingual add-on. Download it from your WPML account downloads page – it’s included with Multilingual CMS and Agency. This is the WPML side; it translates the sign-up form.
• Mailchimp for WordPress (MC4WP) from WordPress.org. This connects WordPress to Mailchimp and is the plugin you’ll build your sign-up form in. After activating, connect it to your Mailchimp account at Mailchimp for WP > Mailchimp.
• MC4WP: WPML Integration from WordPress.org, built by ibericode. This is the routing plugin that sends each sign-up to the right Mailchimp audience based on the visitor’s WPML language. It’s a separate free plugin today; we’re merging it into MailChimp Multilingual in an upcoming release.

You also need a Mailchimp account with at least one audience set up, and your WPML languages configured in WordPress.

WPML supports the MC4WP plugin only. Mailchimp’s own official WordPress plugin is a different plugin and isn’t covered by this add-on. If you’re on it, switch to MC4WP before continuing.

Build Your Sign-Up Form in MC4WP

Go to Mailchimp for WP > Forms and create a sign-up form in your site’s default language. Add the fields you want (email, name, opt-in checkboxes, GDPR consent text), the submit-button text, and the per-form success and error messages on the form’s Messages tab. MC4WP stores its messages per form rather than globally, so each form carries its own set.

When the form is ready, embed it where you want it on the site – a block in a page, a sidebar widget, a footer area, or a checkbox on the WooCommerce checkout or WordPress comment form via MC4WP’s integration settings.

Translate the Form With WPML

As soon as you save the form in MC4WP, it becomes available for translation through WPML – no scan required.

1. Go to WPML > Translations > Dashboard.
2. Scroll to the Mailchimp Sign-up Forms section.
3. Select the forms you want to translate and send them to your preferred translation method.

The translation job contains every visitor-facing string from the form: field labels, placeholders, submit-button text, opt-in checkbox labels and consent text (including raw HTML), and every success and error message from the form’s Messages tab. You don’t need to register strings manually.

If your consent text links to an internal page like your privacy policy, translate that page first. WPML rewrites the consent-text link to the translated page only if a translation exists at the time the form is sent for translation.

Route Sign-Ups to the Right Mailchimp Destination

The WPML add-on translates the form; per-language routing happens in MC4WP: WPML Integration. Its settings page is in the WordPress admin at Mailchimp for WP > WPML, and the page has two sections:

• Language map. A table with one row per WPML site language. For each language, pick the target Mailchimp audience from the dropdown in the Mailchimp list column. The default option -- use form or integration setting falls back to the audience configured on the form itself. (The dropdown still uses the older list label, but the destination is what Mailchimp now calls an audience.)
• Subscriber language. A single checkbox: Set the subscriber’s language based on the site language. Enable it so the subscriber’s language field in Mailchimp is set from the WPML language at submission time. Mailchimp uses that field to drive its language-aware features for the contact.

Save the page. From now on, a sign-up from a French page is sent to whichever audience is mapped to French and arrives in Mailchimp tagged with language: fr. The same routing logic applies to every other language on the site.

Design Your Mailchimp Side – Audiences, Tags, and Groups

Decide your Mailchimp structure before you finish configuring the routing. There are two viable patterns:

• One master audience, segmented per language. Mailchimp’s own recommendation. Map every WPML language to the same audience and rely on the language field (set by the routing plugin) plus tags, groups, and segments to drive per-language welcome flows and campaigns. One audience is cheaper to run (Mailchimp bills per audience) and easier to maintain.
• A separate audience per language. Use this when you want each language’s subscribers held entirely apart, with their own confirmation email, welcome email, and automation set. Map each WPML language to a different audience in the routing plugin’s language map.

Either way, the work to design the per-language welcome flows happens in Mailchimp, not in WordPress. Set up your audiences, tags, groups, and automations first, then come back to the routing plugin and finish the language map.

How Mailchimp Translates What WPML Doesn’t

Once a subscriber lands in Mailchimp, every email after that point is sent from Mailchimp – WPML and MC4WP are no longer in the loop. The split is:

For the Mailchimp-side content, Mailchimp offers three patterns to handle multiple languages: conditional merge tags driven by the subscriber’s language field, links to a Google-Translate version of the email, or separately designed translated emails sent to per-language segments. Most multilingual setups use either separate per-language audiences (each with its own confirmation and welcome email) or one audience with per-language segments and translated email versions.

Common Pitfalls

• Sign-ups are translated correctly but all land in one audience. The routing plugin (MC4WP: WPML Integration) isn’t installed, isn’t activated, or its language map is empty. Open Mailchimp for WP > WPML and configure the map.
• Forms aren’t appearing in the Translations Dashboard. Confirm the MailChimp Multilingual add-on is active alongside WPML core and WPML String Translation. The Mailchimp Sign-up Forms section appears in the Dashboard only when the add-on is active.
• The consent-text link points to the source-language privacy policy in a translated form. Translate the linked page before sending the form for translation. WPML only rewrites the link if a translation already exists at the time the form translation job is created.
• The double opt-in confirmation email arrives in the source language. That email is set up in Mailchimp, not on WordPress. Either send each language to its own audience (with its own confirmation email), or use Mailchimp’s conditional merge tags so the email body branches on the subscriber’s language field.
• Sign-ups are tagged with the wrong language. Confirm Set the subscriber’s language based on the site language is checked at Mailchimp for WP > WPML.
• The site uses Mailchimp’s official WordPress plugin instead of MC4WP. This add-on doesn’t cover that plugin. Switch to MC4WP: Mailchimp for WordPress to use this flow.

One Add-On Coming Soon

You need two compatibility plugins on top of MC4WP today: MailChimp Multilingual for the form translation, and ibericode’s MC4WP: WPML Integration for the routing. WPML and ibericode have agreed to merge the routing functionality into MailChimp Multilingual itself. After that release, you’ll only need MailChimp Multilingual on the WPML side, and the ibericode plugin will direct existing users to the unified add-on. We’ll cover the migration in the release notes when it ships.