Skip to content

Fill gaps from assistant conversations: replay option typo, sessions export FAQ - #230

Open
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/4a5ce161
Open

Fill gaps from assistant conversations: replay option typo, sessions export FAQ#230
mintlify[bot] wants to merge 2 commits into
mainfrom
mintlify/4a5ce161

Conversation

@mintlify

@mintlify mintlify Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes recurring points of confusion surfaced by assistant conversations about Session Replay configuration and exporting session data.

Changes

  • Corrected recording_sessions_percent to the actual init option name record_sessions_percent in the JavaScript Session Replay docs, and clarified that init options are set in your site's code, not the Mixpanel UI.
  • Added a Sessions FAQ entry explaining that Session Start/End are virtual events computed at query time, cannot be exported via the Raw Data Export API, and how to export session data through report CSV exports instead.

Context

Assistant query buckets showed repeated questions about the correct sampling option name (a docs typo confirmed the confusion) and about exporting session start/end times, which the docs did not address directly.

@mintlify
mintlify Bot requested a review from a team as a code owner September 7, 2026 16:13
@mintlify
mintlify Bot requested a review from rssebastian-mp September 7, 2026 16:13
@mintlify

mintlify Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
mixpanel-docs 🟢 Ready View Preview Sep 7, 2026, 4:16 PM

@greptile-apps

greptile-apps Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Confidence Score: 4/5

The incorrect exclusion of Mixpanel UI configuration should be corrected before merging.

The option name is fixed correctly, but the new categorical guidance contradicts the same page’s supported remote configuration workflow.

Files Needing Attention: docs/tracking-methods/sdks/javascript/javascript-replay.mdx

Important Files Changed

Filename Overview
docs/features/sessions.mdx Adds an accurate FAQ explaining why virtual session events require report-level exports.
docs/tracking-methods/sdks/javascript/javascript-replay.mdx Corrects the option typo but incorrectly excludes the documented Mixpanel UI configuration path.

Reviews (1): Last reviewed commit: "docs: point Raw Data Export API link to ..." | Re-trigger Greptile

When the SDK initializes, it makes a sampling decision based on your configured sampling rate. A percentage of initializations will trigger session recording accordingly.

To enable Session Replay and set your sampling rate, set the `recording_sessions_percent` when initializing the SDK. This is the only change needed in your existing JavaScript SDK implementation to enable Session Replay.
To enable Session Replay and set your sampling rate, set the `record_sessions_percent` init option when initializing the SDK. This is the only change needed in your existing JavaScript SDK implementation to enable Session Replay. Init options are set in your website's source code where you call `mixpanel.init()`, not in the Mixpanel UI.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 UI configuration contradiction

The statement that init options are “not in the Mixpanel UI” contradicts this page’s Remote Configuration section, which says record_sessions_percent can be configured under Organization Settings for paid Session Replay customers using SDK 2.74.0 or later. These users may incorrectly conclude that sampling must be controlled only in source code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants