Product analytics
Understand the people behind the events.
Connect active users, sessions and product events to reliability, so usage and failures become part of the same engineering conversation.
See how your product is used
Track page views, grouped by route, and named events. Daily, weekly and monthly active users and session metrics provide a view of engagement over time, and D1, D7 and D30 retention are always shown.
Funnels and retention
Build funnels of two to six steps over a window of up to 30 days, and read retention as a cohort grid. During the beta, funnels and the retention grid are enabled per organisation.
Give events a useful vocabulary
Name important interactions around the product: creating a project, applying a discount or exporting a report. Consistent names make adoption easier to compare.
Bring usage into debugging
Use the same project and identity context for analytics and errors. An often-used feature with a small error rate can deserve more attention than a noisy edge case.
Related
- Find the failure. Keep the context. Group exceptions into issues, inspect stack traces and breadcrumbs, and understand which users and releases are affected.
- Fix what matters to your users. Bring errors, performance and feature usage together to help prioritise engineering work by its effect on the product.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.