Student pricing is available for eligible university email holders. View plans

NextSprints
NextSprints Icon NextSprints Logo
Product Design

Master the art of designing products

Product Improvement

Identify scope for excellence

Product Success Metrics

Learn how to define success of product

Product Root Cause Analysis

Ace root cause problem solving

Product Trade-Off

Navigate trade-offs decisions like a pro

All Questions

Explore all questions

Meta (Facebook) PM Interview Course

Practice Meta-focused PM cases

Amazon PM Interview Course

Practice Amazon-focused PM cases

Apple PM Interview Course

Practice Apple-focused PM cases

Google PM Interview Course

Practice Google-focused PM cases

Microsoft PM Interview Course

Practice Microsoft-focused PM cases

All Courses

Explore all courses

1:1 PM Coaching

Practice in a one-to-one session

Resume Review

Narrate impactful stories via resume

Guides Pricing
nextsprints logo

Not a member?

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement.

nextsprints logo

Register to continue.

Login with Google Login with LinkedIn

By proceeding, you agree to our Terms of Use and confirm you have read our Privacy and Cookie Statement .

Company focus

PostHog
Product Success Metrics Easy Member-only

How would you measure the success of PostHog Session Replay?

Prepared by NextSprints

12 mins
Report an error
Metric Definition North Star Design Guardrail Metrics Developer Tools Product Analytics B2B SaaS Privacy Success-Metrics North-Star-Metric Session-Replay
Product Management Product Success Metrics Question: measuring PostHog Session Replay

Introduction

Session Replay is one of PostHog's oldest and most-loved products. It records what users actually do on a website or mobile app, so teams can watch the clicks, scrolls, errors and rage clicks behind a number on a dashboard. The first 5,000 recordings each month are free, after which teams pay per recording, and mobile replay is an add-on. Replay matters beyond its own revenue: it is often the product that makes analytics "click" for a team, because it shows the why behind a funnel drop. With Replay Vision, PostHog now also uses AI to scan replays for struggles automatically. Measuring Session Replay's success means capturing whether teams learn from recordings, not just whether recordings exist.

Framework Overview

I'll cover product context, goals, a North Star metric and its breakdown, supporting metrics, guardrails, trade-offs and counter metrics, then finish with strategic initiatives.

Step 1

Product Context (3 minutes)

Key stakeholders:

  • Product teams (engineers, designers, PMs, founders): watch replays to debug issues and understand behaviour.
  • Support and success teams: look up a customer's session when a ticket arrives.
  • End users: are recorded, so their privacy must be protected through masking.
  • PostHog: earns usage revenue and drives adoption of other products.

User flow:

  1. Team enables recording (on by default for many new web projects) and sets sampling, masking and minimum duration.
  2. Recordings are captured and linked to events, errors and the user's person profile.
  3. Team finds relevant sessions through filters, playlists, links from funnels and error issues, or Replay Vision summaries.
  4. Team watches, comments, shares with colleagues and acts: files a bug, changes a design, or contacts the user.

Lifecycle stage: mature growth. Replay is a high-revenue product with strong competition (FullStory, Hotjar, LogRocket, Microsoft Clarity, which is free) and now an AI layer that changes how recordings are consumed.

Why it matters to PostHog's strategy: replay is the bridge between quantitative data and understanding. A team that clicks from a funnel drop into a replay is using two products together, which is the core of PostHog's all-in-one bet.

Subscribe to access the full answer

Image of author NextSprints

NextSprints

Updated Oct 31, 2026