Read a flow report and see who was held back

Use the Flows list, a flow's report and the Recipients table to see what a flow sent, who it earned from, and who it skipped.

Updated · 3 min read

Where it is in the app

Open Home, choose Email & SMS, then Flows.

  • Home
  • Email & SMS
  • Flows

Every flow has a report. It tells you how many people entered, how many emails left, what was held back and why, and what the flow earned.

#The Flows list

Open Email & SMS, then Flows. Each row shows the flow's name and trigger, its Type, Status (Draft, Live or Off), Last updated, and four numbers: Sent, Delivered, Held, Revenue and Per recipient.

  • A date menu sets the window for the numbers: Last 7 days, Last 30 days (the default), Last 90 days or All time.
  • Held is a link when it is not zero. It opens the people the flow wanted to email and did not.
  • Per recipient shows a dash under ten delivered emails, because the number would be noise.
  • Last updated is approximate. It shows the later of when the flow was made and when it was last switched on.
  • Filter with the search box, Status, and Tags. Press Clear filters to reset.

The ⋮ menu on a row has Edit, Rename, Clone, Tags, Turn on or Turn off, and Delete. Clone copies the flow, switched off. Tick several rows to turn them on, turn them off, or delete the drafts together.

Click a flow's name to open its report.

#The report page

At the top are the flow's name and trigger, Live since the date, and the same date range menu (press Apply). The buttons are Pause (or Turn on) and Edit flow.

The figures:

  • Entered: people who started.
  • Sent: emails that left.
  • Held back: emails the flow wanted to send and we stopped. Click it to see who.
  • Waiting: people in the middle of the flow, with the time of the next email.
  • Delivered, Opened, Clicked: opens and clicks are shown as a share of delivered. Opens count real opens only.
  • Orders and Revenue in this window, with revenue per person emailed.

A sentence under the figures states the rule: an order counts for the flow when it happens within your attribution window of a click on one of its emails. An open on its own never counts. You set the window under Settings, Attribution.

#Held back, and why

The Held back — and why list names each reason and how many people it caught. Each row has see who. The reasons you can see:

  • Already had a marketing email inside your … cap. The Smart Sending limit.
  • They unsubscribed.
  • They marked you as spam.
  • Their address bounced before.
  • No opt-in on record, or Imported or opted out — not from your site, depending on your consent setting.
  • Imported without proof of consent.
  • Domain still warming up.
  • Locked by your plan.
  • Another rule held it back.

Held back is the safety net working. Nobody is emailed against these rules.

#Steps and Show more

The Steps table lists each email step with its Subject, Sent, Held, Delivered, Opened, Clicked, Orders and Revenue. Press Show more for bounces, unsubscribes, spam marks, click-to-open, average order, the next email time, and Left because counts for people who left early.

#The Recipients table

Press Recipients (next to Steps), or click any figure. The left list filters the table: Waiting, Recipients, Delivered, Opened, Clicked, Ordered, Bounced, Unsubscribed, Marked as spam, Held back. Each has a count. Waiting shows who is in the flow right now and ignores the date range.

Each row shows Email, Name, Step, What happened and the time. Click an email address to open that contact. Press See their path to see every step that person went through.

The table shows 25 rows per page. Export CSV downloads every row that matches the filter you are looking at, up to 100,000.

#If it didn't work

  • "Nobody has been through this yet." Nobody has entered. Check the flow is Live and that the trigger is something that has happened since you switched it on.
  • Revenue shows a dash. No order has been matched to a click on this flow's emails yet.
  • You cannot find a person. Check the date range, and the Held back list. They may have been skipped.
  • "We cannot read this flow's steps." The stored flow is invalid. Open it in the editor, or email support@aminoengine.com.
Was this helpful?

Still stuck? A person answers.

Email support@aminoengine.com and we answer within one business day.