Does Campaign Monitor Remember Between Runs?
Does Campaign Monitor Remember Between Runs? No. A Campaign Monitor journey holds no memory of its own between runs. When a journey acts on a subscriber, it reads that subscriber exactly as the record stands at that moment: the custom field values currently stored, the list the subscriber currently belongs to, the segments the subscriber currently matches, and the activity currently on file. Anything an earlier run worked out survives only if that run wrote it back first, as a field update or a
Does Campaign Monitor Remember Between Runs?
No. A Campaign Monitor journey holds no memory of its own between runs. When a journey acts on a subscriber, it reads that subscriber exactly as the record stands at that moment: the custom field values currently stored, the list the subscriber currently belongs to, the segments the subscriber currently matches, and the activity currently on file. Anything an earlier run worked out survives only if that run wrote it back first, as a field update or a segment change that a later step can check.
That distinction is easy to miss because the account feels continuous. Lists, segments, and journeys are all still there tomorrow, and a subscriber partway through a journey keeps receiving the next steps at the set delays. The continuity lives in records and journey definitions, not in a memory one run hands to the next.
What does a Campaign Monitor subscriber actually hold?
A subscriber record holds custom fields, list membership, and activity. A custom field stores one named value on the record, such as a date, a plan, a city, or a preference the subscriber selected. A list is the grouping the subscriber belongs to, and joining a list is one of the standard ways a journey starts. A segment is a live rule over those fields and activity: subscribers move in and out of a segment as their stored values change.
Those stored values do real work. Journey triggers include a subscriber joining a list, a subscriber entering a segment, a subscriber exiting a segment, and a date held in a custom field. When a journey runs, its steps can send an email, wait for a set delay, check a condition, and update a custom field. Each field update writes current state back onto the record, and that written state is all a later run can see.
Two details shape what memory means here. First, the record shows the present, not the reasoning. A field updated today describes what is believed now. It does not explain what was checked before the change, which option was set aside, or why the last run chose one message over another. Second, the checks run on their own clocks. Segment membership changes are checked every 10 minutes, so a trigger can wait before it fires. Date-based journey emails are sent at midnight in the account time zone, and a date entered after that point waits for the next day. The system is precise about current values and timing, and silent about everything a run figured out along the way.
What does the journey itself keep?
A journey keeps its definition. It keeps its trigger, its steps, its delays, its conditions, and its re-entry setting that decides whether a subscriber can go through the same journey again. Once a subscriber is inside a journey, the steps continue at their intervals until the journey ends. That reliability is real, and it is also the whole of what the journey remembers: the rule, applied again, on schedule.
What a journey does not keep is a run journal. A condition reads current fields and segment membership and sends a subscriber down one branch or the other. That decision is not stored as an explanation. When the steps finish, the lasting record is whatever now sits on the subscriber: the field values present, the lists present, the segments matched, and the position in the journey. The platform stores definitions and subscriber state, not a history of what each run learned.
Where scheduled AI agents hit the same wall
Add a scheduled AI agent beside a Campaign Monitor account and the gap widens. The agent runs on a schedule, reviews subscribers who went quiet, checks who clicked but did not buy, drafts a follow-up, or decides which segment needs attention next. Inside Campaign Monitor, its work survives only where it updated a custom field or moved a subscriber into a new segment. Outside Campaign Monitor, in the chat or tool where the agent actually reasoned, the full context of that run, what it checked, what it ruled out, and why it chose one action over another, has no home on the subscriber record at all.
The next run, whether it is the same agent tomorrow or a different tool next week, meets current fields and current values. It does not meet the reasoning. It re-reads the same subscribers, re-checks the same activity, and re-derives the same conclusions, because the one place that held the full story was the previous run itself, and that run ended.
Give the runs one shared memory
Vilix AI is built for exactly that missing layer. It is cloud-hosted with zero infrastructure to run, so there is no database to provision and no server to maintain before an agent can remember. Every connected tool reads and writes the same memory over MCP, so an agent working beside Campaign Monitor, a coding assistant, and a chat tool all share one state instead of separate run histories.
That memory holds full conversation history, not just facts. A later run can reopen what an earlier run actually said, checked, and decided, in order, rather than guessing from a field value that something happened. When a nightly agent finishes a review of quiet subscribers, it saves what it found, what it skipped, and what it planned to do next. The morning run starts from that record, not from a blank slate.
Getting started is simple. Vilix AI has a free plan forever, and a 7-day Pro trial with no credit card. Data stays portable the whole time: export everything or delete it anytime.
Campaign Monitor remembers subscribers well. Fields, lists, segments, and journey definitions are exactly the right tools for sending the right message at the right time. What no single run leaves behind is its own reasoning. Give scheduled agents one shared memory outside the subscriber record, and each run stops starting over and starts building on the last one.
Get Started for Free Free forever, no credit card.