Real-time Dashboard
Track notification traffic as it happens with Fyno’s Real-time Dashboard: live status counts, trend cards, delivery rates, active alarms, and channel trends over a rolling window.
The Real-time Dashboard shows notification traffic as it happens, over a short rolling window, and refreshes itself automatically every 10 seconds. Where the Analytics Dashboard is built for reporting and trend analysis over days or weeks, the Real-time Dashboard is built for the minutes during and after a send.
The Real-time Dashboard is currently in Beta. Metrics and controls may change between releases.
Navigate to: Dashboard > Real-time. Real-time sits under Dashboard in the left menu and is not visible until you click Dashboard.

The page heading shows the current time next to the dashboard name. The Live badge means the dashboard shows live data. There is no Real-time Dashboard for test data.
Use the Real-time Dashboard to:
- Watch a campaign or bulk send as it executes.
- Catch a spike in Error, Failed, or Undelivered while you can still act on it.
- Confirm that a route, template, or provider change behaves as expected right after you ship it.
- Verify traffic is flowing at all before escalating to a provider.
Global controls
The controls at the top of the page set the scope for every widget on it.
To keep the same filters every time, select the time window and Analytics Labels you want, then bookmark the page.
The top of the page also has a Status Guide link, which opens the full status lifecycle reference, and a countdown to the next automatic refresh. No manual refresh is needed.
Status summary
The table at the top of the page counts every notification in the selected window at each stage of its lifecycle.

Every status except Requested shows a percentage below its count. The label under each column heading tells you what the percentage is measured against:
The table opens with a single All row that totals every channel. Click the arrow beside All to expand it and see the same counts broken down by channel, one row per channel, such as SMS, Email, and WhatsApp. Click the arrow again to collapse the breakdown.

Counts are derived the same way as elsewhere in Fyno:
Delivery reports arrive after the notification is sent, not at the same time. Fyno counts a notification under Sent as soon as the provider accepts it, but cannot count it under Delivered or Undelivered until the provider reports back, which can take seconds or minutes. Delivered therefore reads lower than Sent for a while after a send, and on a 5- or 15-minute window it may read zero while Sent is in the thousands. This is expected. Widen the window to 60 minutes before concluding that delivery has stalled.
Trend cards

Four cards plot the shape of traffic across the window. Each card shows its total for the window, a trend line, and Max, Min, and Avg below the chart. The vertical axis scales to the data in the window.
Max, Min, and Avg are the highest, lowest, and average values across the points plotted in the window.
Hovering over any point on one of the four charts shows the values at that exact time across all four cards.
The time of the hovered point is shown in the top-right corner of each card. The hover moves through the window one minute at a time, so no minute in the window is skipped.
Delivery rates
The Delivery rates table breaks delivery performance down for the same window.
Use the dropdown in the section heading to switch between three views:

- Notification Events Delivery Rates: grouped by notification event, for pinpointing which event is degrading.
- Provider Delivery Rates: grouped by provider, for spotting whether a drop is limited to one provider.
- Analytics Labels Delivery Rates: grouped by label, for tracking a campaign or business initiative as a whole.
Notification Events
Provider
Analytics Labels

The table carries the same statuses as the status summary: Requested, Error, Failed, Dropped, Attempted, Timeout, Sent, Delivered, Undelivered, and No DLR.
Table controls
Two controls sit above the table:
The table also has the following controls:
In full-screen view, the heading shows the selected time window and the refresh indicator.

Sorting
To sort the table, click the three-dot menu beside a status column heading and choose a sort order. Each option sorts in ascending or descending order.
For every status except Requested, you can sort by:
- Count
- %
- % Change, when comparing with yesterday
Requested is different. Requested has no percentage, so its menu has no % options. Without the comparison, Requested can only be sorted by count. When comparing with yesterday, its % Change options sort by the change in count from yesterday, not by a percentage.
Requested
Other statuses

Expanding rows
Each row can be expanded using the arrow beside its name, in every view. Expanding a row shows one row per integration that was used, with the channel shown beneath the integration name, and the status counts for that integration alone. A channel appears in more than one row when the notification event, label, or provider used more than one integration on it.
In the Analytics Labels Delivery Rates view, notifications sent without an analytics label are grouped in a No analytics label row.
The table shows 20 rows per page by default. Use Rows per page and the arrows below the table to change the page size or move between pages.
Active Alarms
The Active Alarms section shows every alarm with at least one occurrence in the selected window, including alarms first raised before the window started. You can see what has gone wrong next to the traffic it affected.

Each alarm appears as a card with:
- The alarm name and its severity: High, Medium, Low, or Info.
- The number of occurrences in the window, with a bar chart of occurrences across the window.
- What the alarm relates to, such as the workflow, notification event, provider, or integration.
- When it last occurred.
- View, which opens the full alarm details.
The severity chips in the section heading show the total number of alarms at each severity level in the selected window.
If no alarm has occurred in the selected window, the section shows a message saying all is calm in place of the cards.
Full-screen view
Click the full-screen icon in the section heading to open Active Alarms in a full-screen view. The heading keeps the severity chips and also shows the selected time window and the refresh indicator. Click the icon again to return to the dashboard.

Channel trends
A card is shown for each channel with at least one notification requested in the selected window. Each card plots Requested and Attempted for every minute in the window, with the total for each shown above the chart. Requested is plotted in grey and Attempted in the channel’s colour.

Hover over a point on the chart to see the Requested and Attempted counts for that minute. The time of the hovered point is shown in the top-right corner of the card, and the counts above the chart change to that minute’s values.

Comparing with yesterday
Select Compare against the same window yesterday at the top of the page to see how today’s traffic compares with the same window yesterday. Every section of the dashboard except Active Alarms updates to show the comparison.

How the change is calculated
Each value gets a change chip with an up or down arrow. The change is calculated differently for Requested and for the other statuses:
The change for Requested is a count, not a percentage. Wherever Requested is shown, in the status summary, the trend cards, the delivery rates table, and the channel cards, its chip shows how many more or fewer requests there were than yesterday. Every other status shows a percentage.
What changes in each section
Status summary
Trend cards
Delivery rates
Channel trends
The chip for Requested appears below its count. For every other status, the chip appears next to today’s percentage.

Hover over a value to see the exact counts for yesterday and today, for example Yesterday: 172,627 and Today: 174,674.
