Measurement & privacy Games × Radio Explore connected products Edition discovery Explore the projects

Bubbles analytics

Play & engagement

12 Oct 2026 – 18 Oct 2026 · 7 days · Closed calendar dates1/1 reporting projects for this measure · 7/7 sources reporting · Saved snapshot

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

Game starts · Bubbles

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: 0
Game completions: 0
Active play time: 0m 0s

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
Date	Bubbles
2026-10-12	—missing
2026-10-13	—missing
2026-10-14	—missing
2026-10-15	0partial
2026-10-16	0clean
2026-10-17	0clean
2026-10-18	0clean

Can we compare these dates?

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

Comparable full dayPartial dayLegacy / test riskBounded / sampledNot measured

12 Oct 202618 Oct 2026

Bubbles

The longest available comparable history in this selection is 3 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 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 7 dated release and collection notes

2026-10-17
Bubbles · A game release checks what it publishes
The independently deployed game passed its normal release, exact candidate asset checks and deployed browser smoke. Safe negative probes returned six clean missing responses and three generic HTML fallbacks; actual output inspection supplies the artifact coverage. Generic HTML fallbacks are neither exposure nor proof of safety. Provider preview URLs remain disabled, so no addressable Bubbles preview is claimed tested. This guard release does not complete the broader gameplay qualification programme.
Read release evidence · reviewed 2026-10-18
2026-10-16
Bubbles · Opt-in reporting and consent revocation released
Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. The receipt-only main merge is separate from the deployed runtime revision. Later exact verification followed an initial propagation-related smoke failure. Owner-preview and scoped browser proof do not complete formal qualification or physical acceptance.
Read release evidence · reviewed 2026-10-16
2026-10-15
Bubbles · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
2026-10-15
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.
2026-10-12
Bubbles · bubbles · native result sharing
The later runtime carries the reviewed SDK 1.2 attribution implementation and native Classic sharing. Its owner-preview receipt covers sharing, player clearance and the unchanged service-worker bytes; earlier full audio proof remains separate. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. Owner-preview and scoped Chromium/WebKit receipts do not complete formal qualification. Classic export is not a verified uploaded score, a public result permalink or sharing for every mode. Prior full audio proof and later sharing/clearance proof are distinct.
Read release evidence · reviewed 2026-10-13
2026-10-12
Bubbles · bubbles · radio 1.2.0 release
The dedicated SDK 1.2 runtime receipt records exact deployment, native player/audio/attribution Chromium/WebKit journeys and explicit test/privacy exclusions. Later sharing and player-clearance proof stays separate. Dedicated owner-preview audio/attribution proof on this exact source. The later sharing release is not substituted for full playback verification. Formal qualification, held editorial/shared mix, real audience, physical device and human listening remain open.
Read release evidence · reviewed 2026-10-13
2026-10-10
Bubbles · bubbles · exact radio deployment
A stable, recoverable music dock exposes FM music, Original and Off, with saved controls and quiet reload. Presenter shows are discoverable through FM links while native editorial playback remains held. Owner-preview browser evidence does not complete formal qualification or physical iPhone/human listening. Native editorial remains held and shared continuous shuffle depends on FM #244.
Read release evidence · reviewed 2026-10-11

Follow the numbers to their source

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

Bubbles6 measures available

Live aggregate endpoint · generated 2026-10-23T03:09:27.411Z

Collection began: 2026-10-15T11:33:11.547Z
Comparable history from: 2026-10-15T11:33:11.547Z
Source revision: Not supplied

Selected UTC days are closed; this does not guarantee collection coverage. 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?

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)

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: 8496128e32ddfd0bddf8da66
Captured: 2026-10-23 03:09:27 UTC
Dates: 2026-10-12 – 2026-10-18
Time zone: UTC; dates may differ from your local day

Tracking, retention & privacy choices