Analytics
Analytics collects Visits and product Events and derives every Metric from them, split by Version.
Agent traffic counts the same as human traffic.
Contract
A Visitor is an unnamed id scoped to one Startup. A Visit is one span of a Visitor's Events across the Startup's Sites and Apps. When a Visitor becomes a Lead or a Customer, earlier Visits join that record.
| Rule | Detail |
|---|---|
| Declared Events only | Only declared Event names feed Metrics; a typo in a tracking call creates no phantom Metric |
| Derived, never typed | A Metric has a definition, window, population and source, and recomputes from Events |
| Revenue from the ledger | Revenue Metrics read ledger Entries, so they agree with the books to the cent |
| Outside revenue apart | Revenue from sibling Startups is reported separately from outside Customers |
| Variant on every Event | Every Event carries its Version and Flag variant, so any Metric splits after the fact |
| Consent by region | A Visitor without Consent is counted in aggregate and never profiled |
| Agent buyers | An MCP call or API request from an Agent is an Event like a page view |
The Product analytics System builds funnels and cohorts on this capability.
Verbs
| Verb | Object | Event |
|---|---|---|
| Visit.list | Visit | None. |
| Metric.get | Metric | None. |
Interfaces
Example
streakly.app, a habit-tracking App, defines activation as a first check-in within seven days of Order.paid. Activation drops from 61 to 44 percent after Version 12. Split by Version, the drop traces to a new onboarding screen, and the Startup reverts it.