Unit Economics

Overview

Unit Economics solution is designed to quantify the total cost associated with delivering products or services to customers.

Steps to create Unit Economics

1. Cost Gathering / Allocation

   • Create a cost allocation that includes direct and indirect/shared components (segments) of the costs to arrive to a Total Cost of the allocation

2. Cost Splitting

   • Identify the cost splitting i.e. identify the cost that you wanted to split segments in unit Cost ( per execution )

3. Unit Economics

   • Calculate the cost that can be served for the segment ( per dimension, e.g. Customer )

Below are examples of cost gathering, cost splitting, and calculating Unit Economics

Example 1: No Dimension

• Identify the unit metrics that you want to apply, as shown below

• Cost Allocation: Total Cost of cost allocation in a Month, e.g. consisting: direct, shared, etc.

• Cost Splitting: Unit Cost of running on allocation per Execution:

• Unit Economics: N/A

Unit Metric API to post via Postman

curl -X POST 'https://api.mavvrik.ai/<tenant slug>/unit-economics/<segment id>/metrics' \
--header 'Content-Type: application/json' \
--header 'x-api-key: <your API key>' \
--data '{
    "metrics": [
        { 
            "date": "2025-01-01", /* will be aggregated to month */
            "value": 400
        },
        { 
            "date": "2025-02-01",
            "value": 200
        }
    ]
}'

Example 2: Single Dimension

• Units BY Customer, with the following Unit Metric input:

• Cost Allocation: Total Cost of cost allocation in a Month, e.g. consisting: direct, shared, etc.

• Cost Splitting: Unit Cost of running on allocation per Execution:

• Unit Economics: Serving Cost of running on allocation per Dimension:

Unit Metric API to post via Postman

curl -X POST 'https://api.mavvrik.ai/<tenant slug>/unit-economics/<segment id>/metrics' \
--header 'Content-Type: application/json' \
--header 'x-api-key: <your API key>' \
--data '{
    "metrics": [
        {
            "date": "2025-01-01", /* will be aggregated to month */
            "dimensions": [
              { "key": "customer", "value": "Customer A" }
            ],
            "value": 100
        },
        {
            "date": "2025-01-01",
            "dimensions": [
              { "key": "customer", "value": "Customer B" }
            ],
            "value": 300
        },
        { 
            "date": "2025-02-01",
            "dimensions": [
              { "key": "customer", "value": "Customer A" }
            ],
            "value": 100
        },
        {
            "date": "2025-02-01",
            "dimensions": [
              { "key": "customer", "value": "Customer B" }
            ],
            "value": 100
        }
    ]
}'

Example 3: Multi Dimensions

• Units BY Customer and Location, with the following Unit Metric input:

• Cost Allocation: Total Cost of cost allocation in a Month, e.g. consisting: direct, shared, etc.

• Cost Splitting: Unit Cost of running on allocation per Execution:

• Unit Economics: Serving Cost of running on allocation per Dimension:

Unit Metric API to post via Postman

curl -X POST 'https://api.mavvrik.ai/<tenant slug>/unit-economics/<segment id>/metrics' \
--header 'Content-Type: application/json' \
--header 'x-api-key: <your API key>' \
--data '{
    "metrics": [
        {
            "date": "2025-01-01", /* will be aggregated to month */
            "dimensions": [
              { "key": "customer", "value": "Customer A" },
              { "key": "location", "value": "US" }
            ],
            "value": 60
        },
        { 
            "date": "2025-01-01",
            "dimensions": [
              { "key": "customer", "value": "Customer A" },
              { "key": "location", "value": "EU" }
            ],
            "value": 40
        },
        {
            "date": "2025-01-01",
            "dimensions": [
              { "key": "customer", "value": "Customer B" },
              { "key": "location", "value": "US" }
            ],
            "value": 200
        },
        {
            "date": "2025-01-01",
            "dimensions": [
              { "key": "customer", "value": "Customer B" },
              { "key": "location", "value": "EU" }
            ],
            "value": 100
        },
        {
            "date": "2025-02-01",
            "dimensions": [
              { "key": "customer", "value": "Customer A" },
              { "key": "location", "value": "US" }
            ],
            "value": 30
        },
        { 
            "date": "2025-02-01",
            "dimensions": [
              { "key": "customer", "value": "Customer A" },
              { "key": "location", "value": "EU" }
            ],
            "value": 70
        },
        {
            "date": "2025-02-01",
            "dimensions": [
              { "key": "customer", "value": "Customer B" },
              { "key": "location", "value": "US" }
            ],
            "value": 25
        },
        {
            "date": "2025-02-01",
            "dimensions": [
              { "key": "customer", "value": "Customer B" },
              { "key": "location", "value": "EU" }
            ],
            "value": 75
        }
    ]
}'

Steps to create Unit Economics in Mavvrik portal

1. Log into Mavvrik

2. Click on the menu

3. Click on unit economics under operate

4. Click on +Unit Economics

5. Fill in the details and click on create

6. Unit Economics entry is created

7. Click on the created Unit Economics entry

8. Click on +segment

9. Select the Cost allocation to which you want to apply the unit economics and click on Next

10. Enter the dimensions you have calculated in the cost splitting step and click on Create

11. You will see below

12. Click the three dots on the segment and select View Metrics. This opens a dialog with two tabs: Metrics and cURL.

13. To enter metrics via the UI,

    1. click +Metric, select the Date, and enter the Value (the unit count for that dimension, e.g. calls or executions).

    2. Select a dimension Key and enter its Value

    3. Click +Dimension to add more than one dimension to the same entry

    4. click Save.

14. Update the Unit Economics metrics calculated and post the data using Postman

15. After the data is posted, you can see the data in the UI as below

Header Icons

The Unit Economics list page (and each entry's detail view) has a header toolbar with: Share (copies a link to the current page/filters), Bookmark, Subscription (see Bookmarks and Subscriptions for how these work), Screenshot (downloads the page as a PDF), Reload (clears filters/selections back to default), and Help (opens this documentation).

Troubleshooting

Metrics are missing for the month or dimension being reviewed

1. Confirm that you are viewing the intended Unit Economics entry and segment, and check the cost allocation selected for that segment.

2. Open the segment's three-dot menu and select View Metrics. Check that the required metric entries have been saved.

3. Compare each entry's Date with the month you are reviewing, and check its dimension Key and Value against the customer, location, or other dimension you expect.

4. If an entry has not been added, use +Metric to enter its date, unit count, and applicable dimension values, then click Save.

The calculated cost differs from the expected amount

1. Compare the allocated cost and metric values for the same month. Include the direct and shared cost components used by the selected allocation.

2. Check that metric Value represents the intended unit count, such as calls or executions, rather than a monetary cost.

3. Use the worked examples above to reconcile the calculation: monthly allocated cost divided by total monthly units gives the unit cost; multiplying that unit cost by a dimension's units gives its serving cost.

The Unit Metric API call is rejected or returns an error

1. Confirm the request includes an x-api-key header; a Content-Type header alone is not sufficient to authenticate.

2. Confirm the URL path matches your tenant and the specific segment you're posting to: open that segment's View Metrics → cURL tab and copy the auto-generated command rather than reusing a URL from another segment or tenant.