Observability for behaviour.
Structured JSON logging for flows, dropoffs, and UX insight -- no dashboards required.
Clientlog is for developer-founders, engineers, and technical teams who see product friction as a runtime bug, not a marketing problem.
No SDKs. No tracking pixels. Just structured JSON events and workflows.
We don't store IP addresses or other personal identifiers by default -- session and event data is used to measure behaviour, not individuals. If you extend the client library to attach your own user identifiers, that's your data and your responsibility for the consent it requires.
Add a script tag to your frontend. It automatically captures structured events like clicks, navigation, and scrolls. Events are posted via POST /event to our API.
<script src="https://clientlog.bayis.co.uk/clientlog.js"></script>
<script>
const logger = clientlog.createLogger({
endpoint: "https://api.dev.clientlog.bayis.co.uk/v1/event",
project: "myproject/home",
options: { session: true, clicks: true, navigation: true }
});
</script>
Once your account is set up, you can access your raw and enriched events using the API. Raw events include payload, timestamp, and action; enriched events add geo and user-agent metadata -- never raw IP addresses, which are discarded at enrichment.
GET /events raw event streamGET /events/enriched ...with metadataGET /sessions/ latest sessionsWrite rules that tag sessions based on the events they contain -- conversions, drop-offs, bot traffic, whatever matters to your product. Rules run as events arrive, so classification is near-instant, not batched.
Set webhooks to fire when particular events happen. Spike in bot traffic? Increase in drop-off rate? A specific action you care about? All possible from triggered insight into your users' journeys.
Use our funnel simulator to test these journeys, observations, and triggers before investing real traffic.
Get early access and help shape the project. We'll only email you with relevant updates.
or
No spam. Unsubscribe anytime.