CodeCow/stack
1
0
Fork 0
mirror of https://github.com/stack-auth/stack.git synced 2026-07-20 21:29:36 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

more clear wording around clickmaps

Browse Source
This commit is contained in:
Madison 2026-07-17 04:26:19 -05:00
parent 496b88eec6
commit 38897fbc54
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs-mintlify/guides/apps/analytics/overview.mdx
View File

@ -12,7 +12,7 @@ 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**: Visualize where users click across your pages
- **Clickmaps**: See which elements get clicks on your pages (element-tied, not coordinate heatmaps)
See [Replays & Clickmaps](./replays-and-clickmaps) for the full guide to session replays and clickmaps.
@ -99,7 +99,7 @@ export const hexclaveClientApp = new HexclaveClientApp({
tokenStore: "cookie", // use "nextjs-cookie" in Next.js
analytics: {
replays: {
// Enabled by default; set to false to opt out.
// Optional. Defaults to true when the Analytics app is enabled; set to false to opt out.
enabled: true,
// Optional. Defaults to true.
maskAllInputs: true,
@ -128,7 +128,8 @@ This stops the SDK from sending `$page-view` and `$click` events. If you'd rathe
## Best Practices
1. **Use Tables for quick incident triage**: the Tables UI is the fastest way to inspect recent `events` rows without writing SQL.
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. **Keep replay privacy defaults on**: leave `maskAllInputs` enabled unless you have a specific reason and a data-handling policy for unmasked inputs.
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](./replays-and-clickmaps).
5. **Keep replay privacy defaults on**: leave `maskAllInputs` enabled unless you have a specific reason and a data-handling policy for unmasked inputs.

2
docs-mintlify/guides/apps/analytics/replays-and-clickmaps.mdx
View File

@ -96,7 +96,7 @@ Recorded replay data is stored privately (the DOM recording is gzipped and kept
## Clickmaps
A clickmap overlays your live site with the **number of clicks each element received**, so you can see what users interact with - and spot "dead clicks" on things that look clickable but aren't. Click data comes from the same `$click` events the SDK already captures, so there's nothing extra to instrument.
A clickmap overlays your live site with the **number of clicks each element received**, so you can see what users interact with - and spot "dead clicks" on things that look clickable but aren't. Clicks are tied to DOM elements (not pixel coordinates): a marker appearing in the middle of an element does not mean the user clicked that exact point. Click data comes from the same `$click` events the SDK already captures, so there's nothing extra to instrument.
### Enabling