Connect Delivery Cost to Revenue - Ruba Docs

Ruba cost analysis workspace in light mode

Ruba cost analysis workspace in dark mode

Revenue alone cannot tell you whether a customer is profitable. Cost Insights joins the revenue Ruba already knows with the cost of serving that customer, producing cost, profit, and lifetime-value metrics.

Cost Insights is in beta. Open Insights → Cost analysis in the dashboard; there is no organization-setting step to enable it.

Data path

Your application ingests a usage event with a reserved _cost object in its metadata.
Ruba attributes and aggregates that cost alongside orders and subscription revenue.
You inspect cost, profit, and customer LTV through Insights → Cost analysis or the Metrics API.

{
  "events": [
    {
      "name": "llm.inference",
      "external_customer_id": "user_123",
      "metadata": {
        "_cost": {
          "amount": 0.025,
          "currency": "usd"
        }
      }
    }
  ]
}

The example records a $0.00025 cost in cents for one inference event.

Costs worth attaching

Model-provider calls in AI products
Compute, storage, and bandwidth consumed by a customer
Per-message email or SMS charges
Any third-party unit cost that can be attributed to an event

Continue the implementation

Shape cost events

Validate the _cost object and choose the event identity.

Read profitability

Query cost, profit, and lifetime-value metrics.