Overview
SessionSight SDKs at a glance
Last updated:
SessionSight provides five SDKs, each designed for a specific purpose:
| SDK | Environment | API Key | Purpose |
|---|---|---|---|
| Insights | Client-side (browser) | Public | Session recording, heatmaps, form analytics |
| Split Testing | Client-side (browser) | Public | A/B tests, copy tests, JSON experiments |
| Goals | Server-side | Secret | Goal tracking (count or revenue, USD) |
| Feature Flags | Server-side | Secret | Feature flag evaluation and targeting |
| Feedback | Server-side | Secret | User feedback, ratings, bug reports |
Insights SDK (client-side)
Runs in your visitors’ browsers. Captures session recordings, click/scroll/movement data for heatmaps, form field interactions, and page navigations. All data is sent to SessionSight automatically.
One line to install, one line to initialize. See Setup to get started.
Key features:
- Automatic and manual recording modes
- User identification with custom properties
- SPA navigation tracking
- Privacy modes and data attributes for controlling what gets captured
- Visitor ID available via
getVisitorId()orss_vidcookie
Split Testing SDK (client-side)
Runs in your visitors’ browsers. Assigns visitors to test variations, tracks exposures automatically, and reports conversions. Supports three test types: ID (component branching), text (copy testing), and JSON (structured data). Zero-flicker by design with localStorage caching, SSR bootstrap, and an anti-flicker snippet.
One line to install, one line to initialize. See Setup to get started.
Key features:
- Three test types: ID, text, and JSON
- Zero-flicker with caching, SSR bootstrap, and anti-flicker snippet
- Automatic conversion attribution via Goals
- Visitor ID shared with the Insights SDK via
ss_vidcookie for stable variant bucketing; exposures themselves are session-scoped
Goals SDK (server-side)
Runs on your server. Tracks goal completions. Each goal is either a count goal (conversion counter) or a revenue goal (USD totals). Uses a secret API key so values can’t be spoofed from the browser.
Key features:
- Increment and decrement goals
- Revenue goals where
amountis summed into progress as dollars - Metadata for context (plan, source, campaign)
Feature Flags SDK (server-side)
Runs on your server. Evaluates feature flags with targeting rules based on user context and segments. Supports multiple environments for staged rollouts.
Key features:
- Boolean and string flag evaluation
- Targeting with user context and segments
- Per-environment configuration via the
environmentsetup option - List all flags programmatically
Feedback SDK (server-side)
Runs on your server. Collects user feedback, bug reports, and ratings. Supports pre-defined option values and free-text messages, with metadata for context. Uses a secret API key so submissions are authenticated.
Key features:
- Structured feedback with options and free text
- Flexible enough for star ratings, sentiment, and bug reports
- Automatic session linking via the Insights SDK (visitor and user identity are resolved from the session)
API Keys
Each SDK requires an API key from your SessionSight dashboard:
- Public key (
sessionsight_pub_...): safe to include in client-side code. Used by the Insights and Split Testing SDKs. - Secret key (
sessionsight_sec_...): must stay on your server. Used by the Goals, Flags, and Feedback SDKs.
Manage keys from the API Keys page, or use the API key selector in the top nav to auto-fill code examples throughout these docs.