Skip to main content

Automations Stats

Automation statistics answer two questions: is the journey delivering, and where do contacts fall out of it?

You build automations under Actions → Automations. Each automation starts from a trigger and moves contacts through waits, conditions and actions. Its statistics show how many contacts reached each step, and for every email it sends, the same detailed report you get for a broadcast.

Getting there​

There are two ways in:

  • Statistics → Automations Stats lists all your automations. Click the chart icon in an automation's Details column.
  • On the Automations list under Actions → Automations, click the chart icon in an automation's Stats column.

Both open the automation's Automation Stats page.

The Automations Stats list​

Statistics → Automations Stats shows your automations in a table headed Recent Automations:

ColumnWhat it shows
IDThe automation's number.
NameThe automation's name.
AudienceBased On List: every automation runs on a contact list.
Trigger ActionThe contact list the automation runs on.
Total ActionsHow many email actions in the automation have statistics.
Last ActivityWhen the automation was last updated.
DetailsClick the chart icon to open the automation's Automation Stats page.

Paused automations are listed too. Deleted automations aren't.

The Automation Stats page​

The page is titled Automation Stats and shows one automation, in either of two views. Switch between them with the two icons at the top right: the list icon (List View) and the tree icon (Folder View).

Tree view​

The tree view is shown first. It draws the automation as it appears in the builder, with its figures on each step. It's the view for spotting where contacts stop: a healthy count on the welcome email and a much smaller one three steps later tells you exactly which step to look at.

Use the + and − buttons on the left to zoom in and out of a large workflow.

Each kind of step shows different details:

StepWhat it shows
TriggerThe trigger's name, the automation's Name and the List Name. Click the list name to see all the automation's contact lists. Edit opens the automation in the builder, in a new tab.
WaitHow long contacts wait at this step.
ConditionWhat it checks, Open previous email? or Click on a link?, and for click conditions whether any link counts (Any Link) or only a chosen one (Custom). Evaluation shows how long the condition waits before deciding.
Action: Send an emailThe email's Title, Actions, which is how many contacts it has processed, and When it sends: Send Now or a time of day. Hover over the question mark next to a time to see what happens when that time has already passed that day. Click View Stats for the email's full report.
Action: Notify AdminThe notification's Title and Actions: how many notifications it has sent to the address you set in the action.
OperationThe copy or move operation, its Actions count and the list it copies or moves contacts To List.

List view​

The list view is a searchable table with one row per action. Use it to compare actions side by side, or when the workflow is too large to read comfortably as a tree.

ColumnWhat it shows
Automation NameThe action's name.
IntervalWhen the email sends: Instant, or a time of day.
SentEmails the action has sent.
OpenedUnique opens / total opens.
ClickedUnique clicks / total clicks.
UnsubscribedUnsubscribes attributed to the action.
DetailsClick the chart icon for the email's full report.

Notifications and copy or move operations are listed too, with the action type in brackets after the name and their count under Sent. They don't send to your contacts, so their other columns show ---.

An email action's report​

View Stats in the tree, or the chart icon in the list, opens the report for one email action. The page is titled with the automation's name and says which action you're looking at: "You're viewing statistics for the action … belongs to automation …".

The report has the same tabs as a broadcast's: Summary, Opened, Clicked, Unsubscribed, Bounced, Complaints, Logs and A/B. See Broadcast Stats for what each tab shows. The Summary table adds three rows at the top:

FieldWhat it shows
Action TitleThe email action's name.
Designed ByYour account's name and email address.
Sent ActionsHow many emails this action has sent.

The rest of the Summary shows the lists, the broadcast, the pools it sends through, the start time and status, the audience size, Sent, Skipped, Opened, Clicked, CTR, Bounced and Unsubscribed, and the tracking settings, with the Top Domains, Opened vs Unopened and Countries by Email Opened charts alongside.

Exclude bots​

The Opened, Clicked and Unsubscribed tabs have an Exclude bots switch, and it's worth using. Security scanners and mailbox pre-fetchers open messages automatically, which inflates open counts. Switching on Exclude bots gives a truer picture of human engagement. Display Emails shows or hides the contacts' addresses.

Judge conditions on human opens

A condition that branches on opens is decided by tracking data. If an email's open figure looks high but few contacts take the Yes branch after it, bot opens are probably flattering the headline figure. Compare with Exclude bots switched on.

Exports​

Export Options downloads the data behind the action: a PDF overview, a CSV file for each tab, or everything as one ZIP file. Use it for analysis outside Mumara ONE or to feed another system. Exports run in the background by default and appear under Tools → Exported Files. See Exporting statistics.

Reading condition steps​

A condition doesn't send anything, so it has no Sent, Opened or Clicked figures. To see how it split your contacts, compare the Actions count on the first action of its Yes branch with the one on its No branch.

That ratio is often the most useful number in a branching automation. A very low Yes rate points at the email before the condition, its subject line, its timing or its deliverability, rather than at the condition itself.

How statistics accumulate​

Statistics are recorded per action, and they build up for as long as that action exists.

  • Renaming an action keeps its history. The label changes; the numbers don't reset.
  • Deleting and rebuilding an action starts a new record. The old numbers don't carry over.
  • Pausing an automation stops new figures coming in. The figures it has already collected are kept.
Restructuring resets the affected steps

New actions can only be added at the end of a branch, so changing the middle of a workflow means rebuilding the steps after it, and those rebuilt actions start their statistics from zero. If you need the history, export it before you restructure.

What to look at first​

  1. Sent on the first email. If it's zero, the problem is enrolment, not sending: check the automation's trigger and that the automation is running.
  2. Sent at each later step. A sharp drop from one email to the next points to a wait or condition that isn't letting contacts through as you expected.
  3. How each condition splits. A very low Yes rate is a signal about the email before it.
  4. Unsubscribes per email. One email well above the others deserves a look at its content or its timing.

Next steps​