From e16dd0a73c883816b0412f3570e25601305bea8f Mon Sep 17 00:00:00 2001 From: Madison Date: Fri, 17 Jul 2026 04:34:12 -0500 Subject: [PATCH] change wording around user sessions for replays and clickmaps --- docs-mintlify/guides/apps/analytics/replays-and-clickmaps.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs-mintlify/guides/apps/analytics/replays-and-clickmaps.mdx b/docs-mintlify/guides/apps/analytics/replays-and-clickmaps.mdx index 97a952f1c..69c467df6 100644 --- a/docs-mintlify/guides/apps/analytics/replays-and-clickmaps.mdx +++ b/docs-mintlify/guides/apps/analytics/replays-and-clickmaps.mdx @@ -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.