Skip to main content
Metrics type: Key Metrics • Category: Email Marketing
Percent of members who started a multi-step automation and reached the final email. Sharp drops = broken trigger or template-render error.

​
At a glance

The share of members who entered a multi-step automation (Customer Journey or Classic Automation) and reached its final email. Computed across active multi-step automations as completers divided by entrants. A multi-step journey only earns its full revenue if members move through all of its steps, so a falling completion rate means the back half of every journey, often the highest-converting offers, is being seen by fewer and fewer people. A gentle decline is usually natural attrition (people unsubscribe, lose interest, or convert and exit early). A sharp drop is almost always mechanical: a broken step trigger, a template-render error mid-journey, a wait-step misconfiguration, or a segment-exit rule that is ejecting members too aggressively. The card is read as a structural-health gauge for the automation programme, not a campaign performance metric.

​
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 skincare brand on Shopify running Mailchimp Standard with three multi-step Customer Journeys. Snapshot for the 30-day window ending Thursday 11 Jun 26, with the prior 30-day period for comparison. What this snapshot is telling us:
  1. The blended rate of 74.6 percent is below the 80 percent threshold and down 4.3 points vs prior. The headline says “investigate”, but the blended figure hides where the problem actually is. Decomposing by journey is the first move.
  2. Win-Back is the entire story. It collapsed from 71.0 percent to 42.9 percent, a 28-point drop. That is not natural attrition, attrition moves a point or two, not nearly thirty. This is a mechanical failure. Investigate: open the Win-Back journey and check (a) whether a step trigger disconnected after a UI migration, (b) whether step three or four throws a template-render error (send a test through each step), and (c) whether a wait step was lengthened, leaving members stuck mid-queue and counting as incomplete.
  3. Welcome and Post-Purchase are healthy. Welcome at 78 percent is slightly under the generic threshold but stable vs prior and entirely normal for a four-step welcome series, some new subscribers convert early and exit, which is the desired outcome. Post-Purchase actually improved. Neither needs action.
  4. The blended figure was misleading on its own. Two healthy journeys plus one broken journey averaged to a “soft amber” 74.6 percent, which understates how broken Win-Back is and overstates any problem with the rest. Always decompose before acting.
  5. The revenue at risk is in the tail. If Win-Back’s final two steps carry its strongest re-activation offer, fewer than half of entrants are now seeing it. Cross-reference top-automations-by-revenue, Win-Back’s contribution will have fallen over the same window.
The diagnostic flow when this card flags amber:
  1. Decompose the blended rate by journey. The composite always hides a load-bearing weak point; find the journey dragging it.
  2. For the dragging journey, identify the step where members stall. A completion cliff between two specific steps points straight at the broken or mis-rendered step.
  3. Send a test through each step. A template-render error surfaces immediately in a test send.
  4. Check wait-step durations. A lengthened wait makes members look incomplete when they are simply still queued; this is a false alarm, not a break.
  5. Check exit and goal rules. An over-aggressive exit condition ejects members who should continue; a goal rule firing early is desirable (they converted) and not a problem.
The rapid-response playbook for marketing leadership:

​
Sibling cards merchants should reference together

​
Reconciling against Mailchimp

Where to look in Mailchimp’s own dashboard:
  • Mailchimp → Automations → Customer Journeys, open a journey, and use the journey map view to see how many members are at each step. The drop-off between steps is the visual equivalent of the completion-rate decomposition.
  • Mailchimp → Reports → Automations for per-automation and per-step send and engagement counts.
  • The journey map’s per-step member counts are the raw material: entrants at step one versus members reaching the final step.
Why the Vortex IQ completion rate may legitimately differ from a glance at the Mailchimp journey map: Mailchimp shows per-step member counts; it does not surface a single blended programme completion percentage. Reconciliation means confirming the per-journey entrant and completer counts, not disputing a single Mailchimp number: Quick rule for support tickets: when a merchant says “Mailchimp shows most people reaching the end, why is your rate low?”, the usual answer is either in-flight members in a wait step (not yet complete, not dropped) or goal-rule early exits (converted and left, a good outcome). Both depress the raw completion percentage without indicating a broken journey. A sharp drop versus prior period, by contrast, is the mechanical-failure signal to chase.

​
Known limitations / merchant FAQs

My completion rate is 78 percent. Is that bad? Not on its own. For a welcome series, 78 percent is entirely normal, some new subscribers convert after the first email and exit via a goal rule, which is the desired behaviour. The 80 percent threshold is a generic guide; what matters far more is the trend. A stable 78 percent is fine; a journey that fell from 78 to 50 percent in a month is broken. Always read this card vs prior period, not against a fixed number. A long wait step makes my completion rate look terrible. Is that real? No, that is an artefact. Members sitting inside a multi-day wait step have entered but not yet completed, so they count against completion until they clear the wait. A journey with a seven-day wait will always show depressed completion for the most recent cohort simply because they are still queued. Judge such journeys on their settled cohorts, not the in-flight ones, and do not treat a long-wait journey’s lower rate as a fault. Why does early conversion count against completion? Because completion measures reaching the final email, and a member who buys after email two and exits via a goal rule never receives the later emails. That is an excellent outcome (they converted) but it lowers the completion percentage. A journey with a strong early-conversion goal will structurally show lower completion. This is why completion should be read alongside the journey’s revenue, not in isolation, a “low” completion rate driven by early conversion is a success, not a failure. The blended rate moved but each individual journey looks fine. How? The blend is volume-weighted. If a high-entrant, lower-completion journey grew its share of total entrants this period (say a big welcome intake), the blended rate falls even though no single journey changed. Always decompose by journey before concluding something broke; a mix shift is not a malfunction. Can Vortex IQ fix the broken step for me? No. Vortex IQ is read-only. It surfaces the completion drop, helps you locate the stalling step, and points at the likely cause; the republish happens in Mailchimp by the merchant’s team. The Vortex Mind Customer Recovery Opportunity report can raise a merchant-side Action describing the suspected break, but the configuration change stays with the merchant. Does this include single-email automations? No. A single-email automation has no series to complete, so it is excluded from this metric. Single-email automation health is judged by its send and engagement figures, not by a completion rate. This card is strictly about multi-step journeys.

​
Tracked live in Vortex IQ Nerve Centre

Automation Series Completion Rate is one of hundreds of KPI pulses Vortex IQ tracks across Mailchimp and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.