Protocol 11 analytics

Play & engagement by mode

Custom dates
UTC · max 90 days
24 Sept 2026 – 23 Oct 2026 · 30 days · Today is partial1/1 reporting projects for this measure · 7/7 sources reporting · Saved snapshot

This report is frozen at 2026-10-23 07:46 UTC. Refresh these dates · Latest 30 days

Game starts · Protocol 11

Count per UTC day · gaps mean unavailable

A recorded launch into gameplay. Repeat play counts again. These are browser reports, not verified players.

Game starts
1
Partial coverage
Game completions
0
Partial coverage
Active play time
7m 38s
Partial coverage
1009-2410-0810-23

Inspect a date to see source values. The data table below works without interactive charts.

Chart data & export

These are daily values for game starts. A dash means unavailable. Daily distinct-browser counts must not be added to estimate period-level people.

Game starts· UTC dates ·count
DateProtocol 11
2026-09-24—missing
2026-09-25—missing
2026-09-26—missing
2026-09-27—missing
2026-09-28—missing
2026-09-29—missing
2026-09-30—missing
2026-10-01—missing
2026-10-02—missing
2026-10-03—missing
2026-10-04—missing
2026-10-05—missing
2026-10-06—missing
2026-10-07—missing
2026-10-08—missing
2026-10-09—missing
2026-10-10—missing
2026-10-11—missing
2026-10-12—missing
2026-10-13—missing
2026-10-14—missing
2026-10-15—missing
2026-10-160partial
2026-10-170clean
2026-10-180clean
2026-10-191clean
2026-10-200clean
2026-10-210clean
2026-10-220clean
2026-10-230partial

Can we compare these dates?

Coverage for the selected measure. Colour describes evidence, not popularity.

Comparable full dayPartial dayLegacy / test riskBounded / sampledNot measured
24 Sept 202623 Oct 2026
Protocol 11

The longest available comparable history in this selection is 6 complete daily observations. First collection days and today remain partial. Legacy activity may include tests that cannot be separated.

Local vs online play

Protocol 11 reports the play mode of every accepted gameplay event. Local play is Classic plus Journey; online play is Private room plus Public matchmaking. Each accepted event belongs to exactly one mode, so these subtotals are additive with the overall measure above them, not a second measurement of it. Every mode measure carries its own four-part definition in the source register below.

The split begins inside this window (2026-10-16), so earlier days are gaps rather than zeroes and the subtotals only add up over the days they cover. Visits and engaged sessions are not split by mode: one tab session can span several modes, so per-mode session counts would overlap.

Have browsers come back?

These are optional browser signals, kept separate for each project. They cannot identify people or establish cohort retention. Daily browser counts do not add up to a period total.

  • Protocol 11Not measured for these dates

    DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill. Browser returns are unavailable until this product releases its own optional consent client.

What changed around this activity?

Dated release observations sit beside the collection and comparison boundaries reported by each source. Nearby dates suggest questions to investigate; they do not show that a release caused a change in use.

This is a reviewed selection, not a complete release feed. Notes are frozen with the report and may precede the selected dates; notes after its last selected day are omitted.

Explore 5 dated release and collection notes
  1. Protocol 11 · Collection began

    First source-reported collection date. Earlier activity is unavailable; the first day may be partial.

  2. Protocol 11 · Comparison boundary

    The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.

  3. Protocol 11 · Current table release and anonymous measurement source

    Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Owning source and release receipt reviewed. Synthetic production QA sent no engagement events; that exclusion is not evidence of real audience collection. The later phone clearance draft has not shipped.

    Read release evidence · reviewed 2026-10-16
  4. Protocol 11 · Protocol 11 · later player-feature delivery

    The qualified feature tree and deployed assets are recorded separately from later tooling/documentation. The public readiness endpoint independently reported production D1 and matchmaker ready. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The owning browser qualification is a frozen composite, not one uninterrupted full-suite run; actual-domain browser UI remained blocked. Source/runtime equality and live readiness are distinct from that interaction gate. The current v2 film is a disclosed one-round demonstration; broader campaign acceptance remains open.

    Read release evidence · reviewed 2026-10-13
  5. Protocol 11 · protocol-11 · exact radio deployment

    The Jukebox combines the original soundtrack, six FM music stations and two shows under one stream owner. Explicit Play, saved controls, bounded refresh and original fallback preserve table feedback. Physical iPhone and human audible acceptance remain open. Stable hand ordering, legal targets, Flaming feedback and desktop table visibility remain unresolved player-facing work.

    Read release evidence · reviewed 2026-10-11

Follow the numbers to their source

Every measure has a definition, a collection boundary and blind spots.

Protocol 1122 measures available

Live aggregate endpoint · generated

Collection began
2026-10-16T00:00:00.000Z
Comparable history from
2026-10-16T00:00:00.000Z
Source revision
Not supplied
  • Exact accepted event counters, not unique humans or anti-cheat proof. Blocking, opt-out, offline play and automated traffic affect coverage.
  • DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill.
  • Current UTC day and collection-start day may be partial. Cross-device retention, cohort retention and acquisition sources are not measured.
  • Browser returns are unavailable until this product releases its own optional consent client.
  • Mode subtotals come from the same accepted gameplay events as their overall measure: from the day the split begins, the mode subtotals sum exactly to that measure, and a day with no row for a mode is a measured zero for it. Before the split begins there are gaps, not zeroes, and raw history older than 90 days cannot be reconstructed.
  • Visits and engaged sessions are tab session markers and are deliberately not split by mode: one tab session can span several modes, so per-mode session counts would overlap and double-count.
Visits 14Reported activity
One accepted visit marker per tab session; sessions reset after 30 minutes idle. Reloads in the same session do not add visits. Not distinct people.
Engaged sessions 4Reported activity
One accepted marker per tab session after at least 10 seconds of active product use. Foreground, unpaused and recent trusted input required.
Games started 1Reported activity
Accepted new game/dive start actions; restoring or resuming a saved game does not count. Client reported, not verified human play. Multiplayer tabs report participations, not distinct tables.
Games completed 0Reported activity
Accepted terminal game/result transitions. Client reported; not a validated competitive result. Multiplayer tabs report participations, not distinct tables.
Deliberate replays 0Reported activity
Accepted deliberate repeat new-game actions in the same tab session, after completion or abandonment. Automatic restores/resumes are excluded.
Active time 7m 38sReported activity
Accepted 1–30 second foreground, unpaused activity increments, ending 30 seconds after trusted input. Server bounds total by session wall time. Radio time is excluded.
Game starts · Classic 1Partial measurement
Accepted new game launches the client reported as Classic, excluding restores and resumes. Counted from accepted game_start events whose mode is classic. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
Game starts · Journey 0Partial measurement
Accepted new game launches the client reported as Journey, excluding restores and resumes. Counted from accepted game_start events whose mode is journey. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
Game starts · Private room 0Partial measurement
Accepted new game launches the client reported as Private room, excluding restores and resumes. Counted from accepted game_start events whose mode is private_room. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
Game starts · Public matchmaking 0Partial measurement
Accepted new game launches the client reported as Public matchmaking, excluding restores and resumes. Counted from accepted game_start events whose mode is public_matchmaking. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
Game completions · Classic 0Partial measurement
Accepted terminal results the client reported as Classic, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is classic. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
Game completions · Journey 0Partial measurement
Accepted terminal results the client reported as Journey, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is journey. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
Game completions · Private room 0Partial measurement
Accepted terminal results the client reported as Private room, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is private_room. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
Game completions · Public matchmaking 0Partial measurement
Accepted terminal results the client reported as Public matchmaking, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is public_matchmaking. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
Deliberate replays · Classic 0Partial measurement
Deliberate repeat new-game actions in Classic inside the same tab session. Counted from accepted game_replay events whose mode is classic. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
Deliberate replays · Journey 0Partial measurement
Deliberate repeat new-game actions in Journey inside the same tab session. Counted from accepted game_replay events whose mode is journey. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
Deliberate replays · Private room 0Partial measurement
Deliberate repeat new-game actions in Private room inside the same tab session. Counted from accepted game_replay events whose mode is private_room. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
Deliberate replays · Public matchmaking 0Partial measurement
Deliberate repeat new-game actions in Public matchmaking inside the same tab session. Counted from accepted game_replay events whose mode is public_matchmaking. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
Active play time · Classic 7m 38sPartial measurement
Reported foreground play seconds while the active mode was Classic. Summed from the accepted 1–30 second active_time increments whose mode is classic. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
Active play time · Journey 0m 0sPartial measurement
Reported foreground play seconds while the active mode was Journey. Summed from the accepted 1–30 second active_time increments whose mode is journey. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
Active play time · Private room 0m 0sPartial measurement
Reported foreground play seconds while the active mode was Private room. Summed from the accepted 1–30 second active_time increments whose mode is private_room. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
Active play time · Public matchmaking 0m 0sPartial measurement
Reported foreground play seconds while the active mode was Public matchmaking. Summed from the accepted 1–30 second active_time increments whose mode is public_matchmaking. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
Reporting browsers —Not measured
Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.
Returning browsers —Not measured
Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.

What am I looking at?

A recorded launch into gameplay. Repeat play counts again. These are browser reports, not verified players.

The chart uses one measure and one unit at a time. Each coloured line belongs to a project; the source totals cover the selected window.

What does it tell us?

We can see when recorded activity occurred and inspect how it is distributed across the selected dates.

No clean growth comparison yet. New collection and legacy test traffic limit the history we can trust.

Last complete week

The most recent complete Monday–Sunday UTC week for each project's own headline measure, against the week before. A record needs exact daily history for two adjacent complete weeks; this is a valid comparison, not only the large movements that raise an operational alert.

No project has two complete comparable weeks yet, so no week-on-week figure is shown. Collection is too recent to compare honestly, and nothing is inferred from it.

Why some projects are not compared (1)
  • Protocol 11: Fewer than two complete comparable weeks so far.

If you’re assessing the business

Early product instrumentation, with material evidence gaps.

Usage
1/1 projects reporting this measure. 7/7 sources provide some activity. Reports are not verified people.
Retention
No portfolio cohort-retention evidence. Returning browsers, where available, are a narrower signal.
Commercial proof
Revenue, paying customers, acquisition cost and customer value are not measured here.

Use this to ask better product questions. It cannot establish product–market fit, market demand or an investment case.

Read the product dossiers

Report details

Snapshot
6156ac9381310a5e6b3e7170
Captured
2026-10-23 07:46:09 UTC
Dates
2026-09-24 – 2026-10-23
Time zone
UTC; dates may differ from your local day
Tracking, retention & privacy choices