Know more

Clientlog tells you what actually happened on your own site, measured on your own terms.

User journeys are runtime flows. They can be debugged.
Events are structured records, with a vocabulary you choose.
Sessions are the primitive. There is no user to track.

Facebook pixel conversion and a Google Analytics goal cannot be reconciled. They count different things, at different moments, under different definitions. Clientlog measures both from first principles and views product friction as a runtime bug, not a marketing problem.

How it works

1. One script tag

Add the client to your site. Page views, clicks, scroll depth and navigation are captured without further work. Custom events are a single function call.

2. Events become sessions

Every event is enriched with browser, device and coarse location, then aggregated into a session carrying the full action sequence with timings.

3. Rules classify sessions

Your rules are JSONLogic expressions in a YAML file. A matched rule writes a tag. Tags become segments you can count, filter and be notified about.

4. Digests and data

A weekly email with referrers, landing pages, tag distribution and journey structure. The same data through the API, the CLI, or the dashboard.

Rules as code

Your session classification lives in a YAML file in your repository, reviewed like any other change. plan shows drift against what is deployed. apply reconciles it.

- rule_id: pricing_visitor
  tag: pricing
  notification_target: email
  requires_events: true
  description: Visited pricing, the clearest purchase intent signal
  logic:
    some:
      - var: events
      - "==": [{var: payload.path}, "/pricing.html"]

No other analytics tool asks you to version-control your definition of a conversion. Every other tool asks you to click one together in a form and hope you remember why.

Rules documentation

Privacy

Clientlog sets no cookies, performs no fingerprinting, and builds no profile across sites. Session identifiers are generated in the browser and scoped to one site. IP addresses derive a coarse location and are then discarded.

Your data reaches an advertising platform only when you configure a conversion relay and nominate the destination. It is off by default.

Event payloads are whatever your site sends. Personal data in an event payload is your responsibility, and the documentation recommends against it.

Privacy and data handling

Flow overview

Founding projects

GBP 150 per project per month. A limited number of places, price held for twelve months.

See pricing