How to build product growth KPIs and measures #10195

Highlight is primarily an observability tool (session replay, error tracking, log management), not a product analytics platform. It can tell you "this user hit an error on the checkout page" but it's not built to answer "what percentage of users clicked the upgrade button this week."

That said, you can get some product analytics-style data out of Highlight:

What Highlight can do natively:

• Session replay lets you watch how people use features, which is great for qualitative insights
• You can search sessions by URL path to see traffic patterns
• H.track() sends custom events that show up in your session timeline

Why H.track() mentions forwarding to Amplitude:
Highlight doesn't have a built-in funnel/retention/cohort analysis engine. H.track() captures the event in the session context (so you can see it in the replay), but for actual quantitative analysis (conversion rates, feature adoption trends, A/B test results), you need a dedicated product analytics tool.

What to use for product growth KPIs:

• PostHog -- open source, self-hostable, has autocapture for clicks/pageviews plus funnels, retention, and feature flags. Closest to an all-in-one if you want to stay open source.
• Amplitude or Mixpanel -- the standard SaaS options for product analytics. Both have generous free tiers.
• Plausible or Umami -- if you just need lightweight page/button-level analytics without the full product analytics stack.

The typical setup is Highlight for debugging and observability, plus one of the above for product metrics. They serve different needs and the overlap is minimal.

If you want to keep things simple and only add one tool, PostHog covers the most ground since it has both product analytics and a basic session replay feature (though Highlight's replay is significantly more polished).