Features
Numbers that sit next to the words.
Product analytics routed through your own infrastructure and shown beside the content it belongs to. No consent banner, no blocked pixel, no fourth tab to go and check.
Traffic, top pages and custom events, gathered through your own infrastructure and shown beside the content they describe.
How it works.
- Through your infrastructure
- Events post to a route in your own application and are enriched server-side before they reach Stet. An ad-blocker sees a first-party request to your own domain, because that is exactly what it is.
- No consent banner
- Cookieless by design. Nothing is stored on the reader device, so there is no interstitial between someone and the page you wrote for them.
- Attached to the content
- Content served through the client reports its own performance, so an entry has numbers from the moment its page exists, with no instrumentation written for it.
- Typed events
- Custom events are typed at the call site, so a renamed property is a compile error rather than a silent gap in a chart. Marketing builds on the same events in the UI.
- Tracking never throws
- Analytics failures are swallowed on purpose. A metrics outage is never allowed to become a customer-facing one.
Who this matters to.
The same feature, described from the side of the gap you happen to be standing on.
For marketing teams
Add the field, write the page, watch the numbers. No ticket.
For engineers
A typed client you did not write, that cannot break your build.
For publishers
A room full of writers, and one place the work happens.
For agencies
Hand over a CMS the client can extend without calling you.
For enterprises
Self-host it, with roles, permissions and an audit log.