Mailchimp for a listyou can still explain.

Choose Mailchimp when someone on the team will write to people who asked to hear from you: a restaurant's regulars, a studio's members, a local professional's newsletter, an education list. Signup happens on a form you control. Tags cover a location, a class, or a customer versus a prospect. That is enough structure for this tool to do honest work.

Move toward a commerce platform when the business is an online catalog and the money is in browse, cart, and post-purchase automation. Forcing that model into a lightweight audience is how journeys get brittle. Stay here when the truth is a letter plus one or two automatic notes. Do not import a list you bought because the contact limit looked roomy.

We keep a single audience unless there is a legal or brand reason to split. Tags and groups record state. Journeys cover the useful automations: a welcome, a reminder after a booking, a note when a class is coming. Each journey has an end. Classic automations left over from an old editor get audited so they do not fire beside the new journey.

Campaigns are written for an opening, a menu change, a class, or a real announcement. They exclude people the journey just wrote. The template is simple enough that the next coordinator can duplicate it without breaking the footer or the unsubscribe. Authentication and the physical address stay correct. A pretty template that hides the unsubscribe is not a template we ship.

The failure is a new audience for every event, plus a master audience, plus a spreadsheet import. The same person is in three places and receives three versions of the announcement. Unsubscribes apply to one audience and not the others. The list looks large. The complaints are real.

The second failure is turning on every journey template the product suggests. A store block points at products you do not sell. A welcome series offers a code the register will not honor. We delete suggested automations that do not match the business. Suggested is not the same as needed.

We read sends, unsubscribes, complaints, and the clicks that match the ask: a reservation, a class, a reply, a visit. Open rate tells us if placement broke. It is not the report the owner should manage the month by. A journey is judged on whether people completed the useful step, then stopped receiving it.

Revenue attribution inside a light commerce connection is treated cautiously. If you are not an online store, we do not invent email revenue to look like a catalog brand. The question is whether the list still wants the mail and whether the call to action happened. Sunset rules remove people who have not engaged in the window you set.

Restaurant group, four locations, Mailchimp. Each location had its own audience. A fifth audience held 'everyone,' imported from an old point-of-sale export that mixed receipts with people who had opted in. A welcome automation and a weekly special both fired. Regulars at two locations were getting both, plus the all-locations note.

We collapsed promotional mail into one audience with location tags, and we kept transactional receipts out of it. The welcome journey became one note that asked which location they actually visit. The weekly special went only to people tagged for locations that were running it. The old export was not re-imported. The coordinator could duplicate the next special without creating another audience. That was the job. It was not a commerce flow program.