Subathon Analytics: Which Metrics to Track

When a subathon ends there is a question that matters more than the tiredness: what worked? Each platform shows its own numbers, on separate screens and with different criteria. This guide explains which metrics to track and how to read them, using the Results section of TriBathon, which brings the data from all your streams into one place.

Results in 66 s

1. Start with the Overview

The Overview tab answers "how did the period go?" with the key figures:

• Time added by events: the sum of what subs, bits, donations and the rest added to the timer across all your streams in the period. It doesn't include manual adjustments you made yourself.
• Streams and hours live: how many times you went live and for how long. If a stream is still running or has no known duration, the figure is marked "at least".
• Average viewers: an average per platform, weighted by the time that has samples. There is no "global" average.
• Highest combined peak: the moment with the most viewers at once across all your platforms, linking to the stream where it happened.

Below that, Moments highlights the stream with the most viewers and the one that added the most time, next to your "typical stream" of the period (the median). That median is the reference you need: a peak of 300 viewers means nothing until you know your typical stream has 60.

2. Separate subathons from regular streams

A subathon isn't measured like a normal stream: it lasts longer, time added is the central metric and the viewer peak often arrives late. TriBathon automatically classifies which streams were subathons from the timer history, and the Overview tells you ("3 of 8 streams were subathons"). If a stream is misclassified, Premium lets you correct it by hand.

3. Compare platforms, don't blend them

The Platform battle puts, for each platform, hours, average and peak viewers, followers, subs and time added in one table. It shows where your audience is and where your support is, which don't always match. If you multistream, this is the table that will change the most decisions.

4. Community: real growth, not activity

Community has two kinds of data that are easy to confuse:

• Channel totals (followers and active subscribers): the official figures from each platform, taken in daily snapshots. The net only compares snapshots of the same channel; if one is missing, you see "—".
• Activity received (follows, subs and gifted subs per day): what happened during your streams. Here a 0 is a real 0. Note: it isn't the same as net growth, because people also leave.

Below that is the list of the period's subscriptions: a gifted batch counts as one row with its quantity, and YouTube memberships are kept apart. With Premium you see every subscription, who brings you the most subs and who gifts the most.

5. Revenue: each unit on its own

Revenue breaks down what you received in bits, kicks, Super Chats and StreamElements and Streamlabs donations, each currency separate and unconverted. That's the real data. With Premium there is also an estimated total in a single currency, at the exchange rate of the day of each support. The full method to turn it into profitability is in was your subathon profitable?.

6. Trends: to decide your next stream (Premium)

Trends compares the last 30 days with the previous 30 (at least 3 streams are needed in each period for the comparison to make sense) and shows how viewers, consistency, games and best hours evolve. Time slots with few hours streamed don't enter the best-hours ranking, so a single lucky stream doesn't decide your schedule.

A 10-minute routine after every subathon

1. Open the period's Overview and note time added, hours and combined peak.
2. Compare the subathon stream with your typical stream (the median in Moments).
3. Check the Platform battle: where was the audience and where was the support?
4. Check the period's net follower and subscriber growth in Community.
5. Review Revenue by unit and note what weighed most: bits, donations, subs…
6. Adjust the next one: if time added piled up in a few moments, revisit your timing configuration.

Conclusion

The useful subathon metrics are few: time added, a viewer peak put in context, net community growth and an honest revenue breakdown. What matters is reading them without mixing what can't be mixed. Results is built for that, and the free tab already gives you the essentials for the last 7 days.