Does Mailchimp Remember Between Runs?
Does Mailchimp Remember Between Runs? No. A Mailchimp automation flow holds no memory of its own between runs. Each contact who enters a flow moves through the triggers, rules, and actions in that flow's definition, reading the contact record as it stands at that moment. Anything a previous run noticed, wrote, or decided survives only if that run wrote it onto a contact first: a tag, an audience field, a note, or a segment condition that now matches. That distinction is easy to miss because Ma
Does Mailchimp Remember Between Runs?
No. A Mailchimp automation flow holds no memory of its own between runs. Each contact who enters a flow moves through the triggers, rules, and actions in that flow's definition, reading the contact record as it stands at that moment. Anything a previous run noticed, wrote, or decided survives only if that run wrote it onto a contact first: a tag, an audience field, a note, or a segment condition that now matches.
That distinction is easy to miss because Mailchimp feels continuous. The same audience, campaigns, and flows are still there tomorrow. The continuity lives in stored contacts and flow definitions, not in a memory one run hands to the next.
What does a contact actually hold?
A contact holds the audience record. It keeps an email address, a status, audience field values such as a name, a plan, or a date, tags applied manually or by an automation, and engagement history such as opens, clicks, and purchases from a connected store. Those values persist, and every later flow can read them.
A flow can check a tag before branching, read an audience field to personalize an email, or use a segment to target contacts who opened a previous campaign. A conditional split can send contacts who clicked one way and contacts who did not another way. All of that works from current stored state, and it works reliably.
The scope is the audience. What persists is what was saved as a value, a tag, or activity on that contact. The reasoning behind a campaign, the rejected draft, and the discussion in another tool about why a segment got an exception are not on the contact unless someone typed them there. A new run reads values. It does not recover the conversation that produced them.
Audiences also stay separate. The same person in another audience is a different record, with its own fields, tags, and history.
How do Mailchimp automation flows actually run?
An automation flow, built in the Customer Journey Builder, connects a starting point to journey points: triggers, actions, and rules. The starting point is the event that puts a contact into the flow: a signup, a tag added, a form submitted, a purchase, a date reached. Rules add time delays and if/else splits. Actions send an email or SMS, add or remove a tag, update a contact field, archive a contact, or fire a webhook to a third party app.
Flows only apply to actions or events that happen after the flow is activated. Plan limits shape how large a flow can be: an Essentials plan or higher allows up to 4 steps in a flow, while a Standard plan or higher allows up to 200 steps. Editing a live flow means pausing it first, and contacts already inside do not move forward while it stays paused.
Every entry is a fresh pass through that definition for one contact. A welcome flow reads the new contact in front of it, sends the first email, waits, checks a condition, and ends or branches. The next signup starts the same way, from its own contact record. The flow does not retain the last contact's summary, a note about which subject line already underperformed for this segment, or what was promised to the same person in a support chat last month, unless a field or tag stores that state explicitly and the flow is built to read it back.
A contact's position inside a single journey does persist: Mailchimp tracks where that contact is in the flow, so a delay or a split resumes for that contact instead of restarting. That is progress inside one journey for one contact. It is not memory shared across flows, across campaigns, or across the AI tools wrapped around the account.
What about reports and campaign history?
Reports are the other place a run leaves a trace. Each campaign and flow keeps its own results: sends, opens, clicks, bounces, unsubscribes, and revenue where a store is connected. For a person reviewing performance, that record answers what happened, send by send.
That history is an audit and analytics record. It is not working memory the next flow reads before acting. A flow does not open last month's report to learn why open rates fell, and it does not recover an earlier AI-generated draft from the results before writing the next one. If an operator adds an AI step through Mailchimp's Intuit Assist, a connected app, or an outside agent in n8n, Make, or Zapier, that step generates new text each time from the contact data and instructions in front of it, not from a shared memory of prior runs.
The gap shows up in ordinary work. A scheduled agent that drafts the weekly newsletter, checks last week's performance, and proposes the next angle has to be handed the numbers, the angle already used, and the promise already made, every single week. The flow fires reliably. The context arrives manually, or not at all.
Where this leaves agents working from Mailchimp
Mailchimp is often the sending engine behind a wider setup: an n8n, Make, or Zapier scenario updates contacts, an AI agent drafts copy from campaign results, and a chat tool is where the plan gets decided. Each tool sees the same current tags and fields. None inherits the thread behind them: why a segment was split that way, what was agreed with a partner, or which explanation already failed.
So the daily work becomes re-briefing. Someone pastes background into a prompt, re-asks a question answered in another tool, or writes longer flow instructions so the next run can act without the missing context.
One memory that every run can read
The fix is a memory layer that lives outside any single audience or flow, so every run and every tool works from the same past. Vilix AI is built for exactly that job, for scheduled agents and automations that start blank.
Vilix AI is cloud-hosted, with zero infrastructure to run or maintain. Connect it once over MCP and the same memory is available everywhere the work happens: alongside Mailchimp flows, in n8n, Make, and Zapier scenarios, and in the AI chat tools used to plan and review the work. What gets stored is full conversation history, not just facts extracted from it, so a later run can recover the exact agreement, the reason a decision was made, and the wording that was already used, not only a tag value on a contact.
The loop is simple. Before acting, a run retrieves the relevant history for the work it will touch. It acts with that history in hand. Then it saves what it did and what it learned back to the same memory. Mailchimp stays the system of record for contacts and sends. Vilix AI becomes the system of record for the thread behind them, and the re-briefing cycle ends.
Free forever, no credit card. The free plan is free forever, the 7-day Pro trial needs no credit card, and your memory stays under your control: export everything or delete it anytime.