Mailchimp Campaign Manager: The Touchpoint Rules Behind the Confusion

Threads about Mailchimp’s campaign manager surface often in QuickBooks communities. One recent question, posted in French on an Intuit community page, asked simply what the feature covers. The accepted answer came from the vendor’s own help material. It reads more like a map than a fix, and that map settles most of the confusion on its own.

Mailchimp is the marketing arm of the Intuit ecosystem, and many QuickBooks users meet it through that door. The campaign manager is its planning hub. Knowing what it will and will not do saves a round of trial and error.

The campaign manager in brief

The tool exists to plan, run, and measure one marketing campaign from end to end. You set a single goal, then connect multiple marketing touchpoints to it on a shared calendar. When the campaign finishes, its report shows what worked. Those analytics are meant to guide your next steps.

None of this is complicated in isolation. The friction comes from the touchpoint rules, and those rules are not uniform.

Which touchpoints attach to a campaign?

This is where users stumble, because the answer draws a hard line between two groups. Many people expect everything on the calendar to roll up into campaign reporting. It does not, and that surprise is what sends them searching.

Emails and web touchpoints must be attached to a campaign. An email here is a message built for one specific campaign, sent to your whole audience or targeted by contact email address or tag. Multivariate tests belong to this group as well, since they are variants of a campaign email.

Text messages and social posts sit on the other side of the line. They cannot be attached to a campaign at all. You can schedule them inside the campaign manager’s calendar, but that is the extent of it. No setting changes this; the restriction is by design.

Tasks and events round out the calendar. A task is anything the campaign needs done, with a name, a start date, an end date, and a status you update as work progresses. An event covers marketing moments such as a webinar, a sale, or a product launch.

A connector to outside apps

The web touchpoint gets its own definition, and it is the least intuitive of the set. It works as a connector. When your Mailchimp activity fires, it hands a specific action to an outside application. An outside app could, for instance, be told to act whenever a campaign email goes out. Like emails, every web touchpoint must be tied to a campaign.

Not every plan includes the campaign manager

The feature ships with the Standard subscription or higher, so that is the first thing to check when the calendar seems absent. SMS touchpoints carry a second gate. You must set up an SMS marketing program before you can add any text touchpoint at all.

Finding emails and texts later

Items built in the campaign manager do not stay visible on that calendar alone. Emails and SMS touchpoints also appear in the List View tab of the All Campaigns page, and on the Reports page. If something you built seems to have vanished, those two locations are where it resurfaces.

Testing variants of one email

Multivariate testing earns its own paragraph in the answer. You send different versions of one email to subscribed contacts, then compare results to judge engagement. Up to eight combinations are allowed, built from four testable variables: subject line, sender name, content, and send time. Each version that differs on one variable counts as a single combination.

The takeaway

We read this thread as a planning problem, not a bug. The campaign manager rewards users who learn the rules first and punishes assumptions. Texts and social posts will schedule, but they will never report into a campaign, so treat them as standalone activity from the start. Emails, their test variants, and web connectors are the opposite: they belong to a campaign, or they do not run.

The answer offers no reason for the split. It simply states the rule, and knowing the rule is what closes the thread.