RevenueCat Charts v3 is a data pipeline rebuild, not a UI refresh (real-time charts, more stable history)

Original article (source): RevenueCat - “RevenueCat Charts v3: fresher data, better decisions” (Apr 16, 2026)

• https://www.revenuecat.com/blog/engineering/revenuecat-charts-v3-fresher-data-better-decisions/

Summary

RevenueCat’s point is straightforward: they rebuilt the plumbing underneath Charts, and the practical effect is faster feedback loops and fewer “why did last week’s numbers change?” arguments.

What changes with Charts v3:

• Near real-time updates for most charts, driven by live event ingestion (instead of batch refresh every 2 to 12 hours).
• A unified subscription model across stores, so concepts like renewals, product changes, and resubscriptions behave consistently.
• Refunds stop rewriting history. Revenue shows up on purchase date, and if refunded later it is subtracted on the refund date (instead of shifting completed periods).
• Cohorting methodology changes in their explorers, using customer-relative lifecycles rather than “month bucket edge effects”.

They also flag expected metric shifts (example: trial conversion rate may look lower if it tightens to direct trial-to-paid counting).

Why this matters

If you run growth experiments, the worst-case loop is:

1. ship a paywall test or promo,
2. stare at charts that are stale for hours,
3. then have historical periods change after refunds and adjustments.

Charts v3 is trying to make “is this working?” a same-day question, and make historical reporting stable enough to trust when you review learnings.

Tiny win

Before your next pricing or paywall change:

• pick one chart you use for go/no-go (trial conversion, refunds, MRR, churn),
• write down what movement would make you stop the test,
• and add a quick note for your team on how refunds and resubs are counted in your dashboard.

Read the original: https://www.revenuecat.com/blog/engineering/revenuecat-charts-v3-fresher-data-better-decisions/