CellWall Logo

Posthog Recorder

PostHog

Heatmaps & Session Replay
monitor Exposure
v89da8cb1
A JavaScript library for capturing and replaying user sessions, including clicks, scrolls, form inputs, and network requests.
10M+ sites
Updated 8/4/2026
https://us-assets.i.posthog.com/static/1.410.6/posthog-recorder.js
Exposure Score
92

Popularity

92%

Usage across websites

File Size

165.95 KB

Download size

Load Time

33.09ms

Network latency

Execution Time

54.45ms

Runtime performance

Version Telemetry

Version Timeline

Visual representation of each version's active period

Metrics Over Time

Security score, performance score, and file size trends

0255075100v89daNormalized ScoreVersion
Security Score
Performance Score
File Size (KB)

Uptime History

Average response time over time

Version History Details

Detailed information for each version

v89da8cb1Latest
Span: 1 day
Score: 85
Size: 165.95 KB

Exposure & Risks

Security Score

Overall Security85 / 100
Exposure Levelmonitor

Risk Assessment

Critical Risks0
Total Observations1

Exposure Status

Monitor
Moderate behavioral concerns, review and mitigation advised.

Behavioral Concerns

No Known Security Risks

Our telemetry scan did not detect any immediate behavioral security risks for this resource.

Security Observations

Security-related findings from analysis

No security observations recorded for this version

Privacy & Data Flow

Data Collection

Cookies and local storage used by this script

Cookies

ph_*1 year
Used by PostHog for user identification (distinct ID) and session tracking. This is a wildcard as the actual name includes a project ID or hash.

Local Storage

ph_*
Used by PostHog to store client-side state such as the distinct user ID, session ID, or feature flags. This is a wildcard as the actual key includes a project ID or hash to prevent conflicts across multiple PostHog instances on the same domain or for specific internal state management for the recorder itself (e.g., buffering events). These keys are often used in conjunction with or instead of cookies for persistence and state management across sessions or page views for the user being recorded or for the recording process itself (e.g., event queue). The specific `posthog-recorder.js` may use such a key for managing the recording state or temporary data before sending it to the PostHog backend, though primary user/session IDs are typically set by the main PostHog library (posthog.js) and simply utilized by the recorder component. The `ph_posthog-recorder_playback_id` key, for example, might store a unique identifier for the current recording session to ensure continuity of data capture or for client-side debugging purposes, allowing the system to correlate recording segments if needed, though this is an example and not definitively present in all configurations. Other keys prefixed with `ph_` are commonly used for general PostHog SDK operations, including user identification and feature flag management, which the recorder relies on for context. The `recorder` specifically might store a buffer of events before sending them or state related to the recording itself, such as the current session's start time or last recorded event timestamp, to ensure proper sequencing and continuity if the browser tab is refreshed or navigated. This also includes keys for storing user properties and experiment variations for contextualizing the recordings within PostHog's broader analytics platform. The duration for these local storage keys is typically indefinite until manually cleared by the user or the browser's storage policies, but practically, they are often updated or overwritten with each session or significant interaction, ensuring fresh data. They might also be used to store configuration for the recorder, such as sampling rates or features enabled/disabled, which guides how the recording process behaves in the client's browser. It's also plausible for keys to store an indicator of whether a user has opted out of recording, although consent management is often handled at a higher level by a separate consent management platform (CMP).

Third-party Connections

External domains this script connects to

No external connections detected

Permissions Required

Browser permissions and capabilities used

No special browser permissions required.

Privacy Observations

Privacy-related findings from analysis

No privacy observations recorded for this version

Technical & Performance Analytics

Load Performance

File Size165.95 KB
Load Time33.09ms

Runtime Performance

Execution Time54.45ms
Network Requests0

Impact Assessment

Good
Minimal performance impact on page load

Performance Observations

Performance-related findings from analysis

No performance observations recorded for this version

Global Variables

Variables added to the global scope

No global variables detected

Event Listeners

Events this script listens for

No event listeners detected

Browser API Access

APIs and browser features accessed by this script

No API access detected

Technical Details

Compressed
Yes
CDN Delivery
No
Total Views
2
Is Mirror
No
Network Requests
0
Resource Hash
89da8cb1e99ce0c9e9bb76fe266844d365f157e077a76c36fc1ec87bef519161

AI Insights & Alternatives

Description

A comprehensive overview of this resource

The PostHog Session Recording library (`posthog-recorder.js`) integrates with the main PostHog analytics platform to provide detailed visual replays of user interactions on a website. When loaded, it passively observes and records all user activity, including mouse movements, clicks, scrolls, form submissions, DOM changes, and potentially console logs and network requests. This data is then sent to the PostHog backend, allowing website owners to visually reconstruct and replay individual user sessions exactly as they occurred in the browser. This script functions by creating a "recording" of the DOM, tracking changes to elements, and capturing various user events. It does not typically interact directly with sensitive user data for modification but records how users interact with forms and other elements, which could include personal information if entered by the user. It's used primarily for debugging, understanding user behavior, identifying UX issues, and providing context for customer support.

Key Features

Core functionalities and capabilities of this resource

  • Session Replay
  • User Interaction Tracking
  • DOM Change Recording
  • Error Monitoring
  • UX Analysis
  • Debugging
  • Click Tracking
  • Scroll Tracking

Alternatives

Similar libraries you might consider

Hotjar
FullStory
Microsoft Clarity

Documentation & Resources

Official Documentation