Product Analytics

Product analytics is the use of behavioral data to understand how people actually use a product, where they retain, and what product decisions should change. Spenser Skates, Founder & CEO, Amplitude adds the concept through Amplitude’s origin: Spenser Skates and Curtis Liu needed to understand why Sonalight users tried the voice app but did not keep using it.

The source makes product analytics narrower and more operational than generic traffic analytics. The founders wanted to answer whether a successful first voice-recognition match predicted later retention, what cohorts behaved differently, and which product changes could improve behavior. Existing tools such as Google Analytics, Flurry, Mixpanel, Kissmetrics, and Adobe did not answer those questions in the way the founders needed, so their internal tool became Amplitude.

Key Claims

• Product analytics is most useful when it answers a decision question rather than only reporting usage counts.
• Retention questions can expose whether the product has a reliability, onboarding, habit, or value problem.
• The same behavioral visibility can become a company when multiple teams recognize the pain and will pay to solve it.
• Product analytics connects Data-Driven Product Culture to concrete founder decisions: what to fix, whether to pivot, and how to explain value to customers.

Connections

• Amplitude, Spenser Skates, Curtis Liu, and Sonalight - source case.
• Technical Demo Retention Gap - failure pattern that created the analytics need.
• Internal Tool Productization, Customer Evidence Strategy, and Founder-Led Sales - path from internal tool to product.
• Google Analytics, Flurry, Mixpanel, Kissmetrics, and Adobe - named comparison tools.
• Zynga and [[TwelveGigs|12gigs]] - early market context where the value was legible.