Version: 1.30.0. Source reviewed at 4171265227d8ea584bca359ba40b09d3ac0c8c6a on 2026-10-09.
Status: Complete written guide; source-reviewed behavior. No new v1.30 screenshots, screen recording, native export/clipboard test, or cloud-data test was performed for this guide. Existing v1.29 captures contain fictional analytics and remain historical. The companion narration is an untimed draft pending recording and timing.
Analytics combines a live show snapshot, persistent performance history, historical night/gig exports, and account-saved favorites. Each answers a different question and has its own scope. Read the heading and selectors before quoting a number or exporting a report. For a venue handoff about a particular night, use History & Venue Reports → Export a night or gig, explicitly select the night and gig, then inspect the saved file. [1]
The live header's Copy/Print controls use the current show snapshot. Changing the history browser's date does not change that snapshot, and changing a historical export selector does not filter the visible live cards. [1][3]
Choose Refresh to load the current show snapshot. Read any error before interpreting the values. The main cards are:
Top singers shows completed songs, group participation, and applause by singer. Top songs shows tracked performed songs and applause. The live song aggregation is keyed by the show's song identifier, so do not assume every same-title row represents one combined title total. Both on-screen lists show at most 12 rows.
Hourly activity shows completed turns by local hour, with solo/group totals. Performance log shows time, singers, song, solo/group type, and applause for the latest 50 events on screen. A multi-singer performance is one completed turn in the live snapshot; each participating singer can receive credit. The exported live performance list can contain more rows than the on-screen log. [1][4]
Use the header controls after Refresh:
Wait for the copied confirmation, then paste into the intended destination and inspect the result. Clipboard refusal is surfaced as an error. If Print Report cannot open, the tab asks for pop-ups to be allowed; use the native historical export flow when that is the output you need. Copying does not create a disk file or send anything to a venue.
Open History & Venue Reports and locate the History section below the export controls. Choose a specific night in its date picker, or All time (combined). The recent-night chart shows up to the latest 30 nights; clicking a bar selects that night, and clicking the selected bar again returns to the combined view.
Check the heading and totals, then review songs, artists, singers, and the log. A single night shows its Set list chronologically. All time shows Latest performances, limited to the latest 100 history rows. Historical records include the Source field so imported history can be distinguished from other records. Top tables show the first 12 returned rows. [1][4]
History is stored as singer-credit rows: a duet can create one row for each participant at the same song/time. The History browser's “performances” count counts these rows, while the live Completed card counts turns. The historical export groups matching song/time credits back into events. These figures can legitimately differ; check their definitions before comparing them. [4][5]
The History date picker does not set the separate export date. Set both deliberately if you want the visible night and saved report to match.
Most sung aggregates the currently loaded history log into singer/artist/title combinations, ordered by count and then recency. Search by singer, artist, or song. The table gives Times sung and Last Performed and displays at most 100 aggregate rows. [1][2]
Important scope limit: Most sung follows the History browser's chosen night, but has no night selector of its own. With All time (combined) selected, the underlying log contains only the latest 100 history rows, so these counts are not a complete lifetime leaderboard. Select a specific night in History first when you need that night's complete loaded log. The all-time History summary totals use separate full-scope queries; do not infer that the Most sung counts share that full scope. [1][4]
Saved favorites fetches actual songs starred by signed-in singer accounts. It includes eligible singers who performed or checked in at this host's shows and songs in the host's catalog. Guests cannot save favorites. The table shows the song, how many distinct singers saved it, and their names. Search matches song, artist, or any saver name. A favorite is a stated preference, not proof it was performed. [1][2]
The view requires a host account and internet access. Read the sign-in or connection error and use Retry when offered. It is not narrowed to the selected historical night or currently selected gig. A successfully loaded result is kept for the lifetime of this Analytics tab; the header Refresh reloads the live snapshot only. To get a fresh successful favorites result, leave Analytics, return, and open Saved favorites again.
Most sung and Saved favorites share their search text. Clear the search when switching if results appear unexpectedly sparse. An empty filtered table is different from an empty source.
Older history rows without a gig tag appear under All gigs only. An empty gig-specific report can therefore coexist with visible older history. Gig selection affects stamping for performances recorded afterward; it does not retroactively attach a gig to all earlier records. [1][4]
The historical export groups identical artist/title/time singer credits into a single completed event. It calculates hourly activity by local hour of day and estimates average wait as average minutes between consecutive performance events multiplied by the number of singers minus one. Historical rows do not contain actual request/queue timestamps. [5]
For a multi-night export, long gaps between nights can enter that spacing calculation, and the hourly chart combines those nights by hour of day. Prefer a single night and gig for a practical venue readout. The staffing text is a deterministic heuristic: a peak of at least 15 songs in an hour or an estimated wait over 90 minutes can trigger a suggestion for support. Treat that as a prompt for judgment, not a measured labor requirement or guarantee that one host is sufficient. [5]
A finished report has an explicit intended scope, a successful copy/save result, and a reviewed output whose sample rows and totals match that scope. Confirm that an HTML export or printed PDF actually opens before a venue handoff. This guide does not claim native file, clipboard, printing, or cloud-favorites verification. [1][2][4][5]
All links are pinned to the reviewed v1.30 source and require access to the private repository.