Loading…
Loading…
Jotform to Mailchimp, wired so signups land on the right audience with the right tags and merge fields, not as orphaned contacts.
The Jotform to Mailchimp integration exists to do one thing well: take a form signup and turn it into a Mailchimp subscriber without a CSV in the middle. Someone fills out your newsletter or lead form, and they land in your audience, ideally with their name, interests, and a tag that says where they came from. For list-building, it removes the manual import step entirely.
Where teams get tripped up is the structure underneath. Mailchimp organizes contacts into audiences, merge fields, tags, and groups, and the form fields have to map to those exactly or data lands in the wrong place or not at all. Add double opt-in, which can quietly leave subscribers in a 'pending' limbo, and you get the classic 'my signups aren't showing up' problem. This page covers how the mapping works, where it breaks, and when you should route through a webhook instead.
I spent five years on Jotform's product team. The Mailchimp integration was popular and the source of a steady stream of 'where did my subscribers go' tickets. Here's how to wire it so contacts land clean.
In Jotform's Integrations tab you authorize Mailchimp and choose the target audience (list). Every submission adds a contact to that one audience. If you run multiple audiences, pick deliberately, because there's no automatic routing between them.
Email is required and maps to the subscriber's email. Other fields map to Mailchimp merge fields (FNAME, LNAME, and any custom ones you've defined). A field that has no matching merge field in Mailchimp simply won't carry over, so create the merge field in Mailchimp first.
You can attach a static tag (like the form's name or a campaign source) so you know where the contact came from, and map fields to Mailchimp groups/interests. Tags are the cleanest way to segment Jotform signups inside Mailchimp later.
If the audience uses double opt-in, the new contact is added as 'pending' and only becomes 'subscribed' after they click the confirmation email. With single opt-in, they're subscribed immediately. This setting lives in Mailchimp, and it determines whether your signups look 'missing.'
A simple email-and-name form adds subscribers to your main audience with a tag for the signup source. The cleanest, most reliable use of the integration, as long as merge fields and opt-in are set up correctly.
A gated-content form adds the contact and tags them by which lead magnet they downloaded, so you can send a relevant follow-up sequence. The tag is what makes the segment work later.
Registrants land in an audience or group tied to the event, ready for reminder and follow-up emails. Pair with a tag for the specific event so the next event's list stays separate.
A preferences form maps checkbox selections to Mailchimp groups so subscribers self-select what they hear about. Reduces unsubscribes, but only if the group structure in Mailchimp matches the form's options exactly.
If your audience uses double opt-in, new signups sit as 'pending' until they confirm via email, and they won't appear in your subscribed count or receive campaigns. People read this as 'the integration isn't working.' Decide intentionally between single and double opt-in, and if you use double, tell users to check their inbox.
Mapping a form field to a merge field that doesn't exist in Mailchimp means that data silently doesn't transfer. Create every custom merge field in Mailchimp before mapping, and match the merge tags exactly.
Mailchimp won't let you forcibly re-add someone who unsubscribed; the API rejects it to protect compliance. If a known unsubscriber fills the form again, they stay unsubscribed. That's by design, not a bug, and you can't override it from Jotform.
The integration writes to a single audience. If you need different forms going to different audiences, set up the integration separately per form. There's no conditional routing to different audiences based on a field within one integration.
I ran into them for five years on the Jotform product team. Book a free call and I'll tell you exactly how to handle your Mailchimp setup, or send me the details first.
Skip the native integration if you need conditional routing (different answers sending people to different audiences or complex tag logic): a webhook or Zapier gives you that branching. Skip it if your email platform isn't Mailchimp; map to the right connector instead. And if compliance matters, lean on double opt-in and a clear consent checkbox rather than fighting Mailchimp's re-subscribe protection, which exists for a reason.

Waitlist with referral tracking, drip emails, and launch-day handoff.

Recurring membership on Jotform: tier selection, Stripe billing, welcome drip, and dunning baked in

Donation pipeline: gift, receipt, record, tax letter.
In Jotform's Integrations tab, authorize Mailchimp, choose the target audience, then map the email field and any other fields to Mailchimp merge fields. Optionally add a tag for the signup source. Create any custom merge fields in Mailchimp first, or that data won't carry over.
The most common reason is double opt-in: new contacts sit as 'pending' until they click the confirmation email, so they don't appear as subscribed. Other causes: the contact previously unsubscribed (Mailchimp blocks re-adding them) or you're looking at the wrong audience. Check the audience's opt-in setting first.
Yes. You can attach a static tag (like the form name or campaign source) and map fields to Mailchimp groups. Tags are the cleanest way to segment Jotform signups later. The group structure in Mailchimp must match your form's options for group mapping to work.
Not with the native integration, which writes to a single chosen audience. For conditional routing, where different answers send people to different audiences or apply different tag logic, use a webhook or Zapier to add the branching.
Free 20-minute call. I'll tell you which workflow fits your Mailchimp setup and what it would take to build, or you can send me the details first.