Flows

The journey says what should happen. Flows (/workspace/<slug>/flows, under Current status in the sidebar) shows what did: a map of your product's pages, connected by the paths real users took, built from events your app sends to Skene. One script tag, and the map draws itself.

Install tracking

Flows is fed by the Observe script: a small, dependency-free tag that captures interactions in the browser and batches them to Skene.

1. Open Flows and click Install tracking.
2. Click Generate Key (workspace owners only). This creates a publishable key with the sk-pub- prefix.
3. Copy the snippet into your app (the modal also has a Next.js variant using next/script):

<script
  src="https://www.skene.ai/observe.js"
  data-key="sk-pub-..."
  data-endpoint="https://www.skene.ai/api/v1/cloud/ingest/interaction"
  defer
></script>

A public key in your HTML? That's the point. Publishable keys are write-only: they can only send events to the ingest endpoint, so they're safe to embed in client-side code. Your sk-upstream- secret keys are not; keep those out of the browser. You can also create a publishable key from the API keys page: pick the Publishable key type.

What the script captures

Clicks, page navigations, form submits, and rage clicks (a burst of fast clicks on the same spot). Events are batched in the browser and sent to the public ingest endpoint (POST /api/v1/cloud/ingest/interaction).

The flow map

Nodes are your pages, built from real navigation events. Edges are the moves users made between them within a session, weighted by traffic (the Traffic legend shows the scale). Each edge label also carries the median time sessions took to make that move.

• Date range: defaults to Last 7 days, with presets from Today up to Last 90 days.
• Display: hide edges whose traffic falls outside a range you set (pages left with no visible edges disappear too), and toggle the conversion percentage badge on each edge. Reset filters puts everything back.

Page details

Click a node to open its panel:

• Total events, Visitors, and Avg time for that page. Visitors counts distinct sessions that reached the page, so it works without identifying anyone. Avg time is how long a session stayed before its next navigation.
• Click Heatmap: where on the page people actually click, with the top click targets ranked.
• Exit Points: where sessions leave from this page, with percentages.

Retention and reset

Event data is kept for 90 days, then purged automatically. Until events arrive, the page shows an empty state pointing you to Install tracking.

Reset Data (workspace owners only) permanently deletes every captured event and session for the workspace. There's no undo.

Next steps

• Events: the code and database events your journey expects
• Workspace: API keys: key types and how they're scoped