Bubbles analytics
Play & engagement
This report is frozen at 2026-10-17 19:07 UTC. Refresh these dates · Latest 30 days
Returning browsers · Bubbles
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 Partial coverage
- Game completions
- 0 Partial coverage
- Active play time
- 0m 0s Partial coverage
- Returning browsers
- 0 Partial coverage
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 | Bubbles |
|---|---|
| 2026-10-11 | —missing |
| 2026-10-12 | —missing |
| 2026-10-13 | —missing |
| 2026-10-14 | —missing |
| 2026-10-15 | 0partial |
| 2026-10-16 | 0clean |
| 2026-10-17 | 0partial |
Can we compare these dates?
Coverage for the selected measure. Colour describes evidence, not popularity.
The longest available comparable history in this selection is 1 complete daily observations. 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.
Bubbles0 returning · 0 reporting browsers
Opted-in browser IDs with a gameplay start in this window and an earlier different tab session in the retained 90-day run history. Same-tab replays excluded. Not human or installation retention; daily counts do not sum to period distinct counts.
No opted-in browser was observed in this window. This zero cannot show whether the wider audience returned.
Inspect Bubbles 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
- Bubbles · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
- Bubbles · 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.
Follow the numbers to their source
Every measure has a definition, a collection boundary and blind spots.
Bubbles6 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-15T11:33:11.547Z
- Comparable history from
- 2026-10-15T11:33:11.547Z
- Source revision
- Not supplied
- Current UTC day is partial. Stored browser reports are subject to privacy opt-outs, network loss and abuse controls; they are not unique people.
- Collection is opt-in and starts at this deployment. No historical gameplay is imported or invented. Anonymous daily totals are retained durably; pseudonymous run facts expire after 90 days.
- Active-time collection starts 2026-10-15T11:33:11.547Z; earlier time is unavailable. Raw gameplay run facts expire after 90 days.
- Gameplay starts 0Reported activity
- Opted-in gameplay starts at the first accepted shot/turn, or Snake start. Route visits and unplayed boards excluded. Random run IDs deduplicate retries; not unique humans.
- Completed games 0Reported activity
- Started runs reaching their actual game terminal result, attributed to launch UTC day. Quits and restarts excluded; not a completion cohort rate.
- Active gameplay 0m 0sReported activity
- Cumulative foreground, focused, unpaused gameplay 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.
- Opted-in browsers 0Reported activity
- Distinct random opted-in browser IDs with a received gameplay start in the selected window. Browser reports, not humans; daily counts are distinct per day and do not sum to the period total.
- Returning opted-in browsers 0Reported activity
- Opted-in browser IDs with a gameplay start in this window and an earlier different tab session in the retained 90-day run history. Same-tab replays excluded. Not human or installation retention; daily counts do not sum to period distinct counts.
- Engaged opted-in tab sessions 0Reported activity
- Distinct opted-in tab-session IDs receiving at least 10 active seconds across runs started in the selected window. Daily thresholds apply separately to runs started each UTC day; daily counts need not sum to the period distinct count.
- Visits —Not measured
- Only opted-in gameplay is collected. Page visits and acquisition are not collected.
- Deliberate replays —Not measured
- A distinct replay action is not yet recorded; multiple starts are not assumed to be replays.
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)
- Bubbles: 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
- 190bc6bbf72b6655f991bc13
- Captured
- 2026-10-17 19:07:48 UTC
- Dates
- 2026-10-11 – 2026-10-17
- Time zone
- UTC; dates may differ from your local day