Website measurement
This page is about the keepstate.ai website, not the product: what the site records about its visitors, and what it does not.
No trackers, analytics cookies or third-party measurement scripts. Measurement is first-party and server-side only: what the durable form rows record, and the five standard UTM keys (utm_source, utm_medium, utm_campaign, utm_term, utm_content) read on the server from the address the visitor already sent. Signing in to request supporting documents uses a necessary session cookie. Missing data renders unavailable, never zero.
| event | definition | state | collector / reason |
|---|---|---|---|
| preview_join_receipt | A durable waitlist row written with its receipt id. · privacy: form data the user submitted plus build metadata; no cookie, no tracker Campaign parameters are read server-side from what the visitor already sent; no cookie, no tracker, no cross-site identifier (F-12). | Evidence:observed measurement | server-side: the leads table row itself |
| trace_apply_receipt | A durable design-partner application row with its receipt id. · privacy: form data plus build metadata Campaign parameters are read server-side from what the visitor already sent; no cookie, no tracker, no cross-site identifier (F-12). | Evidence:observed measurement | server-side: the leads table row itself |
| data_room_request_receipt | A durable data-room request row. · privacy: form data plus build metadata Campaign parameters are read server-side from what the visitor already sent; no cookie, no tracker, no cross-site identifier (F-12). | Evidence:observed measurement | server-side |
| page_view | A page render. | Evidence:unavailable | not collected: the no-analytics law (no trackers, no cookies) stands until it is amended in writing |
| demo_watch_started | The demo page's transcript entered the viewport. | Evidence:unavailable | not collected: no-analytics law |
| demo_watch_completed | The transcript was read to its end. | Evidence:unavailable | not collected: no-analytics law |
| preview_join_started | The join form received focus. | Evidence:unavailable | not collected: no-analytics law |
| trace_apply_started | The apply form received focus. | Evidence:unavailable | not collected: no-analytics law |
| signup_activated | A self-serve signup reached a running first session. | Evidence:unavailable | not collected: no-analytics law; the control plane's own ledger is the record |
| client_verified | A thin-client checksum was verified on install. | Evidence:unavailable | not instrumented yet; the released client verifies its checksum on every install path and refuses a tampered mirror (the public client gate), the counter does not exist |
| login_completed | A device-code login completed. | Evidence:unavailable | not instrumented yet; the hosted login runs, the counter does not |
| workspace_sync_confirmed | The files a user chose to send were confirmed. | Evidence:unavailable | not instrumented yet; workspace upload runs, the confirmation counter does not |
| remote_session_started | A hosted session started. | Evidence:unavailable | not instrumented yet; hosted sessions run on the deployed control plane, the start counter does not |
| reconnect_completed | A dropped connection re-established on the same session. | Evidence:unavailable | not instrumented yet; the attach relay reaches a running hosted session, the re-establishment counter does not |
| ledger_viewed | A session ledger was read by its owner. | Evidence:unavailable | not instrumented yet; the console renders the event trail and the credits ledger, the read counter does not |
| feedback_submitted | Cohort feedback landed durably. | Evidence:unavailable | no cohort has opened |
This page covers website analytics and nothing else. A number that describes how the product behaved under a gate is a different kind of measurement, and it belongs to one of the three families set out on the methodology page: bench, production canary, or customer trial. An event reading unavailable here says only that its counter does not exist. It says nothing about whether the underlying capability is proven, which is what the availability matrix answers.
Attribution on the durable lead row: src (surface),
cta (intent), landing (first path this
browser tab saw, kept by the form page in the tab's own session storage,
no cookie), and build (site commit). Nothing follows a
visitor across sites.