How it works
Product analytics starts with event collection. PostHog captures user interactions automatically and lets you define custom events for specific business metrics.Autocapture
Autocapture tracks user interactions without manual instrumentation. Install the PostHog snippet and it automatically collects:- Page views and navigation
- Button and link clicks
- Form submissions and inputs
- Custom data attributes
Autocapture works on web applications out of the box. For mobile apps, you’ll need to instrument events manually using the SDK.
Custom events
Track specific business events with custom instrumentation:Insight types
Product analytics offers six visualization types to analyze your data from different angles.Trends
Track metrics over time. See how events, user actions, or properties change across days, weeks, or months.Use cases: Daily active users, feature adoption rates, conversion metrics
Funnels
Analyze conversion through multi-step processes. Identify where users drop off in signup flows, checkout processes, or onboarding sequences.Use cases: Signup conversion, checkout abandonment, feature adoption funnels
Retention
Measure how many users return after their first visit. Understand which features drive long-term engagement.Use cases: Weekly retention cohorts, feature stickiness, churn analysis
User paths
Visualize the actual routes users take through your product. Discover unexpected navigation patterns.Use cases: Navigation analysis, feature discovery patterns, exit paths
Stickiness
See how frequently users perform actions. Identify your power users and engagement patterns.Use cases: Feature engagement frequency, power user identification, habit formation
Creating insights
Build insights from the insights page or directly from the new menu:- From dashboard
- With SQL
- Navigate to Product analytics in the sidebar
- Click New insight
- Select your insight type (Trends, Funnels, etc.)
- Configure events, filters, and breakdowns
- Save to a dashboard
Event definitions
Manage your event schema from the event definitions page:- Verify events: Mark events as verified to indicate they’re correctly tracked
- Add descriptions: Document what each event represents
- Set tags: Organize events by feature area or team
- View volume: See how frequently events fire
Event definitions are shared across your team. Changes apply to everyone in the project.
Filtering and breakdowns
Refine insights with filters and breakdowns:Property filters
Filter events based on properties:user_plan = 'free' or page contains '/pricing'.
Breakdowns
Break down metrics by property values to compare segments:- Break down conversion by traffic source
- Compare retention across user plans
- Analyze feature usage by device type
Common workflows
Track feature adoption
Create a Trends insight showing the event for your new feature over time. Break down by user plan to see which segments adopt fastest.
Analyze signup conversion
Build a Funnel from landing page view → signup click → account created → first action. Identify the biggest drop-off point.
Measure retention
Create a Retention insight with your activation event. See what percentage of users return each week after first use.
Find power users
Use Stickiness to see how many days per week users perform key actions. Users in the 5-7 day range are your power users.
Integration with other products
Product analytics connects with PostHog’s other tools:- Session replay: Click any data point to watch actual user sessions
- Feature flags: Create flags based on user properties or behaviors
- Experiments: Use insights as experiment metrics
- Surveys: Target surveys based on user actions
Best practices
Start with autocapture, add custom events later
Start with autocapture, add custom events later
Let autocapture handle basic interactions while you focus on tracking business-specific events. Add custom events for conversion actions, revenue events, and key features.
Use consistent naming conventions
Use consistent naming conventions
Adopt a naming pattern like
object_action (e.g., project_created, file_uploaded) to keep events organized as you scale.Add rich properties to events
Add rich properties to events
Include context like plan tier, feature area, or dollar amounts. This makes filtering and analysis more powerful without creating dozens of events.
Create dashboards for different stakeholders
Create dashboards for different stakeholders
Build focused dashboards for product, growth, and leadership teams. Each team cares about different metrics.