> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/app-analytics/revenue/total-revenue-current-vs-previous-period.md).

# Total Revenue - Current vs Previous Period

The Total Revenue graph is a comparative analytic tool in Twinr’s Inbuilt Analytics that visualizes your app’s revenue over two distinct periods. This comparison allows you to quickly assess financial growth and make strategic decisions based on revenue trends.

## Overview

The Total Revenue graph juxtaposes your earnings from the current period against those from the previous period, presenting a side-by-side comparison to highlight growth or declines.

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

* **Revenue Summary**: At the top, the graph provides a total revenue figure for the current period, along with a percentage indicating the increase or decrease compared to the previous period.
* **Graph Trend Lines**: Two trend lines represent the revenue over time—one for the current period and one for the previous period. This dual-line format allows for direct visual comparison.
* **Tooltip Data**: Hovering over any point on the trend lines reveals specific revenue figures for each corresponding day.


---

# 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:

```
GET https://help.twinr.dev/app-analytics/revenue/total-revenue-current-vs-previous-period.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.