Analytics
How GoClaw CRM is actually being used.
API requests by day
July, daily totals.
Where these numbers come from
| Metric | Key | Status |
|---|---|---|
| API requests | api.requests | Live |
| Database size | db.primary.gb · db.log.gb · db.ai.gb | Live |
| Active users | users.active.monthly | Runtime rollout |
| Session length | sessions.duration.avg | Runtime rollout |
| Bandwidth | bandwidth.egress.mb | Runtime rollout |
The vital signs of one product: how many people used it this month, how hard its API is being hit, how much data it moved, and how long people stay.
These numbers come from the same metering pipeline that feeds billing — so what you see here and what you’re charged for can never disagree. A couple of metrics are still rolling out from the product runtime; the source table shows exactly which.
Behind this page/apps/:saasAppId/analytics · ownership-validated
Retrieve
SaaSAppUsageTracking holds monthly period rows per metric key. The builder-plane reader is sp_Builder_GetAppUsage (period + keys, ownership-validated, up to 24 months of history). Writes go only through UpsertUsageMetering / SetUsageGauge (bwhq_metering) — never from the portal.Save
Read-only. Export produces a CSV of the visible period.Success
- Counters accumulate, gauges overwrite — rendering respects AggregationMethod.
- Values are BIGINT in bytes/MB; conversion happens at display.
- users.active.monthly / sessions.duration.avg / bandwidth.egress.mb are new keys published by the tenant runtime; api.requests and db gauges are live today.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.