Statsig adds analytics and session replay

This expansion matters because it turns Statsig from a single line item for experiments into the system product teams open every day to watch behavior, diagnose friction, and decide what to ship next.

• The products fit together at the event level. A team can gate a feature, run an experiment, read the metric impact in analytics, then watch session replay to see what users actually did. That makes each added module easier to adopt than buying a separate tool with a separate data pipeline.
  1 sacra 2 sacra
• The money flow also gets bigger inside the same account. Statsig already charges on metered events, and company materials note that analytics events and session replays are part of that usage base. More teams using more workflows means more events processed and a higher bill without a new vendor search.
  1 sacra 2 sacra
• This is also a defensive move against category convergence. Amplitude is moving into experimentation, LaunchDarkly is adding analytics and warehouse native features, and PostHog bundles flags with analytics and replay. Winning now depends on owning both release control and measurement in one product stack.
  1 sacra 4 sacra

The next phase is suite compression across product infrastructure. If Statsig keeps making analytics and replay good enough for enterprise teams, it can pull budget from analytics and observability tools, not just experimentation vendors, and become a larger standard platform inside product led organizations.