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

change wording around user sessions for replays and clickmaps

Browse Source
This commit is contained in:
Madison 2026-07-17 04:34:12 -05:00
parent 3e90315712
commit e16dd0a73c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -14,8 +14,8 @@ Beyond raw events and SQL, Analytics ships two visual debugging tools: **Session
Replays and clickmaps both depend on the SDK's analytics capture, which runs when **all** of the following are true:
1. The **Analytics** app is enabled in your dashboard (**Apps -> Analytics**). The Session Replays and Clickmaps sub-apps inherit this - you don't enable them separately.
2. Your client app uses a **persistent `tokenStore`** (e.g. `"cookie"`, or `"nextjs-cookie"` in Next.js).
3. The visitor has an **authenticated session**. Capture is tied to the user's session, so anonymous traffic isn't recorded.
2. Your client app uses a **persistent `tokenStore`** (e.g. `"cookie"`, or `"nextjs-cookie"` in Next.js). Without one, the SDK does not start capture.
3. The visitor has a Hexclave **session with a refresh token** (a signed-in user, or an anonymous session created by the SDK). If there is no refresh token, the client may still attempt to send events, but the server will reject them and nothing is stored.
When those hold, the SDK captures `$page-view` and `$click` events and (for replays) records the session - no manual setup required.