Which page produced the pilot?

This site is built so we can answer that without an advertising pixel. The numbers live in our own logs, an optional webhook, and an optional key-value store. They are not shown on this page.

What we collect without a cookie

Every page view sends the path only. No session id, nothing stored on your device. That is how we know a URL was read even when most visitors decline analytics. The cookie policy says the same thing.

If you click through to the app, we also send the click type (pilot, trial, demo or sign-in), the page you were on, and a one-shot click id in the URL as sv_cid. Still no session id unless you clicked Accept. The app can store that click id on the organisation at signup.

What Accept adds

After Accept, a first-party session id is stored in local storage so we can see how a visit moved through the site. UTM tags are kept with that session and copied onto app links. We do not use advertising cookies. Declining analytics does not stop the site or the cookieless counts.

How a founder reads it

Events POST to /api/track. If ANALYTICS_WEBHOOK_URL is set, each event is forwarded there. Conversion events are also written as ATTRIB lines in the Vercel function log, which you can filter by path.

If Vercel KV is configured, the same events increment a daily per-page counter. A private GET to /api/attribution?days=30 with Authorization: Bearer $ANALYTICS_READ_TOKEN returns pages ranked by pilot_cta_clicked. Without KV, the API tells you so, and the log lines remain the source.

This public page does not display those counts. A token in the browser would become a public token.

Related: Cookie policy · Privacy · Help centre