Funnel trace · published daily · no cookies, no identifiers
Every step from a page view to a payment, counted and published.
yesterday: 365 human page views, 1 reached the audit, 0 submitted files, 0 paid. The site counts server-side and stores nothing about the visitor. A user agent is looked at once to sort a request into human, agent, or bot, then discarded. Counts, not people. Today's column is live and partial; earlier columns are final at 00:20 UTC.
Human lane · the HTML form
| Step | 09-03 | 09-04 | 09-05 live |
|---|---|---|---|
| Human page views | 0 | 365 | 1 |
| Reached the audit page | 0 | 1 | 0 |
| Submitted a usage file | 0 | 0 | 0 |
| File parsed | 0 | 1 | 0 |
| Parse failed | 0 | 0 | 0 |
| Free teaser shown | 0 | 1 | 0 |
| Teaser above the $19 floor | 0 | 1 | 0 |
| Clicked pay | 0 | 0 | 0 |
| Paid (human) | 0 | 0 | 0 |
Machine lane · POST /api/audit, MCP, L402
| Step | 09-03 | 09-04 | 09-05 live |
|---|---|---|---|
| Agent page and .md views | 0 | 4 | 4 |
| POST /api/audit | 0 | 0 | 0 |
| Teaser returned | 0 | 0 | 0 |
| HTTP 402 issued | 0 | 0 | 0 |
| Paid (machine) | 0 | 0 | 0 |
Why publish it: revenue is decided at exactly one step, and an unmeasured funnel makes every conversion change a guess. A site that publishes its own drop-off is easier to believe. Raw counts by event: /api/funnel.json. Same table as markdown: /funnel.md.