Skip to content

Analytics

This page describes the questions the Revenue page and its Usage tab answer, and the one action you take from them.

Your numbers are on the Revenue page in the portal; usage is its Usage tab.

Revenue shows, for each currency you were paid in, four figures for the period you choose:

Figure What it is
Paid Money in from your customers, by the day each payment arrived, before refunds and fees
Refunded What of that money you returned to customers
Monaiq fee The platform fee Monaiq kept of each payment. It keeps its fee when you refund a payment, and gives it back when it refunds a payment by itself: one that arrived for an invoice already paid or cancelled, or one at checkout for a license it couldn’t issue
Kept Paid, less refunds, less Monaiq’s fee, before Stripe’s own processing fees

A refund counts against the payment it returns, on that payment’s day, not on the day you made it. Months are calendar months in UTC. Stripe’s own processing fees, which Stripe bills to you, are not in these figures. Monaiq does not collect or account for tax, so no figure here is a tax figure. Your own purchases of your own products are not revenue.

The breakdown splits the period by product, offering or customer. Amounts are never added across currencies: with more than one, you switch between them, and the page opens on the currency you last chose, or else the one with the most payments.

The Usage tab reports usage: how often your customers used the parts of your app that count their uses. It cuts that usage three ways.

Question What it tells you
Usage by feature Which parts of your app are being used, and how heavily
Usage by customer Which customers are driving that usage
Usage by offering Which of your priced offerings the usage sits under

Read together, those three answer the questions worth acting on. A feature nobody touches is a candidate for dropping out of your pricing. A customer whose usage is climbing is a candidate for a larger offering. An offering carrying heavy usage at a small price is telling you the price is wrong.

Each feature’s uses are counted in that feature’s own terms. The page never adds API calls to gigabytes: a customer or an offering shows what its usage charged and how many features it used, and opens to the uses of each feature and the days it was used on.

Usage by feature answers three adoption questions for each feature, over the period you choose.

Measure What it is
Breadth “N of M customers”: the customers who used the feature, of the customers holding a license of its product at any point in the period
Depth Uses per customer: the feature’s uses divided by the customers who recorded at least one use of it
Frequency Active days: the days each customer used the feature, averaged over the customers who used it

A license counts as held while it runs, including while it is suspended, and a license cancelled during the period counts too. A feature your app only checks, without counting uses, reads “Checks only”: its breadth and active days show, and it has no uses per customer. If the licenses cannot be counted, the page shows “N” alone and says so, rather than a number of customers it could not check.

Pick a product, then one of its features, to follow that feature: the chart becomes its recorded uses by day, and the customer and offering views narrow to the customers and offerings that used it.

The headline figure is the accrued usage charges: what the uses recorded in the period are worth at your per-use rates. It is split by how far billing has got: not yet billed, invoiced, and paid. The invoices that bill the usage are listed under the breakdown, each linking to its invoice.

Billed usage also counts in Revenue once its invoice is paid, so do not add the Usage and Revenue figures together. Amounts are per currency. If you charge in more than one, switch between them above the figures.

The period is this month, last month, the last 30 days (the default) or a range you pick, in whole calendar days in UTC, and the page states the days it covers. A link that asks for a period the report does not offer shows the last 30 days and says so.

Nothing here is estimated. The figures are the uses your app reported to Monaiq as your customers used it, recorded against the seat that reported them (one person or device on a license) and the license it belongs to. That is why the same numbers can be cut by customer and by offering: each report already knows which license it belongs to, and every license belongs to a customer and an offering.

Usage is billed for the period it happened in, so the Usage tab and the invoice for a period are looking at the same records.

You do not raise an invoice from here. The usage a period records is billed on that period’s invoice, which Monaiq raises. Get paid covers what happens to it after that.

Usage only appears for features your app reports: the uses it counts, and the checks it makes on features it only gates. If your app reports neither, there is nothing to chart, and the page has nothing to show you.

Revenue and Usage are about money in and use. Your invoices, their statuses and your payouts are in Get paid, and the licenses themselves sit with the customers who bought them.