Track product usage and engagement
Open
@arthurdedeus is already working on this.
Since Apr 30, 2026.
feature/customer-analytics
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
We're roughly able to monitor usage and engagement variations through usage metrics. Those are currently only built on top of events, while our most accurate usage metrics come from billing tables (available through data warehouse).
- https://github.com/PostHog/posthog/pull/57001
- Usage variations
- Engagement variations
To gauge MRR and forecasted MRR variations, usage metrics may not be the best way as these are "static" properties and not time-series aggregations.
- MRR/forecasted MRR variations
- Visibility on why a metric has changed
Lastly, a current blindspot we have in analytics is AI/MCP usage of our tools and data. The team is already working on this, but worth calling out as MCP power-users may be super healthy customers without ever accessing the UI.
- AI/MCP usage blindspot
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.