Skip to main content

Tutorial

Mailchimp WordPress Integration: Subscribe From Your Own Form

Connect a WordPress form to Mailchimp with an API key and an audience ID, including double opt-in. The older Mailchimp for WordPress action still works if you already use it.

Some links here are affiliate links. If you buy through one, I earn a commission at no cost to you. Core Forms is mine, so weigh my bias there too.

A Mailchimp WordPress integration subscribes the person who submitted your form to an audience you already have. In Core Forms the current way is the Subscribe to Mailchimp (API) action: an API key, an audience ID, and the email field. Double opt-in stays on unless you turn it off.

I build Core Forms. The Mailchimp integration page is the short version of the same action. Mailchimp’s own embed is the other way, and it pulls in a lot of script for one email field. I measured that embed at about 90 KB on a fresh page. You do not need it.

Subscribe with the API action

  1. In Mailchimp, create an API key under Account, Extras, API keys. Copy the whole key, including the datacenter suffix.
  2. Copy the audience ID from the audience settings.
  3. On the form, open Actions and add Subscribe to Mailchimp (API).
  4. Paste the key and the audience ID.
  5. Map the email field. Map first name and last name if you collect them.
  6. Leave double opt-in on for a new contact unless you already have permission to subscribe them immediately.
  7. Save, then submit with your own address and finish the confirmation email before you call it done.

Existing subscribers are updated by email. The action does not reset a status that Mailchimp already has, and it does not create a second contact for the same address.

Custom audience merge fields can be sent as JSON that uses the form’s field tokens. That is optional. An email-only form does not need it.

If you want retries on a failed request, enable background processing for the form. The success message should mention the confirmation email whenever double opt-in is on. The newsletter confirmation example is the wording I use.

Build the signup form

In Core Forms, Add new form. The HTML is just an email input and a submit button:

<p>
  <label for="email">Your email</label>
  <input type="email" name="email" id="email"
         placeholder="you@yourdomain.com" required />
</p>

<p>
  <button type="submit">Subscribe</button>
</p>

That’s the whole form. No first name field. Most signups die on extra fields. Get the email first, and ask for the name in a welcome email.

The older path: Mailchimp for WordPress

Sites that already use the free Mailchimp for WordPress plugin can keep that action. It is still there. New setups should use the API action above so the form does not depend on a second plugin.

If you are on the older action:

  • Install Mailchimp for WordPress and paste the API key into that plugin.
  • On the form, add the Mailchimp action, pick the audience, and map email to EMAIL.
  • Leave double opt-in on unless consent is already sorted.

Save.

The success message

In the form’s Messages tab, set the success message to something specific:

Check your email for a confirmation link. We’ll only send the newsletter once it’s confirmed.

Generic “Thanks for subscribing!” leaves users wondering why they didn’t get the newsletter. Telling them about the double opt-in step prevents the support emails.

Put it on the page

[cf_form slug="newsletter"] works in posts, widgets, the Gutenberg block, the footer, anywhere shortcodes go.

The whole form, JavaScript and CSS, lands at about 5 KB. Versus 90 KB for Mailchimp’s official embed. On a 3G connection, that’s the difference between a form that loads instantly and a form that loads after the rest of the page.

What this gets right

Double opt-in works. Mailchimp’s confirmation email fires the same as it would from their native form. The user clicks confirm, they’re subscribed.

Merge fields work. Email, first name and last name map directly. Extra audience fields can be sent as JSON that uses the form’s tokens. Tags are a Mailchimp-side job unless the older Mailchimp for WordPress action is the one you kept.

No iframes. Some Mailchimp embed templates use an iframe. Iframes break ad blockers and screen readers. Native HTML doesn’t.

No Mailchimp branding. Their official forms include “powered by Mailchimp” footers. Yours won’t.

Where this falls short

No native captcha on the Mailchimp side. You’re not using their built-in spam filtering. Layer reCAPTCHA v3 or Cloudflare Turnstile on the form (one click in Core Forms settings) and you’ll catch more spam than Mailchimp’s default would.

No GDPR field auto-rendering. Mailchimp’s native forms can render GDPR consent checkboxes from your audience settings automatically. Core Forms doesn’t pull those. Add the consent checkbox manually as a form field.

Audience subscription only. This pattern subscribes users to one Mailchimp audience. If you need to subscribe to multiple audiences (rare) or split between audiences based on a field value, you’ll write that as a conditional action.

The MailerPress alternative

If you don’t have Mailchimp opinions yet, look at MailerPress. It’s a self-hosted WordPress-native ESP, no API key, no third-party plugin. The setup is shorter and you keep your subscriber data on your own database. If you also sell with FluentCart, the FluentCart to MailerPress guide shows how paid customers get tagged without anyone being subscribed by a purchase.

Mailchimp’s strength is deliverability and well-known templates. MailerPress’s strength is “no rate limits, no quotas, no third-party privacy policy.”

Pick on those terms, not on what’s “popular.”

The next step

Replace one Mailchimp embed on your site with a Core Forms signup. Test the double opt-in. Check the bundle size in DevTools.

The reduction is real. So is the conversion bump on slow connections, where the page actually loads before the user gives up.

Both Mailchimp and MailerPress are bundled at every plan level. Pricing.

For the plugin’s own Newsletter signup template and the actions for MailerLite, MailerPress, FluentCRM and the rest, the newsletter signup form guide builds it step by step, and the newsletter plugin comparison covers keeping the list in WordPress.

Build the form. Stop reading.

Every note here came out of a real Core Forms setup. Use code BLACKFRIDAY for 40% off either plan. Ends December 2 (IST).

Black Friday Sale

40% off Core Forms

Forms, polls, surveys, payments, and licensing — every feature, unlimited sites, one plugin.

Copy your code

Those are the after-discount prices. Paste BLACKFRIDAY at checkout to apply it. BLACKFRIDAY40 works too.

Ends December 2 (IST)