MRR and payment filters
These filters narrow any report, and the customer list, to customers by how much they pay or have paid. There are four:
- Current MRR: what the customer pays per month today. Churned customers and anyone who never paid have a current MRR of 0.
- Last active MRR: what the customer paid per month the last time they were paying. For paying customers it's the same as their current MRR. For churned customers it's the MRR they had just before they churned. Customers who never paid have none (0).
- Total paid: everything the customer has paid you so far. It counts successful payments, one-time charges included, after discounts. Refunds aren't subtracted.
- Payments: how many successful payments the customer has made, one-time charges included.
Last active MRR is what makes questions about lost customers possible. "Current MRR above 1,000" can never include a churned customer, because they pay nothing today. "Last active MRR above 1,000" finds everyone who paid more than 1,000, whether they're still with you or not.
Total paid and Payments look at the whole relationship instead of a monthly price. They separate a customer who left after one small payment from one who paid for two years before leaving, even when both had the same MRR.
Amounts and currency
Current MRR, Last active MRR and Total paid take amounts in whole units of your account's default currency: dollars, euros, kroner or yen, never cents. The currency is shown next to the input.
Customers who pay in other currencies are converted at the latest exchange rates before comparing, so "Current MRR above 1,000" means above 1,000 in your account currency whatever each customer is billed in. A customer who has paid in more than one currency has each part converted and added up for Total paid. The amount is always in the account's default currency, even if you've switched the report to show another currency.
Payments is a plain count, so it has no currency.
Operators
| Operator | Meaning |
|---|---|
| is | the amount rounded to whole units equals the number, e.g. Current MRR is 0 or Payments is 1 |
| is above | more than the number |
| is below | less than the number |
| is between | from the first number to the second, both included |
Add them the same way as any other filter, for example Filter → Total paid. They can be combined with each other, with every other filter, and with saved segments.
Examples
- Big customers you lost: set the customer list to canceled customers, then add Last active MRR is above 1,000. Export to CSV for a win-back campaign.
- Big customers who are winding down: Last active MRR is above 1,000 together with Current MRR is below 500 finds customers who used to pay a lot and have since downgraded or left.
- Churn and retention for your largest accounts: Current MRR is above 2,000 on the Churn or Retention report.
- Small-customer MRR: Current MRR is below 100 on the MRR report shows how much of your revenue comes from your smallest customers.
- Customers who left before they really started: on the Churn report, Total paid is below 200 shows how many of the customers you lost had paid less than 200 in total. Use it to tell early drop-offs apart from customers who stayed a while.
- Gone after the first payment: Payments is 1 on the canceled customers in the customer list.
- Your most loyal customers: Payments is above 24 finds everyone who has paid you more than 24 times.
Note that on reports that show history, such as the MRR chart, the filter picks customers by their values today (current MRR, last active MRR, total paid or payments so far), and then shows those customers' full history. "Current MRR above 1,000" on the MRR chart shows how the customers who pay above 1,000 now got there. It doesn't show "MRR from customers who paid above 1,000 at the time".
Sharing a filtered view
These filters live in the URL, so a filtered report is a shareable link, and they stay set as you move between reports.
The same filters are available on the REST API as mrr, last_active_mrr, total_paid and payments, using the same range syntax as the date filters: 1000 (is), 1000.. (above), ..500 (below) and 500..1000 (between). See the API reference. The AI assistant, the MCP server and the CLI understand them too, so you can ask for "customers who churned in September and paid less than 200 in total".
