> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/tour/analytics/revenue.md).

# Revenue

The revenue dashboard is divided into three 

### Recurring and usage-based revenue

<figure><img src="/files/uB2vLYsf4g1fRitKTUu1" alt=""><figcaption></figcaption></figure>

### Revenue movements

Revenue movements track how your ARR changes between periods. There are five core components:

* **New business** — ARR added from net-new customers signing their first contract.
* **Expansion** — ARR added from existing customers increasing spend: upgrading plans, adding seats, adding add-ons, or expanding usage.
* **Contraction** — ARR lost from existing customers reducing spend: downgrading, removing seats or add-ons, or capping usage.
* **Churn** — ARR lost from customers canceling entirely.
* **Reactivation** — ARR recovered from previously churned customers returning.

In addition, this chart also shows how usage-based revenue has increased or decreased compared to the previous period.

<figure><img src="/files/sbSZ6MdTGIqXl4y0yaP2" alt=""><figcaption></figcaption></figure>

### Compound Monthly Growth Rate (CMGR)

**CMGR** is a metrics that is heavily used in B2B SaaS and by investors to evaluate a company's month-over-month traction over an extended period (typically 7 to 18 months).

<figure><img src="/files/eJdOwIBekkHHTo5wuUNH" alt=""><figcaption></figcaption></figure>

### Geography

The last part of the revenue dashboard shows the revenue broken down by geography; internationally and by US states.

<figure><img src="/files/qUsg7Wv3mEXWj6j1Wfia" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bunny.com/guide/tour/analytics/revenue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.