Obelism numbers

Web analytics every Obelism product shares. Visitors, pages, sources, campaigns, countries, devices, clicks and your own events, per site and environment.

1 min read

Obelism numbers counts what happens on your sites: who visits, which pages they read, where they came from, what they click and the events you send yourself. Obelism Improve's tests and Content's pages send their events to it, so a test result, a page's click rate and the dashboard all count the same visitors.

What it counts

  • Visitors, sessions and page views over time, with the bounce rate and the average session, against the range before.
  • Pages: the most viewed paths. Query strings never leave the browser.
  • Sources and campaigns: the referring site's host, and the UTM tags of the visit.
  • Countries, devices, browsers and operating systems.
  • Clicks on the elements you tag with data-numbers-id, with a click rate.
  • Events: everything a site sends, by name and scope.

How events get in

  1. The script: one <script> tag, no bundler. It sends page views, also on client-side navigations, and clicks on tagged elements.
  2. The SDK, @obelism/numbers-sdk: the same client as an npm package, for apps with a bundler and for your own events. The Improve SDK sends through it, so a site with Improve already sends to numbers.
  3. Your server: POST /api/log with an API token.

Where it lives

numbers works per Space (one site or project of your Organization) and environment (develop, staging or production), like Improve and Content. Every member of an Organization that may open a Space sees its numbers at numbers.obelism.studio/dashboard. Agents read the same reports through the MCP server.

On this page

Marks in the margin

  • Note
  • Watch out
  • Updated

Scribes marked doubtful lines in the margin. That practice is called obelism.

Stuck on a step?