At a glance
The operational inventory of every Mailchimp Customer Journey, Classic Automation, and Transactional flow currently configured in the account, with status (Active / Paused / Draft / Stopped), trigger type, and revenue attribution. The single most under-used card in the Mailchimp catalogue: brands routinely discover that 30-50 percent of their configured flows are silently inactive (paused during a past migration, stopped during a UI restructure, drafted but never published) while still being assumed to be running. The card surfaces silent revenue loss that no other view captures.
Calculation
Calculated automatically from your Mailchimp data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US-based gift-and-stationery brand on Shopify running Mailchimp Standard, audit performed Wednesday 15 May 26.
What the flow audit is telling us:
- Three flows are silently inactive and represent recoverable revenue. Win-back, Replenishment, and Review-request were all Active in the past, are now inactive, and have no documented reason for being inactive. Industry baselines for these flow types: win-back recovers 1-3 percent of inactive customers (worth 8-15 per recipient); review-request generates social proof that lifts product-page conversion 3-8 percent (revenue impact indirect but meaningful). Reactivating all three is a 30-minute task that recovers an estimated $8,000-15,000/month for this brand at current audience size.
- The Win-back flow paused 14 months ago is the highest-priority recovery. Win-back targets customers who haven’t purchased in 60+ days; with the flow inactive, every customer who entered that 60-day-inactive state in the last 14 months never got a re-engagement email. At the brand’s customer base size, that is roughly 4,000-6,000 customers who should have received win-back messaging but didn’t. Reactivating the flow today captures the next cohort but does not recover the lost cohort; the lost cohort has continued drifting toward permanent churn.
- The Replenishment flow paused 9 months ago is the second priority. Replenishment is highly category-dependent; for gift-and-stationery brands the cycle is roughly 90-180 days, so 9 months of inactive replenishment messaging means 1-2 missed cycles per customer. The lost revenue compounds because each missed cycle reduces total customer LTV.
- The Review-request flow stopped 16 months ago is the lowest priority of the three but still meaningful. Reviews drive product-page conversion lift across all channels (email, paid social, organic search), so the indirect revenue impact is significant even though the direct email revenue contribution is small.
- The VIP-tier exclusive launch flow stuck in Draft for 8 months is a different problem. This is “abandoned setup” rather than “silently paused”; someone started building the flow, got blocked, and never finished. The decision required is: is this still on the roadmap? If yes, complete it; if no, delete it to clean up the working space. Stuck-Draft flows accumulate over time and create UI clutter that obscures the active flows.
- The 5 currently-active flows are doing strong work. Abandoned cart at 24,200 is the lifecycle entry-point; post-purchase, birthday, and (when active) replenishment serve different lifecycle moments. The active programme is well-architected; the problem is silent inactivity, not bad active flow design.
- Audit each flagged flow’s pause/stop reason. Mailchimp’s flow-edit history surfaces who paused and when. If there is no documented reason and no successor flow, the pause is likely accidental.
- For each silently-inactive flow, decide: reactivate as-is, reactivate with refresh, or formally retire. Document the decision in the flow’s internal name (e.g. “Win-back, intentionally retired 2026-Q1, replaced by RFM segmentation”).
- Cross-reference with
mc_top_automation_revenuefor the “what the active flows are doing” view. Reactivating an inactive flow should be measured against the per-recipient revenue of comparable active flows. - Pair with
mc_audience_growth_ratefor the audience-supply view. A reactivated flow needs eligible recipients to drive revenue; if audience growth is stagnant, reactivation alone won’t materially scale revenue. - Schedule recurring audits. Brands that audit this card quarterly catch silent-pause patterns within 90 days; those with annual audits accumulate 6-12 months of silent revenue loss between audits.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Mailchimp’s own dashboard:- Mailchimp → Automations → Customer Journeys for the Customer Journeys list with status indicators.
- Mailchimp → Automations → Classic Automations for the legacy Classic Automations list.
- Mailchimp → Automations → Transactional for transactional flows (typically Mandrill-powered).
Cross-connector reconciliation:
Quick rule for support tickets: if a merchant says “My welcome flow is active in Mailchimp but your card shows it as paused”, the most common cause is the 6-hour refresh lag (a recent reactivation may not have propagated). The next-most-common is that there are multiple welcome flows in the account (one active, one paused, both named “welcome series” with slight variations) and the merchant is looking at the active one in the UI but the inactive one happens to also surface in the audit. Cross-reference by flow ID rather than name to disambiguate.