Oct 8, 2026

Your Forms Shouldn’t Be Designed Around Mailchimp

Robin Adams
Chimpmaster General

“I want the Chicken Schnitzel… but i don’t need to know exactly how it’s made”

Here’s a slightly backwards way to design a form.

Open Mailchimp, look at all the fields and groups you’ve carefully created in your audience, and then build a form that asks people to fill them in for you.

It seems entirely sensible. After all, the information needs to end up in Mailchimp, so why wouldn’t you start there?

The problem is that your customers haven’t seen the lovingly organised inner workings of your Mailchimp account. Nor, we suspect, would most of them particularly like to.

They just want to understand what you’re asking them.

For simple signup forms, the distinction may not matter very much. If you need a name, an email address and perhaps a couple of communication preferences, a Mailchimp form may be perfectly adequate.

But once you want to understand a little more about somebody, designing the form around what you have in Mailchimp can lead you in a rather odd direction. You start asking questions based on how you want the answers stored, rather than how somebody would naturally give you that information.

And those aren’t necessarily the same thing.


What you need to know isn’t necessarily what you need to ask

We have a good example of this ourselves.

At Chimp Answers, we use Accelerate to describe organisations at a particular stage. It’s useful terminology for us because it helps us understand something about the organisation and the kind of support they’re likely to need.

We could therefore put this on a form:

Are you an Accelerate organisation?

This would be wonderfully convenient for our database and almost entirely useless to the person filling it in.

They don’t know what Accelerate means. We do, but that’s rather the point: it’s our classification, not theirs.

Instead, we can ask:

Do you have more than 2,500 subscribers in your audience?

That’s something they can answer without first consulting the Chimp Answers glossary.

We can then decide what their answer means to us and translate it into whatever information we need behind the scenes.

This is a small distinction, but it’s one we find ourselves returning to quite often when designing forms: what you need to know isn’t necessarily what you need to ask.

If you need to identify a particular type of customer, you don’t necessarily need to ask somebody which type of customer they are. If you need to populate a Mailchimp group, you don’t need to show them the group structure and hope they’re as excited about it as you are.

You ask a question that makes sense to them, then take responsibility for turning the answer into something useful to you.

This is where Mailchimp form reach their limit

Mailchimp forms are useful. We use them. For straightforward requirements, we’d much rather use the simple thing that already exists than introduce another platform, another integration and another password for somebody to forget.

But Mailchimp is primarily an email marketing platform, not a specialist form builder.

That becomes noticeable when you want the form to do something more sophisticated than collect information directly into an audience.

Perhaps the answer to one question should determine which question somebody sees next. Perhaps you want to explain certain choices properly, rather than squeezing them into whatever space the form gives you. Or perhaps what somebody tells you needs to be translated into something different before it reaches Mailchimp.

At that point, there’s a danger that you start redesigning the experience around what the form can do.

We’ve seen variations of this plenty of times. A perfectly sensible idea gradually gets chipped away until somebody says, “Well, Mailchimp won’t let us do that,” and everyone accepts this as though Mailchimp has recently been appointed Head of Customer Experience.

It hasn’t.

This is where something like Jotform becomes useful (other flexible form tools are available!).


Let the form do the heavy work and Mailchimp process it

Using a tool like Jotform means we can treat the customer-facing form and the Mailchimp database as two connected parts of the same process rather than insisting that one system does everything.

We can design the form around the person completing it: ask questions in language they understand, use conditional logic where it helps, explain choices properly and generally make the experience behave the way we think it should.

Then we can work out what their answers need to become in Mailchimp.

The Accelerate example is a simple version of this. Somebody tells us how many subscribers they have because that’s a question they understand. Behind the scenes, we can use that answer to help classify the organisation in a way that’s useful to us.

The person doesn’t need to know that any of this is happening. In fact, if we’ve designed it well, there’s very little reason they should.

This separation between collecting information and storing and using information gives us considerably more freedom. The form can be good at being a form, while Mailchimp can get on with being Mailchimp.


The City of Charles Sturt had the same problem on a larger scale

We used this approach in our work with the City of Charles Sturt, based in Adelaide, Australia.

The council wanted residents to be able to manage the communications they received, including Green Living, City Pulse, Around Our City and Pets of Charles Sturt.

Behind the scenes, the communications team needed those choices recorded properly in Mailchimp. That’s important because preference data is only useful if you can trust it when you come to send something.

But residents don’t wake up in the morning hoping for an opportunity to update some Mailchimp groups.

They simply want to say what they’d like to hear about.

That meant the resident-facing experience and the Mailchimp data structure had different jobs to do.

A dedicated form could present the choices in a way that made sense to residents and allow them to manage their preferences. Behind it, those choices could be translated into the structure Mailchimp needed.

The resident didn’t need to know how the plumbing worked, and the communications team didn’t need to compromise the way its data was organised just to make the form easier to build.

That’s the useful bit about separating the two. We’re not doing it because using two systems is inherently cleverer than using one. Quite the opposite: we’re doing it because sometimes asking one system to do two different jobs is what makes things complicated.


Your data can be beautifully organised and still be wrong

There’s another reason we care about this.

When somebody asks us about improving their Mailchimp data, it’s very tempting to go straight into Mailchimp and start looking at fields, groups, tags and segments.

We enjoy that sort of thing, so we’re hardly innocent here.

But before deciding how information should be organised, it’s worth asking where it came from in the first place.

If somebody misunderstood the question on your form, Mailchimp will faithfully store their misunderstanding. If your terminology meant something different to them than it did to you, Mailchimp isn’t going to spot the problem. It will simply keep the answer very neatly.

That’s why good data often starts outside Mailchimp.

Before worrying about where an answer should live, we need to understand why we’re collecting it. What are we hoping to learn about this person? What might we do differently because we know it? And what’s the clearest way for them to tell us?

Only then does it make sense to decide whether the answer should become a field, a group, a tag or something else.

Otherwise, we risk becoming extremely organised about information that wasn’t particularly useful in the first place.


This isn’t an argument for rebuilding every form in Jotform (or any other form tool)

We should probably say this before somebody spends their afternoon migrating twelve perfectly good Mailchimp forms.

If the form you’ve got does what you need, leave it alone.

A simple Mailchimp form is often exactly the right answer. We generally favour the least complicated solution that does the job properly, and adding another platform without a good reason doesn’t make a solution more sophisticated. It mostly gives you another platform.

The time to consider something like Jotform is when the limitations of the form start determining the experience.

If you’re changing sensible questions because Mailchimp can’t accommodate them, exposing internal terminology because that’s how your audience is structured, or abandoning useful logic because the form can’t handle it, then it’s worth separating the two jobs.

Design the form around the conversation you need to have with the person.

Then design the data around what you need to understand as a result.


Your database is your problem

Perhaps that’s the simplest way to think about it.

The person filling in your form shouldn’t have to understand your database. They shouldn’t need to know what your groups are called, which tags you use or how you’ve decided to classify them.

That’s our side of the bargain.

Their side is to tell us something about themselves, provided we’ve asked a sensible enough question.

Our job is to make sure that answer becomes useful information and, ultimately, helps us communicate with them more appropriately.

Sometimes Mailchimp can handle the whole journey perfectly well. Sometimes something like Jotform gives us the freedom to create a better experience before passing the information into Mailchimp.

Either way, the starting point shouldn’t be the empty fields in your database.

It should be the person you’re asking to fill them.

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *