Analytics
Each project on its own relevant measure
Beyond the visit.
Rounds finished, music heard, links checked. Open a result to see its daily history, try the product and share that exact story.
2026-07-26 to 2026-10-23 UTC · same saved report throughout · today is partial
Protocol 11
0h 7m 38sClassic active gameplay
Partial coverage
Classic mode only. Accepted active gameplay seconds are not completed hands, scores or unique players. Read the selected window’s source coverage before comparing periods.
Explore this result
SHOALSHOT
2Reported completed runs
Partial coverage
Accepted terminal game/result transitions, including repeat runs. Client-reported activity is not a validated competitive score, catch or unique player.
Explore this result
Link Check × App Composer
25Completed Link Checks
Bounded count
Reported completed inspections, including repeat jobs. Bounded counters can omit activity. These are not unique people or proof of a composed owner workflow.
Explore this result
Bubbles
0Reported completed runs
Partial coverage
Reported terminal runs across supported games, not a count of successful board clears. Replay measurement is unavailable in this source, not zero. These are not unique players or best scores.
Explore this result
Fighter
155Reported fight completions
Legacy/test risk
Accepted non-tutorial fight results: win, loss, draw or forfeit, attributed to launch day. These are not wins or unique players. Consult the selected source coverage for historical verification risk.
Explore this result
LoftwahFM × games
7h 42m 34sAll-source audible listening
Legacy/test risk
Accepted audible music time across all admitted sources. This is not gameplay time or unique listeners. History before 15 October may include unmarked verification.
Explore this result
Available observations lead; legacy/test history and missing measures follow. Editorial order applies within each group, never the size of incompatible totals. Recorded activity is not a count of people. A zero is measured; “Not measured” means no retained evidence. Historical verification limits follow each result into its story and export.
3 findings from this report.
Chosen from this report only: the strongest complete-week movement, the busiest measured hand-off from Woodhouse, a source that started reporting inside these dates, then Woodhouse's own reading traffic. Where every number comes from.
Discovery · App Composer
7recorded clicks
The busiest measured hand-off from Woodhouse went to App Composer.
26 July 2026–23 Oct 2026
- What this establishes
- 5 in the most recent seven days. The earlier seven days recorded only 2 of 7, so no comparison is claimed.
- What it does not
- That anyone played, tried or kept using it: this counts the outbound action on this origin, not what happened at the destination.
New collection · App Composer
11days recorded
App Composer began reporting inside these dates, so this is the first comparable history it has.
from 13 Oct 2026
- What this establishes
- Everything before 13 Oct 2026 was never recorded. It is missing, not zero.
- What it does not
- That the product was unused before collection began, or that the first days are representative.
Woodhouse · its own audience
4,211visits
42 of those visits met the source's engaged-session threshold.
26 July 2026–23 Oct 2026
- What this establishes
- 4,211 anonymous tab sessions admitted, 42 engaged.
- What it does not
- How many individual people read anything, or whether they came back: both need a measure this source cannot supply.
What this report cannot show yet
- No two adjacent complete weeks are available in retained history for these dates.