Definition
net MRRThe formula travels with the chart.
Subscription numbers you can defend.
A chart is only useful when its definition, source events, and late-arriving changes stay attached. CherrySub turns store histories into reconciled subscription facts with visible freshness.
Apple and Google ingest healthy · current processing lag 1.2s.
Lineage
28,410 eventsEvery point resolves to source events.
Freshness
1.2s lagLate data is visible and backfilled.
The number, its definition, and its source stay together.
Product and finance can disagree about meaning without disagreeing about the underlying history. Definitions are explicit; backfills revise the same maintained view.
Metric lineage
Trace MRR from chart to event.
The visible number is a maintained query over normalized transactions, not a detached export.
Store events28,410 normalized
→fresh
Net MRRsum(price_net × cadence)
→$184,120revenue_overview
Freshness
Late is a state, not a footnote.
Processing lag and expected deltas appear beside the value.
7 events still processingExpected MRR delta: +$69.93 · backfill automatic
Warehouse export
A stable schema with source identity.
Normalized facts arrive with event IDs, store references, and revision timestamps.
field
typecoverageevent_id
string100%occurred_at
timestamp100%access_level
string99.9%revenue_net
decimal99.8%source_payload
json100%destination: warehouse.subscription_events_v3
Maintained view
Backfills revise the chart, not the story.
Late renewals and refunds update the same series while the prior period stays comparable.
Current periodPrevious period
synced 2m agoDefinition
The formula is part of the product surface.
Saved metrics expose cadence, commission, refund, and currency rules.
metric revenue.net_mrr v4 select sum(price_net * cadence_factor) from subscription_periods where state in ("active", "grace") and environment = "production"
A maintained fact table, not another reporting silo.
CherrySub keeps metric meaning, event lineage, and data health visible at the same boundary.
Formulas are inspectable
Cadence, commission, refunds, and currency rules are explicit instead of buried in dashboard code.
Every row keeps an event
Charts and exports resolve back to the normalized source history that produced them.
Late data has a path
Freshness is visible and revisions update the same view instead of spawning corrective spreadsheets.
Trace one revenue point all the way back to the store.
Connect a sandbox catalogue and inspect the definition, events, and freshness behind the first chart.