Analytics

The Analytics page shows traffic and engagement for the World you currently have selected: page views, unique visitors, sessions, average session duration, bounce rate, custom events, plus top surfaces and top events. Switching worlds in the sidebar refreshes the view.

Where to find it

What’s measured

Metric	What it is
Page views	Total surface render events in the period.
Unique visitors	Distinct sessions over the period.
Sessions	Visit windows grouped by inactivity.
Avg. session duration	Time spent per session.
Bounce rate	Sessions that viewed only one surface.
Events tracked	Custom events you emit (e.g. `cta.click`, `form.submit`).
Top surfaces	Most-viewed surfaces in the period, ranked by views.
Top events	Most-fired custom event types, ranked by count.

Each headline metric is paired with a trend badge comparing the current period to the previous one of the same length.

Period filter

Use the dropdown next to the period label to switch between the last hour, the last 24 hours (the default), the last 7 days and the last 30 days. Aggregates are computed server-side, so a very recent event may take a moment to appear in the larger windows.

CSV export

Export CSV downloads the period’s events, one row per event, with the event type, timestamp, surface, session and the event’s own data.

Per-surface figures

The Analytics page reports World-wide totals. For a single surface, open that surface’s detail view — the same data, narrowed to one page.

Tracking your own events

Visitor traffic is tracked for you. To record something domain-specific — a form submission, a click on an upgrade CTA, a completed checkout — post the event yourself:

POST /api/analytics/events
Authorization: Bearer <your-token>
Content-Type: application/json
 
{
  "eventType": "checkout.completed",
  "surfaceId": "sf_abc123",
  "eventData": { "plan": "pro", "currency": "TRY" }
}

Event types are free-form strings; a domain.action convention keeps the Top events list readable.

Privacy

Event data is stored as you send it. Do not put email addresses, phone numbers or anything else personal into eventData — put an identifier you can resolve on your side instead.