Last updated: March 2026 Category: Flows
Overview
Flow Statistics give you a clear picture of how your automations are performing. From high-level conversion rates to per-node delivery metrics, the stats page helps you identify what is working, what needs attention, and where to optimize.
Prerequisites
At least one active flow with some executions
Familiarity with flow nodes and goals (see Flow Goals and Conversions)
Step-by-Step Guide
Accessing Flow Statistics
Navigate to Flows in the left menu.
Click on the flow you want to analyze.
Click the "Statistics" tab at the top of the flow editor.
[Screenshot: Flow statistics page showing summary cards and per-node metrics]
Understanding the Summary Cards
At the top of the statistics page, you will see high-level summary cards:
Total Executions — The total number of times users have entered this flow since activation.
Currently in Flow — How many users are currently progressing through the flow (waiting on a delay, pending an action, etc.).
Total Conversions — The number of users who triggered a Goal event within the attribution window.
Conversion Rate — Conversions divided by total executions, displayed as a percentage.
Total Revenue — The sum of all purchase revenue attributed to this flow's goals.
Average Revenue per Conversion — Total revenue divided by the number of conversions.
Per-Node Metrics
Below the summary, each node in the flow displays its own metrics:
Trigger Node — Shows how many users entered the flow and the entry rate over time.
Delay Node — Shows how many users are currently waiting, how many have passed through, and the average actual wait time.
Send Push Notification Node:
Sent — Total notifications dispatched.
Delivered — Notifications successfully received by the device.
Tapped — Notifications the user tapped to open.
Delivery Rate — Delivered / Sent as a percentage.
Tap Rate — Tapped / Delivered as a percentage.
Condition Node — Shows the count and percentage of users who took the IF branch vs. the ELSE branch.
Split Node — Shows the actual distribution of users across branches compared to the configured percentages.
Goal Node — Shows conversions, conversion rate, and attributed revenue for that specific goal.
Webhook Node — Shows the count of successful calls, failures, and retry attempts.
[Screenshot: Per-node metrics overlay on the flow canvas, showing sent/delivered/tapped on a push notification node]
Filtering by Date Range
Use the date range picker at the top of the statistics page to filter metrics to a specific time period. Options include:
Last 7 days
Last 30 days
Last 90 days
Custom date range
This helps you compare performance across different time periods or measure the impact of changes you made to the flow.
Exporting Statistics
Click the "Export" button to download the flow's statistics as a CSV file. The export includes summary metrics and per-node breakdowns for the selected date range.
Key Concepts
Statistics update in near real time. Metrics refresh as users progress through the flow. There may be a delay of a few minutes for revenue attribution.
Per-node metrics help you pinpoint bottlenecks. If a push notification has a low tap rate, the issue is the message content. If a condition sends most users to the ELSE branch, your targeting may need adjustment.
Conversion rate is your north star. A high execution count with a low conversion rate means users are entering but not converting — review your delays, conditions, and message content.
Tips and Best Practices
Check statistics weekly. Regular review helps you catch issues early and capitalize on trends.
Compare per-node metrics to find drop-off points. If 1,000 users enter but only 200 reach the second action, investigate what is happening in between (conditions filtering too aggressively, delays too long, etc.).
Use date range filtering to measure the impact of changes. After editing a flow, compare the last 7 days to the previous 7 days to see if performance improved.
Focus on tap rate for push notifications. A good tap rate is 5-15%. If yours is below 5%, experiment with different copy, images, or send times.
Track revenue per flow. Use the attributed revenue to calculate the ROI of each automation and prioritize your optimization efforts accordingly.
FAQ
Q: Why do I see more "Sent" than "Delivered" on a push notification node? A: Some notifications may fail to deliver due to expired push tokens, disabled notifications on the user's device, or network issues. This is normal.
Q: Can I see statistics for a flow that is paused or in draft? A: You can view historical statistics for paused flows. Draft flows that have never been activated will have no data.
Q: How is revenue attributed if a user receives multiple push notifications from the same flow? A: Revenue is attributed to the Goal node, not to individual push notifications. As long as the purchase occurs within the Goal's attribution window, it counts.
Q: Can I set up alerts for flow performance? A: Automated performance alerts are not currently available. We recommend setting a weekly reminder to review your flow statistics.
Related Articles