Revenue source

Digital SaaS · ICP 1 — metering & the cost↔revenue join

May 2026 · month-to-dateSynthetic data

Revenue · in range

Recognized revenue this period

Join health

Cost matchable to a paying customer

Metered units aligned

1/1

Declared units metered on revenue

Metering source

Metering & billing

Billing & metering

Connected

Revenue · MTD

Revenue rows50

Last sync2026-05-15T10:00:00Z

Freshness0d

Billing models present

HybridSubscriptionUsage

Join health

How much cost can be matched to a paying customer via the stamped customer_id join key. The unmatched residual is never hidden — it stays visible as the gap below 100%.

of effective cost is attribution-ready

Break down the unmatched residual in Coverage

Unit alignment

Declared product units vs the metered_unit seen on revenue. A mismatch would break cost_per_unit / margin_per_unit in Unit economics.

Declared unit	Key	Primary	Alignment
Feature call	feature-call	Primary	Aligned

The revenue side of the join: the metering source that produces recognized revenue per customer, the join-health that decides whether margin is trustworthy, and the unit alignment that keeps per-unit economics honest. Revenue is governed by @radicas/core and restricted for the cost-viewer role; join health (a coverage %) stays visible.