Question 1

What is revenue analytics in Lago?

Accepted Answer

Revenue analytics is Lago ' s unified layer over billing, revenue, and product usage data, built on Apache Superset dashboards that finance and operations teams use without a separate BI tool. Metrics like MRR, revenue streams, and credit consumption can be filtered by customer, subscription, or product and exported as JSON, CSV, or Excel.

Question 2

Can I build custom dashboards on my billing data?

Accepted Answer

Yes. Dashboards are fully composable on top of Lago ' s billing data, with prebuilt financial reporting views as a starting point and the ability to filter, break down by dimension, and build per-customer views from there. The same data is available through the API for teams that want to pull it into their own BI stack instead.

Question 3

Does Lago forecast future revenue?

Accepted Answer

Yes. Lago forecasts paid usage up to 12 months ahead using historical data grouped by billable metric, subscription, and charge, and returns three scenarios: conservative, realistic, and optimistic. It models subscription growth from historical patterns, though forecasts can ' t account for new products or billable metrics that don ' t have usage history yet.

Question 4

Does Lago handle revenue recognition (ASC 606 / IFRS 15)?

Accepted Answer

Yes. Lago recognizes revenue on an accrual basis, allocating it across the service period it was earned rather than when the invoice was sent or paid, following ASC 606 and IFRS 15 automatically. Recognized revenue, deferred revenue, a revenue waterfall, and balance sheet and income statement views are all available as reports. This capability is in alpha, so teams should reconcile its output against their own books before using it for statutory reporting.

Question 5

What's the difference between recognized and deferred revenue in Lago?

Accepted Answer

Recognized revenue is the portion of an invoice that ' s been earned through service delivery in a given period; deferred revenue is the portion billed in advance for service not yet delivered, and sits as a liability until it ' s earned. Lago tracks both automatically from the same billing data, so finance teams don ' t have to build separate accrual logic on top of invoices.

Question 6

How fresh is the data in Lago's analytics dashboards?

Accepted Answer

Analytics datasets refresh daily, so same-day billing or usage changes may not appear in a dashboard until the next refresh. Teams that need faster visibility can pull analytics data directly through the API instead of waiting on the daily refresh.

Question 7

Can billing data sync to my own data warehouse?

Accepted Answer

Yes, through the Lago Data Pipeline. It syncs core billing tables (customers, invoices, subscriptions, fees, credit notes, and more) into warehouses like Snowflake, BigQuery, Redshift, and Databricks, plus transactional databases and cloud storage, on a schedule as frequent as every 15 minutes. This is what lets a finance team run its own SQL against billing data or build dashboards in a tool Lago doesn ' t natively support.

Question 8

Does revenue analytics work across usage-based, subscription, and hybrid plans?

Accepted Answer

Yes. Because the analytics layer sits on the same billing data as invoicing, it covers self-serve, sales-led, subscription, usage-based, and hybrid revenue streams in one place rather than requiring separate reporting per pricing model.

Your data, everywhere you need it.

Trusted by the most innovative companies

Built for next-gen companies

Reconciliate any revenue stream effortlessly

Get the exact data you need

Forecast revenue

How Lago gathers and visualizes and complex billing data

Resources

Read documentation.

Watch demo.

Usage-based pricing playbook.

Empower all teams with usage data

Engineering

Product

Finance

Operations

Built for companies with sophisticated needs

Revenue Analytics FAQ