Fighter analytics
Play & engagement
This report is frozen at 2026-10-16 17:04 UTC. Refresh these dates · Latest 30 days
Returning browsers · Fighter
Count per UTC day · gaps mean unavailable
Distinct consenting browser identifiers observed in this window with an earlier different tab session in retained history. Same-day returns may count. This is not cohort retention.
- Game starts
- 0 Legacy/test risk
- Game completions
- 0 Legacy/test risk
- Active play time
- 0m 0s Legacy/test risk
- Returning browsers
- 0 Legacy/test risk
Inspect a date to see source values. The data table below works without interactive charts.
Chart data & export
These are daily values for returning browsers. A dash means unavailable. Daily distinct-browser counts must not be added to estimate period-level people.
| Date | Fighter |
|---|---|
| 2026-10-10 | —missing |
| 2026-10-11 | —missing |
| 2026-10-12 | —missing |
| 2026-10-13 | —missing |
| 2026-10-14 | —missing |
| 2026-10-15 | 0legacy |
| 2026-10-16 | 0partial |
Can we compare these dates?
Coverage for the selected measure. Colour describes evidence, not popularity.
No clean full-day comparison is available for this selection in this snapshot. First collection days and today remain partial. Legacy activity may include tests that cannot be separated.
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.
Fighter0 returning · 0 reporting browsers
Distinct opted-in browser IDs observed in this window with an earlier different tab session in retained 90-day history (including same-day returns). Daily distincts are not additive; period totals are unavailable when the raw retention window is incomplete. Clearing/rotating IDs resets continuity; default tab-only visits are outside this cohort.
No opted-in browser was observed in this window. This zero cannot show whether the wider audience returned.
Inspect Fighter returns
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 saved report has no frozen release notes. Its source collection dates remain available below; later notes are never added to an old snapshot.
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 2 dated release and collection notes
- Fighter · 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.
- Fighter · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
Follow the numbers to their source
Every measure has a definition, a collection boundary and blind spots.
Fighter8 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-08-09T08:22:36.602Z
- Comparable history from
- 2026-10-15T12:02:59.539Z
- Source revision
- Not supplied
- Historical counts before 15 October 2026 include unmarked production QA that cannot be separated or subtracted. These are stored reports, not a clean audience cohort; exclude pre-comparableFrom history from growth comparisons and records.
- Requested windows may include partial coverage. Current UTC day is partial. Stored browser reports are subject to privacy opt-outs, network loss and abuse controls; they are not unique people.
- Launch/completion counters backfilled only from the raw rows retained at migration; earlier expired history is unavailable. Anonymous daily totals are retained durably thereafter.
- Visits, engagement, deliberate Quick Fight replay and optional browser cohort measurement start 2026-10-15T14:34:02.048Z; earlier values are unavailable. Browser cohort rows and raw tab sessions expire after 90 days; anonymous daily counters remain durable.
- Active-time collection starts 2026-10-15T12:02:46.571Z; earlier time is unavailable. Individual raw game and session facts still expire after 90 days.
- Fight starts 0Reported activity
- Browser-reported non-tutorial fight launches; match IDs deduplicate retries. Exact accepted events, not verified humans.
- Completed fights 0Reported activity
- Launched fights ending in win, loss, draw or forfeit, attributed to launch UTC day. Abandonment excluded; not a completion cohort rate.
- Active gameplay 0m 0sReported activity
- Cumulative foreground, focused, unpaused fight seconds with input in the preceding 60 seconds. Loading/countdowns, hidden tabs, idle and radio excluded. Browser-reported, bounded by server elapsed time; launch UTC day attribution.
- Tab visits 0Reported activity
- Accepted random tab sessions first observed since this metric began; one per tab session (including reloads), attributed to first observation UTC day, with raw tab deduplication retained for 90 days. DNT/GPC, automation and explicit QA excluded. Not pageviews or people.
- Engaged tabs 0Reported activity
- Tab sessions reaching at least 10 cumulative measured active gameplay seconds across fights. Attributed to the tab visit UTC day; at most once per retained tab. Menus, radio, pause, background and idle time excluded.
- Deliberate Quick Fight replays 0Reported activity
- Accepted deliberate Quick Fight launches after an earlier completed or explicitly abandoned fight in the same tab. Prior terminal match ownership is checked by the server; retries deduplicate. Automatic progression, tutorial and other-mode replay actions are outside this measure.
- Opted-in browsers 0Reported activity
- Distinct random browser IDs voluntarily enabled in Settings and observed in this window; never humans. Off by default; expires/rotates after 90 days. Daily distincts are not additive; period totals use distinct retained IDs, not their sum.
- Returning opted-in browsers 0Reported activity
- Distinct opted-in browser IDs observed in this window with an earlier different tab session in retained 90-day history (including same-day returns). Daily distincts are not additive; period totals are unavailable when the raw retention window is incomplete. Clearing/rotating IDs resets continuity; default tab-only visits are outside this cohort.
What am I looking at?
Distinct consenting browser identifiers observed in this window with an earlier different tab session in retained history. Same-day returns may count. This is not cohort retention.
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)
- Fighter: 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
- e46cf76b46e20163e97c400a
- Captured
- 2026-10-16 17:04:40 UTC
- Dates
- 2026-10-10 – 2026-10-16
- Time zone
- UTC; dates may differ from your local day