Stream History

Stream History is your post-stream analytics. Every time you go live, Lumio records the run as a session and turns it into a report — viewer curves, follower and subscriber growth, chat, emote and GIF totals, donations, and a per-platform breakdown. If you multistream, one session covers all the platforms you broadcast to at once, and each platform's own title and numbers are kept separate.

This guide covers the webapp surface. For how the data is collected and the API behind it, see the Stream History feature reference.

Where to find it

Open Dashboard > Stream > History from the sidebar. The nav item appears when the feature:stream_history feature is enabled for your account and your role holds the history:read permission. Stream History is a baseline feature — it is enabled on every plan, not a paid unlock.

The Dashboard home also shows a compact Recent streams card — the last three sessions with a handful of headline numbers and a View all link into this page. It uses the same feature:stream_history flag and is hidden when the feature is off. The full list, filters, and reports live here on the History page.

The history list

The list shows one card per past session, newest first:

• Platform icons for every platform in the session.
• The session title and a badge — Single (one platform), Multi (a multistream), or a pulsing Live badge while the stream is still running.
• The date, duration, and category.
• A preview row of headline numbers: peak viewers, messages, new followers, and new subs.

Use the pager at the bottom to move through older sessions (25 per page). While a stream is live, the list refreshes on its own — new sessions and updated numbers appear without a reload.

Click View report on any card to open its full report.

Filtering and searching

A filter bar above the list narrows it down. All filters combine, and the page count always reflects the filtered result:

• Search — type part of a stream title to match sessions by their title or any of their per-platform stream titles (case-insensitive; updates as you type).
• Platform — show only sessions that streamed to a given platform.
• Category — show only sessions in a given category.
• Type — restrict to Single or Multi sessions.
• Date range — a paired From–To start-date range that sits with the other filters in the same bar; only sessions that began within it are shown. Each field opens an in-app calendar picker (localized month and weekday names, first day of week following your language). Picking a From date caps the To calendar at that day and vice versa, so the range always stays valid. Use Today to jump to the current month or Clear to drop the bound.

The Platform and Category dropdowns list only the values that actually appear in your history. Changing any filter jumps back to the first page, and the live refresh keeps your filters applied. Use Clear filters to reset the bar.

Sorting

A Sort by control sits at the end of the filter bar. Pick the field to order the list by — Date, Duration, Peak viewers, Avg. viewers, Messages, Chatters, or New followers — and use the arrow button next to it to flip between descending and ascending. The default is Date, newest first.

Sorting runs on the server across your whole history, not just the sessions on the current page, so the top result is the true maximum (or minimum) for the field you chose. When you sort by Duration, Peak viewers or Avg. viewers, sessions that have no value yet — a stream that is still live, for instance — sort to the bottom. The sort is independent of the filters — Clear filters leaves it untouched.

The report page

The report page assembles everything Lumio recorded for that session.

Headline cards summarise the session — peak and average viewers, unique chatters, messages, new followers, new and gifted subs, emotes, GIFs, donations, and duration. Platform-native support gets its own cards, kept clearly separate from donations: Bits, Raids (and raid viewers), and YouTube Super Chats and Super Stickers (with their combined value). Donations counts StreamElements tips only. A card is shown only when the session actually carries that number, so a stream with no donations — or no Super Chats — does not get an empty card.

For a single-platform YouTube stream the follower and sub cards read Subscribers and Members, matching YouTube's own terminology; a multistream keeps the neutral aggregate labels.

Stream table — one row per platform broadcast in the session. For a multistream you see each platform's own title, category, start time, duration, peak and average viewers, messages, and chatters side by side.

When a Twitch broadcast ran a Shared Chat session, the row is followed by a Shared Chat strip that names the channels the chat was shared with — each participating channel is shown with its avatar and how many messages it contributed. This tells you which channels the combined chat numbers are coming from. It is channel-level only (broadcaster identities, never individual viewers), and it appears only for broadcasts that actually had shared-chat activity.

Charts (drawn from the 60-second time series):

• Viewers over time — a line per platform plus a combined total, with the server-computed peak, low, and median markers highlighted.
• Follower growth and Sub growth — cumulative curves, with the follower chart marking the steepest rise.
• Subs by tier and Messages by platform — bar comparisons.

Long streams are automatically thinned to keep the charts fast and readable without losing the peaks and troughs. Charts follow your light/dark theme.

Top lists — your top ten chatters, top ten emotes, and top ten GIFs for the session. Each chatter is shown with the avatar their platform sent along with the messages (initials stand in when none was captured), each emote with its image where the platform supplies one, and each GIF with a thumbnail of the shared clip next to how many times it appeared.

Top lists are frozen into the report when the session is finalized, so older reports keep the shape they were written with: five chatters, no avatars, no emote images, and no GIFs.

Sharing a report

If your role holds the history:share permission, a Share button appears on the report page. It opens a dialog where you can:

• Choose how long the link stays valid — 1 hour, 6 hours, 24 hours, 7 days, or 30 days.
• Optionally set a password the viewer must enter.
• Optionally allow the viewer to export the report's data.

When you create a link, the full URL is shown once — copy it there and then, because it is not shown again. Existing links are listed below the form with their expiry, whether they are password-protected, and whether export is allowed. From that list you can extend a link by the currently selected duration or revoke it immediately.

Exporting a report

If your role holds the history:export permission, an Export button appears next to Share on the report page. It offers these formats:

• CSV (spreadsheet) — a ZIP bundle of sheets (summary, streams, time series, top chatters, top emotes, top GIFs) for opening in a spreadsheet.
• PDF (report) — a formatted document to archive or hand to a sponsor.
• Text summary — a plain-text digest to paste into Discord or a forum.
• JSON — the full report data.

The download starts immediately in your browser. Export is available only once a stream has ended — while a session is still live the Export button is disabled with a tooltip, because the numbers are not yet final.

Viewing a shared report

A share link opens at /share/history/{token} — a public, read-only page that needs no Lumio account. It shows the same report your dashboard does (KPI cards, viewer / follower / sub charts, the per-platform stream table, and the top lists) without the dashboard shell, the Share button, or any editing controls.

The public page is counts-only: donation and Super Chat/Sticker amounts are stripped from a shared report, while the corresponding counts (Bits, Raids, Super Chats) stay visible. A viewer of your link never sees how much money the stream made.

If the link is password-protected, the page first asks for the password. An incorrect password — or a link that has expired or been revoked — shows the same neutral error, so a viewer can never tell a wrong password apart from a dead link. A consequence of that: a dead link still asks for a password first, and only reveals the error once the viewer submits one. The page follows the system light/dark preference and is available in English and German.

If the owner enabled export for the link, the shared page also shows CSV, PDF, Text, and JSON download buttons; otherwise no export is offered.

The same exports are reachable programmatically. See REST API for the complete export surface.

Stream summary email

After a stream ends and its session is finalized, Lumio emails the account owner a summary: a viewer-trend chart, the key numbers (peak viewers, new followers and subs, donations, and a per-platform breakdown), a short recap, and a link to the full report. Streams shorter than 5 minutes are skipped.

You control this under Settings → Notifications, on the Stream summary row in the Stream category:

• Off — no summary at all.
• In-App — a dashboard notification, no email.
• Email — the summary email only, no dashboard notification.
• In-App + Email — both (the default).

Permissions at a glance

Permission	What it unlocks in the webapp
history:read	The History nav item, the session list, and reports
history:share	The Share button and share-link management
history:export	Exporting a report's data
history:delete	Deleting a stored session — available through the API; there is no delete control in the webapp

Owner and Administrator hold all four by default; Moderator holds history:read and history:export; Viewer holds none.