Skip to main content

Scenario Metrics & Performance Tracking

Read scenario performance in Inrō: summary stats, per-step funnel metrics, and the full history of every execution.

Once a scenario is active, the Insights view shows exactly how it's doing: not only totals, but per-step metrics overlaid on the flow itself, and a full record of every individual run.

Open it from inside the builder with View insights in the top-right corner, or from the Scenarios list by hovering a scenario and choosing ⋯ -> View insights.

The Insights tab

Summary stats

The left panel shows the top-level numbers:

  • Executions, last 7 days and total, with an up or down trend.

  • Conversions, last 7 days and total, with a trend.

The Insights summary panel showing executions and conversions for the last 7 days and all time.

A conversion is counted whenever a step in the run records one. The most common source is a conversion-link click; every click on a conversion link counts as a conversion. Survey completions and payments can count too.

Per-step metrics on the flow

The right panel shows your flow as read-only nodes with metrics on each one. This is where the real detail lives.

  • Message steps show sent and read.

  • Conversion links show sent, read, clicked, and converted.

  • Contact steps show counts like added, removed, or updated.

  • Conditions, waits, and other logic steps show how many contacts passed down each branch.

Reading top to bottom gives you a funnel. Where the numbers drop sharply between steps is where contacts disengage, so that's the step to work on. Click any number to see the list of people behind it.

The History tab

The History tab is a record of every individual run of the scenario.

The History tab listing executions with contact, trigger, status, and date.

The execution list

Each row is one run: one contact going through the scenario. A row shows the contact's name and handle, folder tags, a View conversation link that jumps to the inbox thread, a timestamp, and a status.

Expanding a run

Click a row to see the step-by-step breakdown. For each step you can see whether it completed, and for Send message steps you'll see the actual text that went out, including how variables resolved for that contact. For a run still in progress, you'll see a spinner on the current waiting step and a Cancel button.

Filtering and searching

Filter the list by status, search by contact, and pick a date range. The status filter includes completed, in progress, failed, interrupted, and limited. "Limited" runs are paused because your account hit its monthly contact-activation cap; they resume after you upgrade.

Retrying failed steps

When a step fails, you can retry it. In the Insights flow a node with failed runs offers a retry control, and in the History tab you can retry an individual run. This re-runs the step and continues the flow from there.

How to use metrics to optimise

Start in the Insights tab and scan the flow top to bottom. Look for a step where the sent number drops sharply against the step before it. A big drop means contacts aren't reaching that step, either taking a different branch or not converting on the previous one.

For message steps, compare sent to read. A low read rate on an early message usually means the DM isn't being opened at all. For conversion links, compare sent to clicked; a low click rate usually points to the card design or the timing of the ask.

When you find a weak step, open the History tab and read a few real runs around it. The fix is often obvious once you see the actual conversation.

🐾 Netsuke's Tips

  • Check the History tab in the first 24 hours after activating a new scenario. Real runs reveal edge cases that test mode can't, especially in how contacts reply.

  • The View conversation link is one of the most useful features in Inrō. When a contact behaves unexpectedly, it gives you the full context in seconds.

  • Low conversion totals don't always mean the scenario is weak. Check the per-step metrics first; if contacts drop off before they reach your conversion link, the problem is earlier in the flow.

  • Use the date filter to compare quality before and after an edit. If you changed your opening message last Tuesday, filter to before and after to see if read rates moved.

What's next?

You can now build, run, and optimise scenarios. To send proactive outreach to a chosen audience instead of waiting for a trigger, read What Are DM Campaigns?. To revisit the canvas, see The Flow Builder: Visual Editor Tips & Tricks.

Did this answer your question?