Statistics
Automation statistics answer two questions: is the journey delivering, and where are contacts falling out of it?
Getting there
Either click Stats against an automation on the Automations list page, or open Automations Stats in the main menu for all of them.
Tree view and List view
The Automation Stats page offers two ways to read the same data.
Tree view
Draws the workflow as it appears in the builder, with the numbers overlaid on each node. This is the view for spotting where contacts stop — you can see a healthy count at the welcome email and a much smaller one three steps later, and know exactly which step to look at.
It's also the quickest way to see how a condition split its traffic: the Yes and No branches carry their own counts.
List view
A searchable, paginated table with one row per action.
| Column | Shows |
|---|---|
| Actions | The action's label. |
| Interval | Its timing — the delay or scheduled time. |
| Sent | Emails sent by this action. |
| Opened | Opens recorded. |
| Clicked | Clicks recorded. |
| Unsubscribe | Unsubscribes attributed to it. |
| Details | Drill into the contacts behind the numbers. |
Use List view when you want to compare actions side by side, or when the workflow is too large to read comfortably as a tree.
Action details
Details (or View Stats) opens the contacts behind a number — the actual list of who was sent to, who opened, and who clicked.
The detail view identifies which action you're looking at and which automation it belongs to, and includes:
- Contact identity — email address and the list they came from.
- Delivery information — sending node and message identifier.
- Open detail — when it was opened, the IP, and geographic detail such as city.
- Click detail — which link, and when.
- Bounce detail — bounce type, code, and reason where applicable.
Exclude bots
The detail view has an Exclude bots option, and it's worth using.
Security scanners and mailbox pre-fetchers open messages automatically, which inflates open counts. Excluding bots gives a truer picture of human engagement. There's also a Display Emails toggle for showing or hiding addresses.
A condition that branches on opens is evaluated against tracking data. If your raw open numbers look high but the Yes branch is thin, bot opens are likely flattering your headline figure — compare with Exclude bots on.
Reading condition nodes
A condition doesn't send anything, so it has no Sent, Opened, or Clicked figures. It reports an evaluation instead: how many contacts met the condition and took the Yes branch, and how many didn't and took the No branch.
That ratio is the most useful number in a branching automation. A very low Yes rate points at the upstream email — its subject line, its timing, or its deliverability — rather than at the condition itself.
Exports
Export Options downloads the underlying data for an action, for analysis outside Mumara or to feed another system.
How statistics accumulate
Statistics are recorded per action, and they accumulate for the life of that action.
- Renaming an action keeps its history — the label changes, the numbers don't reset.
- Deleting and rebuilding an action starts a fresh record. The old numbers don't carry across.
- Pausing an automation stops new data; existing data is kept.
Because a new action can only be added at the end of a branch, changing the middle of a workflow means rebuilding its tail — and those rebuilt actions start their statistics over. If you need the history, export before restructuring.
What to look at first
- Sent on the first action — if this is zero, the problem is enrolment, not sending. Check the trigger and the automation's status.
- Sent at each subsequent step — a sharp drop points to a Wait or condition that isn't releasing contacts, usually the scheduler.
- The condition's split — a very low Yes rate is a signal about the email before it.
- Unsubscribes per action — one action well above the others is worth a look at its content or its frequency.
Next steps
- Troubleshooting — when the numbers say nothing is happening.
- Worked Examples — journeys worth measuring.