Stream statistics

Comes with strAImer: this module is installed together with the app, so there is nothing to download. It is listed under Module Catalog → Built-in.

What this page is

Statistics in the sidebar keeps a record of every stream — messages, donations, subscriptions, bits, rewards, raids, followers, viewers — and shows it as totals, top lists, a raw event list and charts. The line under the heading says where it all lives: "Totals, top lists and raw data for every stream. Everything is stored locally."

How to set it up

1. Open Statistics in the sidebar. The page opens on Totals; the other three tabs are Data, Charts and Settings.
2. Totals shows one card per stream, newest first. The card header carries the date, the duration, the game and the platforms; a stream still running shows a ● LIVE badge in place of the duration. The tiles below count messages, donations, donation total, subscriptions, gifted, bits, followers, rewards, raids and peak viewers. What counts as one stream: it begins when Automation → Stream Status sees you live and ends when it sees the stream over. Going live again within 20 minutes carries on the same card, so a restart of the app or OBS, a dropped connection or a broadcast you stopped and started again all stay one stream. Only a break longer than 20 minutes starts a new card. A donation that arrives while you are not live is still recorded. If you go live again within those 20 minutes, it joins the card of the stream that carries on; otherwise it is not on any stream's card. The platforms listed are the ones you actually went live on, not the ones you have connected. A platform you never started that day is not shown, even with its connector on and its chat being read. Streams recorded before this was corrected still list every connected platform — that old history is not rewritten. And if you stream through OBS alone, without starting the broadcast on the platform itself, the app cannot tell where it went out, so the line stays empty instead of guessing.
3. Click a card header to unfold it. Inside are four top lists: Top chatters, Top donators, Top cheerers and Top gifters. Each list starts with five rows. When any of them has more, a Show everyone button appears under the lists and opens every row of all four. A list with nothing in it shows a dash.
4. Data is the raw list of events, newest first, up to 200 at a time. The chips above it filter by kind: All, Donations, Subscriptions, Bits, Rewards, Raids, Followers. Beside the chips sit two buttons, Add donation and Import from file: the first writes down a donation that came by card or cash, the second brings in a history exported from DonationAlerts or DonatePay. The guide "Adding and importing donations" describes both.
5. To remove a record — a test donation, say — point at its row in Data and press the ✕ button that appears on the right; it is titled Delete. The confirmation Delete record? says: "The record disappears from statistics and the stream totals are recalculated without it. If the donation counted towards goals, the carousel or the auction, it stops counting there too. This cannot be undone." Cancel leaves it alone. A donation that came in only as history, from a file, or by hand without Count as a live donation never counted there, so deleting it takes nothing away from them. This holds for history loaded from strAImer 0.27.0 on.
6. To delete a whole stream — a five-minute test, say — unfold its card on Totals and press the bin in its bottom right corner. The confirmation Delete this stream? names the date and says what goes: "Everything recorded for {date} is erased: donations, subscriptions, bits, rewards, raids, followers, the chat log and the viewer chart. Donations that counted towards goals, the carousel or the auction stop counting there too. This cannot be undone." The stream disappears from Totals, from Data and from the charts at once. A stream still running has no bin — recording is still going, and it can be deleted once the broadcast ends.
7. Charts holds two blocks. Stream over stream draws one bar per stream, and the chips choose what is measured: Donation total, Messages, Peak viewers, Followers. Viewers during a stream draws the viewer count through a single stream, picked from the dropdown of dates; the peak is written in the corner.
8. Settings → Chat log decides how much chat text is kept: "Message counters and top chatters are always kept. This setting only controls the full message text (bulky data): for how many recent streams to keep it." Switch Store full chat log on or off, set Keep chat log for recent streams to a number from 0 to 100, and press Save.
9. Settings → Count donations from is one checkbox per donation service. Ticked means counted: "An unchecked source is excluded from totals and tops. New sources are counted automatically." This block saves the moment you tick — it has no Save button of its own. A service that is installed but switched off is marked (disabled); with none installed the block reads "No donation connectors installed". An unticked source is not written down at all — the donation never becomes a record, so it is missing from Data as well as from the totals, and ticking the box again does not bring back what arrived while it was off. This is the one switch on the page that loses money records rather than hiding them; leave it alone unless you are sure. DonationAlerts and DonateX are the exception: tick the service again and press Rebuild donation history (step 10), and its donations are pulled back in without duplicates. For DonatePay the way back is Import from file on the Data tab.
10. Settings → Donation history has Rebuild donation history: "Pull the full donation history again from the services that provide it (DonationAlerts and DonateX). Donations already in statistics are not duplicated. Useful after failures; the service must be connected." After the press the line beside the button reads "Started — history will be pulled in the background ✓". If no service has loaded its history yet, it reads "Nothing to rebuild yet: services with history load it themselves when they connect." The rebuild obeys Count donations from: a service unticked there gets nothing pulled in, even though the line still says it started. Tick it first. Both services load their history on their own once, when they first connect. DonateX does so from module version 1.3.0, so a DonateX connected earlier loads its history on the first start after that update. History arrives the same way as an import from a file: into the totals and the tops, with no alerts and no change to goals. DonateX leaves out the test donations sent from its dashboard.
11. If amounts are stored in more than one currency, a strip appears above the cards on Totals: "Some amounts are stored in another currency ({count}) — totals mix them. Convert the history to {currency}." Convert brings them to the base currency and reports what it managed: "Converted: {updated}. Failed: {skipped} — no rate for them (for example, bits without a set rate)."

What it cannot do

• The base currency is not chosen here — that is Settings → Localization. This page only offers the conversion once amounts have diverged.
• Deleting works on one record or one whole stream — nothing in between. There is no way to select several records or to edit one. By hand you can add a donation, but not a stream, a subscription or any other event.
• Deleting cannot be undone here. There is no undo and no bin on this page. There is one way back, and it has to exist beforehand: a snapshot made in Settings → Backup with the statistics boxes ticked. Restoring it puts back every stream whose records are no longer in the database, the deleted one included.
• Deleting a donation takes its money back out of goals, the carousel pot and the auction, not what the money already did. An alert that played has played, a carousel card that came up has come up, and a lot that was already won stays won. A finished auction is left alone entirely; only one still running has the bid annulled.
• Each donation goal gives back exactly what it got from that donation, and only once. A goal that was paused or switched off when the donation arrived loses nothing, even if it is running again by the time you delete. This holds for donations that arrived from strAImer 0.25.0 on. For older ones the app does not know which goals they reached, so the amount comes off every goal that is not paused at the moment you delete, which is only roughly right.
• A donation deleted from a goal that has already been reset does not push the goal negative — it stops at zero, and the app says so in the log rather than pretending it subtracted the whole amount.
• Rebuild donation history pulls DonationAlerts and DonateX and nothing else. DonatePay gives the app no history to pull, so its past donations come in only through Import from file.
• Nothing is exported from this page — no download button and no report. A file does exist elsewhere: the snapshot in Settings → Backup carries statistics when you tick Donation history and stream totals and Chat messages and viewer counts. It is JSON meant for restoring, not a table to open in a spreadsheet, and there is no CSV or XLSX anywhere in the product.
• Followers are counted on Twitch only. No other platform sends the app a follow event, so the followers tile, the Followers chip and the Followers line on the chart stay empty for a streamer who is not on Twitch — and show Twitch's number, not zero, when streaming to Twitch and Kick at once.
• The stored chat log cannot be read anywhere. With Store full chat log on, the text is written and kept, but no tab and no page shows it back — it exists for the backup only. Message counts and Top chatters do not depend on that setting and are kept either way.
• The lists are capped — Totals goes 60 streams back, Data loads 200 records per filter, and Stream over stream draws the last 14 streams. There is no date range to set, and no search by viewer name.
• Charts measures only the four things on the chips; nothing else can be plotted.
• There is no switch for which kinds of event get recorded. Apart from the donation services and the chat log, everything that arrives is written down; the chips on Data only filter what is already stored.