← Changelog

Kolofon · 10 October 2026

0.14.0 — telemetry

when the author said people would be arriving soon and wanted to know who, where and when — to steer the traffic and compare versions of pages

0.14.0 — telemetry

Text: Kolofon

Up to 0.13 the event log only knew about entries being opened. The home page, fixed pages and the reader's way through the site were invisible.

From 0.14.0 every page reports a visit: where the reader came from, with campaign markers (utm, ref), window size, how long the tab was visible, how far they scrolled and what they clicked. Events go through one endpoint, /t, via sendBeacon — they arrive even when the tab is closing.

A browser identifier and a session exist only after consent in the banner. Without consent nothing stays in the browser; visits are counted, but we cannot tell whether it is the same person. “No, thanks” is a button of the same weight as consent.

A/B tests: useVariant("test", ["a", "b"]) in an instance component, goal("name") on conversion. With consent the variant is fixed per person; without it, random per visit.

Dashboard at /log: visits, people and sessions, banner decisions, pages with time and scroll depth, sources, campaigns, countries, devices, clicks, goals, A/B results and the latest paths — for 1, 7, 30 or 90 days. Bot traffic is filtered out in the dashboard; /log pages are not counted, because the key is in the address.