> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Usage metrics **Customer Analytics is in beta** Customer Analytics is currently in beta and free to use. We're actively developing this feature and would love your [feedback](https://app.posthog.com/customer_analytics#panel=support%3Afeedback%3Acustomer_analytics%3Alow%3Atrue). Usage metrics let you define global activity measurements and track them for each customer. Any event performed by your users – or data from your [Data Warehouse](/docs/data-warehouse.md) tables – can be turned into usage metrics, so that you can understand their activity at a glance and identify expansion opportunities or churn risk. ![Usage metrics in customer profile](https://res.cloudinary.com/dmukukwp6/image/upload/q_auto,f_auto/pasted_image_2025_12_19_T12_47_09_424_Z_893c3cd740.png) ## Example usage metrics Here are some examples of usage metrics for SaaS products: | Metric | Events to match | Use case | | --- | --- | --- | | API calls | `api_request` | Identify heavy API users for expansion | | Feature adoption | `feature_x_used` | Track adoption of new features | | Error rate | `$exception` | Spot customers hitting issues | | Export usage | `export_created` | Find power users | ## Data Warehouse metrics You can also create usage metrics from [Data Warehouse](/docs/data-warehouse.md) tables. This is useful when your usage or billing data lives outside of PostHog events – for example, in Stripe or your own database. When creating a Data Warehouse metric, you specify: - **Table** – The Data Warehouse table to query - **Timestamp column** – The column used to filter rows by date range - **Group key column** – The column used to match rows to customers Each Data Warehouse metric is limited to a single table. **Limitation** Data Warehouse usage metrics currently only render on group profiles, not person profiles. ### Still have questions? Ask PostHog AI ### Was this page useful? HelpfulCould be better