WOODHOUSEThe Loftwah Software Factory

Find a project or subject.

15 pages in the index

Esc closes search ⌘ K or Ctrl K opens it

MoreMenu
Measurement & privacyGames × RadioExplore connected productsEdition discoveryExplore the projects

Analytics

Each project on its own relevant measure

Custom dates
UTC · max 90 days

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-09-24 to 2026-10-23 UTC · same saved report throughout · today is partial

    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.

    What we noticed

    1 finding 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.

    1. Woodhouse · its own audience

      3,896visits

      42 of those visits met the source's engaged-session threshold.

      24 Sept 2026–23 Oct 2026

      What this establishes
      3,896 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.
      Open Woodhouse analytics
    What this report cannot show yet
    • No two adjacent complete weeks are available in retained history for these dates.
    • No positive clicks through to a measured project were recorded in these dates.
    24 Sept 2026 – 23 Oct 2026 · 30 days · Today is partial1/1 projects report their measure · 1/1 sources reporting · Saved snapshot

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

    Project overview

    One relevant measure per project · same UTC dates

    Each project, on the measure that describes its use

    Woodhouse3,896VisitsPartial coverage

    Different measures with different units; the values are never added together. Open a project for its full view, or choose one measure for a single-scope chart and table.

    Daily values & export

    One row per project with its own relevant measure, unit and coverage. A dash means unavailable; the measures are not added together.

    Relevant measure per project · UTC dates
    ProjectMeasure2026-09-242026-09-252026-09-262026-09-272026-09-282026-09-292026-09-302026-10-012026-10-022026-10-032026-10-042026-10-052026-10-062026-10-072026-10-082026-10-092026-10-102026-10-112026-10-122026-10-132026-10-142026-10-152026-10-162026-10-172026-10-182026-10-192026-10-202026-10-212026-10-222026-10-23Total
    WoodhouseVisits—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing—missing4partial42clean20clean50clean118clean998clean526clean1,320clean818partial3,896count

    Can we compare these dates?

    Coverage for each project's relevant measure. Colour describes evidence, not popularity.

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

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

    Where Woodhouse sends visitors

    Recorded clicks from Woodhouse to a published project, for this period. A click is a referral: it shows discovery intent, not downstream play, adoption or a unique person.

    No measured product destinations are currently published.

    No published project with a site address is in the measured destination subset.

    Counts come from the same anonymous collection as Visits. Opt-out, blocked measurement and QA exclusion make them partial, and they do not show whether the visitor played, subscribed or came back.

    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.

    • WoodhouseNot measured for these dates

      DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill. Optional browser measurement has not yet received a consenting visit; browser counts are unavailable. Browser measures cover opt-in visits only and remain partial. Private project-scoped visit associations expire after 90 days; a window intersecting expired history is unavailable. Browser totals use retained period DISTINCT counts, never daily sums.

    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 2 dated release and collection notes
    1. Woodhouse · Collection began

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

    2. Woodhouse · 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.

    Woodhouse4 measures available

    Live aggregate endpoint · generated

    Collection began
    2026-10-15T00:00:00.000Z
    Comparable history from
    2026-10-15T00: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.
    • Optional browser measurement has not yet received a consenting visit; browser counts are unavailable.
    • Browser measures cover opt-in visits only and remain partial. Private project-scoped visit associations expire after 90 days; a window intersecting expired history is unavailable. Browser totals use retained period DISTINCT counts, never daily sums.
    Visits 3,896Reported 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 42Reported activity
    One accepted marker per tab session after at least 10 seconds of active product use. Foreground, unpaused and recent trusted input required.
    Active time 42m 44sReported 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.
    Project discoveries 18Reported activity
    Accepted deliberate clicks from Woodhouse to a published project destination. Counts clicks, not visits received by that project.
    Reporting browsers —Not measured
    Distinct optionally consenting, project-scoped browser tokens with accepted visits in the selected UTC window. Period DISTINCT, not a sum of daily browser counts. Tokens rotate after 90 days; resets, multiple devices and privacy choices prevent interpreting these as people.
    Returning browsers —Not measured
    Distinct optionally consenting browser tokens with a visit in this UTC window and an earlier different accepted tab session in retained 90-day history, including same-day returns. Period DISTINCT, not a sum of daily returns. This is not cohort retention; expired earlier visits and token rotation hide returns.

    What am I looking at?

    Each admitted project opens on the measure that describes its own use: gameplay for the games, listening for LoftwahFM, app access and outcomes for App Composer and audience discovery for Woodhouse. The measures have different units and are never added together. Choose a measure for a single-scope drill-down.

    One row and one card per project, each on the measure its product view defines. The games, LoftwahFM, App Composer and Woodhouse report different units; the overview keeps them side by side without adding them together.

    What does it tell us?

    1 of 1 projects report their own measure for these dates. A project that reports nothing keeps its measure named and shows no value rather than a zero.

    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)
    • Woodhouse: 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 report their own measure. 1/1 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
    78533b3457ba704d348cfc21
    Captured
    2026-10-23 04:50:18 UTC
    Dates
    2026-09-24 – 2026-10-23
    Time zone
    UTC; dates may differ from your local day
    Tracking, retention & privacy choices