Reports that build themselves
When a project starts sending events the standard taxonomy recognises, the matching reports are created and published with real numbers already in them. Nothing to configure first.
The taxonomy is the contract
Events carry names like commerce.order.created or users.signup.completed. When a project starts sending names the standard taxonomy recognises, the reports for that family are created and published, with the numbers already in them. There is no template gallery to browse and nothing to pick before you see anything.
Created once, then yours
An automatic report is a starting point, not a fixture. Open it in the builder and change what it counts, add blocks, or throw half of it away. Once you have edited it, it stops being managed for you, because a report that rewrites itself under an author is worse than no report.
Nothing appears from nothing
A report is only created when there is data for it. An empty dashboard of placeholder charts teaches people the product does not work, and it is the first thing most tools show you.
Honest about what it does not know
A comparison against a period with no data says so rather than inventing a percentage. This is how dashboards end up claiming a four thousand percent rise, and it is always because yesterday was zero.
Send one event and watch
The onboarding screen waits for your first event and tells you the moment it lands. If it is an order or a signup, a report is already being built for it.
Start free