Skip to main content
The Analytics app gives you direct access to your project’s analytics dataset in Hexclave. You can inspect raw event tables, run ClickHouse SQL queries, and watch session replays to debug real user behavior.

​
Overview

Analytics is organized into four areas in the dashboard:
  • Tables: Browse rows across tables (events, users, contact channels, and more) with sorting, search, and incremental loading
  • Queries: Run and save reusable ClickHouse SQL queries
  • Replays: Watch session replays and filter by user, team, duration, activity window, and click count
  • Clickmaps: See which elements get clicks on your pages
See Replays & Clickmaps for the full guide to session replays and clickmaps.

​
How Analytics Works

Hexclave records analytics events and replay chunks, then exposes them through the Analytics app for read-only querying and investigation. User activity in your app flows into Hexclave event ingestion, which stores data in ClickHouse. This data powers the Tables view, the SQL query runner, and the Session replay UI. Analytics isn’t only client events. Hexclave also exposes product data from the rest of your project — users, contact channels, teams, permissions, email outbox, and more — in the same read-only ClickHouse dataset, so you can join product state with behavior in one place. See Queries & Tables for the full table list.

​
What Gets Tracked

Hexclave collects both client-side and server-side analytics events:
  • Client-side events: browser interaction events like $page-view and $click
  • Server-side events: currently $token-refresh and $sign-up-rule-trigger

​
Enabling the Analytics App

To use analytics in your project:
  1. Open your Hexclave dashboard
  2. Go to Apps
  3. Open Analytics
  4. Click Enable

​
Quick Start

  1. Enable Analytics in your Hexclave dashboard (Apps -> Analytics)
  2. Initialize Hexclave on your frontend with HexclaveClientApp/HexclaveProvider and a persistent tokenStore (e.g. "cookie", or "nextjs-cookie" in Next.js)
  3. Sign in with a real user session
  4. Open the app and navigate/click around
  5. Check Analytics -> Tables to confirm events are arriving
SDK analytics capture and session replay recording are on by default once the Analytics app is enabled — you do not need to set analytics.enabled or analytics.replays.enabled unless you want to opt out (pass analytics: { enabled: false } or analytics: { replays: { enabled: false } }). After setup, Hexclave automatically captures client-side $page-view and $click events. See Replays & Clickmaps to tune replay privacy or opt out.

​
Tables

The Tables screen is the fastest way to inspect recent analytics records.
  • Opens on events by default; pick other tables from the sidebar
  • Built-in ordering and client-side search
  • Relative/absolute timestamp display toggle
  • Row detail dialog for inspecting full JSON payloads
Use this view when you need to quickly answer “what just happened?” without writing SQL.

​
Queries

The Queries screen is a ClickHouse SQL workspace for deeper analysis.
  • Run read-only SQL queries with a timeout budget
  • Query the users and analytics tables
  • Save reusable queries into folders
  • Re-run saved queries with one click
  • Edit and overwrite saved query definitions

​
Session Replays

The Replays screen helps you move from “an event happened” to “what the user actually saw.”
  • Filter sessions by user, team, duration, recency, and click count
  • Play back multi-tab sessions
  • Control playback speed
  • Optionally skip inactive ranges
  • Jump across click/page-view timeline markers
Use replays when metrics alone are not enough to explain user behavior.

​
Replay recording in the SDK

Session replay recording is enabled by default once Analytics is on and your client app uses a persistent token store. You can tune privacy or opt out via the analytics.replays options:
maskAllInputs defaults to true, so form fields are masked unless you explicitly disable it. For the full set of privacy controls, playback, and clickmaps, see Replays & Clickmaps.

​
Disabling Analytics Capture in the SDK

SDK-managed analytics capture is enabled by default. You can disable it by disabling the Analytics app in the config or dashboard. If you don’t want the SDK to collect any analytics data at all but would like to keep the Analytics app enabled, you can also pass analytics: { enabled: false } when creating your client app:
This stops the SDK from sending $page-view and $click events. If you’d rather keep analytics, enable the Analytics app in your dashboard (Apps -> Analytics) instead.

​
Best Practices

  1. Use Tables for quick incident triage: the Tables UI is the fastest way to inspect recent rows (events, users, and more) without writing SQL.
  2. Use Queries for repeatable analysis: save important SQL in folders, and scope queries with filters/LIMIT so they stay within result and timeout limits.
  3. Use Replays for behavioral debugging: start from an event pattern, then inspect matching session replays to understand what users actually did.
  4. Use Clickmaps for UI friction and attention: overlay click counts on your live pages to see whether a flow takes unnecessary clicks, whether a control looks interactable, or how variants compare in an A/B test. Clicks are tied to DOM elements (not pixel coordinates), so a marker in the middle of a button does not mean the user clicked the middle of that button. See Replays & Clickmaps.
  5. Keep replay privacy defaults on: leave maskAllInputs enabled unless you have a specific reason and a data-handling policy for unmasked inputs.