Revenue analytics is currently works best for:
- Small to medium-sized companies
- Companies with subscription models (mostly SaaS)
If you process more than 20,000 transactions per month, or your revenue comes primarily from one-off payments rather than recurring subscriptions, revenue analytics may feel less useful, slower, or provide less insight than expected.
Revenue tracking enables you to capture revenue from your application via the events you are already sending us, or via an integration between your payment platform and our data warehouse, which you can then track in your revenue analytics dashboard.


You can start tracking revenue by doing the following:
- Choosing your reporting currency
- Configuring your revenue data source
Choosing your reporting currency
PostHog will automatically convert revenue from other currencies into your chosen reporting currency. For example, if someone makes a purchase in Canadian Dollars (CAD) and your reporting currency is US Dollars (USD), PostHog converts it into USD to ensure consistency.
You can configure your reporting currency at the top of your revenue analytics settings.


Configuring your revenue data sources
Next, you need to tell PostHog where to find your revenue data. PostHog can collect revenue from two different types of sources:
Data warehouse tables
The simplest way to send us revenue data is from your data warehouse tables.


The configuration for these are simple. Create a connection between PostHog and your revenue source and PostHog will automatically pick up the revenue data for you. Please refer to the data warehouse docs for more information.
Important: We currently only support revenue analytics data from Stripe. The Chargebee connector already exists and integration with revenue analytics is coming soon. We'll also implement integrations with RevenueCat and Polar in the near future. Check our roadmap at our team page.
Deferred revenue
When using revenue data from your data warehouse (from sources like Stripe), PostHog will automatically defer revenue recognition to match your accounting practices. This means we'll spread the revenue across all the months a charge is relevant for. You can learn more about this on the [deferred revenue](/docs/revenue-analytics/deferred-revenue) page.