Automation in Campaign Monitor: Journeys, triggers, and the transactional/marketing split
Campaign Monitor's native automation surface is Customer Journeys -- a visual builder where you chain triggers (subscribed to a list, joined a Segment, a specific date like a signup anniversary) to steps (send an email, wait, branch on a condition, add to a list, update a custom field). There's no general-purpose "if this then that" rule engine outside Journeys; anything triggered by an external event (a purchase, a support ticket closing) has to reach Campaign Monitor via its API or a connector like Zapier before a Journey can act on it.
Key components and how Campaign Monitor shapes delivery
- Data readiness and mapping: signup, purchase, and engagement signals get mapped to Campaign Monitor custom fields and list/Segment membership, since Journey triggers can only fire off data that's actually stored on the subscriber record.
- Trigger design: lifecycle moments (welcome, win-back) and event-based triggers (added to a Segment via an API call from your e-commerce or CRM system) are configured as Journey entry points.
- The transactional/marketing split: order confirmations and password resets go through Campaign Monitor's separate Transactional email API (billed per-send, not subject to list-unsubscribe rules), while nurture and promotional sends stay in Journeys against your compliant marketing lists -- conflating the two risks deliverability and compliance problems.
- RSS-triggered sends: for content-driven programs, Campaign Monitor's RSS campaign feature auto-sends when a connected feed publishes new content, removing the need for a manually scheduled Journey step.
- Quality and governance: Segment logic and Journey branch conditions are reviewed against Campaign Monitor's own list-hygiene and compliance requirements before go-live.
Adaptability and maturity: engagements scale from a single welcome Journey with two or three steps to programs with a dozen interlocking Journeys plus a separately configured Transactional API integration for order-driven emails. Lean teams start with one lifecycle Journey; mature programs need explicit governance over how Journeys interact so a subscriber doesn't land in two conflicting automations at once.
What Campaign Monitor delivers in practice
- A documented Journey map (triggers, steps, branch conditions) built in Campaign Monitor's own visual builder, not an external diagram that drifts from what's actually configured.
- Custom-field and Segment mapping so external event data (from your e-commerce platform or CRM) can actually trigger the Journeys it's meant to.
- A configured Transactional API integration kept separate from marketing-list sends, with delivery and compliance boundaries documented.
- RSS campaign setup for any content-driven, feed-triggered sending, removing manual scheduling for that program.
- A Journey-conflict review so subscribers aren't double-enrolled across automations with contradictory messaging.
With Campaign Monitor's Journeys builder and Transactional API as the two real execution surfaces, our work is making sure event data actually reaches them correctly and that Journeys don't collide -- not building automation logic Campaign Monitor doesn't natively support.
Use cases (highlights)
- Welcome and onboarding journeys delivered through Campaign Monitor triggered by signups and demographic signals.
- Abandoned cart recovery sequences optimized for time-to-respond and merchandising relevance while Campaign Monitor ensures compliant timing.
- Post-purchase postscript emails that drive repeat purchases, using Campaign Monitor to segment loyal customers from at-risk segments.
- Re-engagement campaigns that reactivate dormant segments using behavior signals tracked in Campaign Monitor.
- Milestone-based campaigns (birthdays, anniversaries) orchestrated via Campaign Monitor workflows with personalized messaging.
- Lifecycle nurturing for high-value segments, with ongoing optimization guided by Campaign Monitor analytics.
- Seasonal and event-driven programs that scale automatically as contact volumes shift within Campaign Monitor.
- Transactional-signal triggered messages (order updates, status changes) buffered by Campaign Monitor rules to ensure delivery integrity.
- Cross-channel coordination where Campaign Monitor aligns email with in-app or SMS touchpoints for a cohesive experience.
- Data hygiene automation to maintain clean audiences within Campaign Monitor across large lists.
These use cases illustrate how Campaign Monitor powers practical, measurable automation outcomes while teams maintain control and governance.

