Connect Delivery Cost to Revenue

​

Data path

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

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

​

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