Read flow metrics and engagement
You can see how often a flow runs, which way people go, and what they answer. Here's what each measurement, filter, and export includes.
Flow reporting helps you see which questions people answer, which offers they reach, and where they leave. Open Flows, select a flow, then choose Metrics or Activity in the builder's left panel.
Metrics and date scope
The Metrics date picker controls this flow's report. If you open it from the dashboard, the link can carry the dashboard's selected period and timezone. Check the dates before comparing it with another report.
Under the date picker, "Excluded browsers aren't counted in this flow's results." is a reminder that your own test runs may be missing. Activity shows the same reminder. The ⓘ beside it lists what isn't counted: excluded browsers, including any you've opened the debugger in, traffic matching your Stop collecting rules, and people you've hidden from analytics. Their forms, flows, and emails still run. See exclude test visitors.
Flow Performance opens with a summary counted in runs. A run is one time the flow was shown, so one visitor can add several. Hover over a dotted label to read its definition.
| Metric | What it counts |
|---|---|
| Views | Each time someone was shown this flow, counted once per run. |
| Starts | Runs where the visitor answered or skipped a question, submitted a form or clicked through an offer, or reached the end. |
| Submissions | Runs that reached the end. |
| Completion rate | Submissions divided by views. |
| Avg. time to complete | The average length of the runs that reached the end. |
| Unique visitors | Distinct visitors within this flow's report scope and dates. |
| Email known from the integration | Visitors whose email address your connected email platform knows. The percentage beside it uses unique visitors as its denominator. |
A system flow isn't shown to visitors, so it has no views or submissions. It shows Total executions, its recorded runs, and Avg. time in flow instead.
How runs ended separates the different ways a run can end. An unfinished run hasn't reached an ending. A form submission or CTA click is a specific action, not the same as every flow ending.
When a flow has questions set up to sync but little identified activity, the bottom of the left panel can show This survey may not be identifying visitors:. It's hidden while the panel is collapsed. Check the identification path, especially identifying parameters on a thank-you page. An email address in an answer cell doesn't necessarily mean RightMessage identified that visitor.
Node metrics and insights
Question nodes show Asks, Completions, and Answer Rate. Asks counts people the question was shown to, Completions counts people who answered it, and Answer Rate divides completions by asks. These count people, not runs, so someone who sees a question on two visits counts once. They cover the nodes in this flow, not every place you've used a shared question.
Offer and form nodes show the display and conversion measurements that apply to them. A Condition shows how many people went down Yes and No, and a Random Split shows how many went into each group. Those counts are routing by design, not drop-off.
Key Insights names the question where the largest share of people stopped, such as 62.5% stopped here (40 of 64 people asked), the offer or form with the highest abandonment, and the slowest question to answer. Select the target icon beside one to find that step on the canvas. Use these as places to inspect. They don't tell you whether the cause is wording, targeting, or a technical problem.
Ask Righty how the flow is doing and it quotes these same numbers for the date range you've selected.
Heat map and path flow
Enable Heat Map shows relative traffic on the canvas, so you can see which parts visitors reached. It doesn't identify a conversion winner.
Show Path Flow opens path analysis for the selected flow and dates. It loads separately from the execution metrics. Its analyzed-since date can be later than the start you requested.
Top Drop-off Points lists up to five steps where the most people stopped, across the whole date range. Someone counts as stopped at a step when they reached it and never got past it on any run in the range, so a person who left once and finished on a later visit isn't counted. When the range starts before question display tracking, those questions are left out of the list and a note shows the day counting started.
Don't add branch counts to calculate all-time visitors. Returning visitors and runs counted in different ways can overlap.
Activity list
Activity shows one row per recorded execution. Each row includes the visitor's identity when known, how the run ended, and how long ago it ended.
| If you'd like to… | Use |
|---|---|
| See runs from a particular period | The date range. |
| Find a visitor's runs | Email or visitor ID. |
| See all matching runs | All, the initial filter unless you have a saved selection. |
| See runs by identified visitors | Identified. |
| See runs that reached completion | Completed. |
| See runs that didn't reach completion | Dropped off. |
| Browse more runs | Pagination. If the report is capped, narrow the dates to reach older runs. |
| Compare answers across runs | Table view, which opens the responses table. |
Select a run to open its details. The drawer shows its recorded status, duration, start time, page, and execution path. It also shows device, location, and split-test variant when available. The node-location control takes you to that point on the canvas.
These details describe what RightMessage recorded at the time. They aren't a live browser replay or confirmation that your email platform accepted an update.
A step's own activity
Select a node on the canvas, then open Activity in its drawer to see only the runs that reached that step, with the same date range, search, and filters. Each row shows what happened at the step, such as the answer given.
For a Condition, each row shows the branch the run took: Went down followed by Yes or No. These are the same recorded branches behind the Yes and No counts on the canvas. A run that didn't record its branch shows a dash instead of a guess.
Responses table
Choose Table view in Activity, or View engagement data (the visitor count in the toolbar on the right of the canvas), to open the flow's responses as a spreadsheet. Its header shows how many runs answered at least one question out of every run that entered: 435 engaged (445 total) means 435 of 445 runs answered something. The ⓘ beside it lists the traffic these counts leave out, and Export CSV sits next to that.
Each row is one run. The first column shows the person, and stays in place as you scroll sideways. Select a person to open a quick look at their profile. Then come one column per question, in the order visitors meet them in the flow, and Outcome, Started, and Path.
- Question cells show the recorded answer, or Skipped, Not asked, Stopped here, or Closed here. A dot marks the question where an unfinished run stopped or was closed. A blank or unasked question isn't a negative answer.
- Outcome shows Completed, Abandoned, or Closed, with the step where the run ended.
- Path shows a dot for each step. Hover over or focus it to see each step's name and time.
Long values are shortened. Hover over a cell to read all of it. The table shows 50 rows per page.
Filter the responses
| If you'd like to… | Use |
|---|---|
| See runs that reached the end, left partway, or closed the widget | All, Completed, Abandoned, or Closed. |
| Find a person or an answer | Search by email or answer. |
| Change the period | The date button. It shares its range with Metrics and Activity, and the exact times show below it. |
| See only runs with a particular answer | Select that choice answer in the table. |
| Start over | Clear filters resets the outcome and removes every answer filter. |
Each answer you select becomes a pill under Match all:, so a row must match every selected answer. Select a pill to remove it.
Export CSV
Export CSV downloads rows matching the current dates, outcome, search, and answer filters. It doesn't switch to an all-time export. The button is disabled while the table or a pending search updates, or when no rows match.
Every plan can export CSV. Keep downloaded responses private, and include the selected dates when you share the numbers.
Missing and unavailable data
A failed request shows an unavailable message rather than an empty measurement. The responses table offers Retry. Runs recorded before display tracking appear only when they answered a question, and can lack shown, skipped, or stop-point events.
For the wider picture, see the dashboard reference or widget, form, and offer reporting. To decide what to change, follow See how your flow is doing.