> For the complete documentation index, see [llms.txt](https://subscriptions-docs.tech-arms.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://subscriptions-docs.tech-arms.io/features/analytics/overview.md).

# Overview

A quick health check of your subscriptions: orders, new subscriptions, revenue and orders per subscription, billing results and statuses.

The **Overview** tab gives you the main numbers of your subscription business on one screen. Use it for a quick check before you dig into the [Revenue](https://subscriptions-docs.tech-arms.io/features/analytics/revenue.md) or [Subscriptions](https://subscriptions-docs.tech-arms.io/features/analytics/subscriptions.md) tab.

In the app menu, click **Analytics**. The **Overview** tab opens first.

![The Overview tab with its six cards](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FyDoeTLdxgVNTUtlh2DAE%2Fanalytics-overview-cards.png?alt=media)

The tab uses the date range and **Compare to** period at the top of the page. To learn how to change them, how to read a card and which orders are counted, see [Analytics](https://subscriptions-docs.tech-arms.io/features/analytics.md).

## Cards

| Card                                 | What it counts                                                                                                                                                                                                                                                                                        | Comparison     |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| **Total orders**                     | The number of subscription orders placed in the period: first orders that started a subscription plus renewal orders that were charged successfully.                                                                                                                                                  | Yes            |
| **Total subscriptions created**      | The number of subscriptions created in the period, whatever their status is now (active, paused, cancelled, failed or expired).                                                                                                                                                                       | Yes            |
| **Average revenue per subscription** | The total of the subscription orders placed in the period, divided by the number of different subscriptions those orders belong to. Shown in your store's currency.                                                                                                                                   | Yes            |
| **Net gained/Loss subscription**     | The number of subscriptions that became active again in the period, after being paused, cancelled or failed, and are still active today. New subscriptions are not counted here. The percentage compares this number with the reactivated subscriptions from before the period that are still active. | Own percentage |
| **Average orders per subscription**  | The number of subscription orders placed in the period, divided by the number of different subscriptions those orders belong to.                                                                                                                                                                      | No             |
| **Average subscriptions lifetime**   | For subscriptions created in the period that are still active, the average number of days from their creation date to today.                                                                                                                                                                          | No             |

### Example: Average revenue per subscription

In the last 30 days you had 12 subscription orders worth 600.00 in total. They belong to 8 different subscriptions. **Average revenue per subscription** shows 600.00 ÷ 8 = 75.00. **Average orders per subscription** shows 12 ÷ 8 = 1.50.

## Charts

![The Success vs. Failed billing attempts and Subscriptions status charts](https://3752025337-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F479XnzvtVA5dDE3Rt2Uh%2Fuploads%2FjKd3NtQig37qTKPUYEu6%2Fanalytics-overview-charts.png?alt=media)

### Success vs. Failed billing attempts

Two lines: the number of successful and failed renewal charges in the period. Every attempt counts, so a renewal that failed twice and then succeeded adds two failed attempts and one successful attempt.

The chart groups attempts by hour for a one-day range, by day for ranges up to about a month, by month for ranges up to 15 months, and by year for longer ranges. It does not show a comparison.

If too few attempts exist, the chart shows **Not enough data available**.

### Subscriptions status

A donut chart of the subscriptions created in the period, grouped by their status today: **Active**, **Paused**, **Cancelled**, **Failed** and **Expired**.

Both charts have their own date range in the top-right corner. Click it to view another period.

{% hint style="info" %}
A failed charge is not the end of a subscription. The app retries it according to your [Renewal & Dunning](https://subscriptions-docs.tech-arms.io/features/email-notifications/renewal-and-dunning-settings.md) settings. To see why charges fail, check [Billing error codes](https://subscriptions-docs.tech-arms.io/resources/help-center/troubleshooting-guide.md).
{% endhint %}

## Good to know

* Statuses are today's statuses. A subscription created last month and cancelled yesterday counts as **Cancelled** in **Subscriptions status**, even if you report on last month.
* **Average subscriptions lifetime** keeps growing day by day for the same period, because it is measured up to today.
* Order figures include the full order total, with shipping, taxes and any one-time items bought in the same checkout.

*If you need help, feel free to reach out to us via in-app* [***Live chat***](https://go.crisp.chat/chat/embed/?website_id=c4ae10a3-f762-4968-b35a-c931caf62a96)***,*** [***Book a call***](https://calendly.com/ta-subscription-app-support/30min) *or at* [***support@tech-arms.io***](mailto:support@tech-arms.io)***.***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://subscriptions-docs.tech-arms.io/features/analytics/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
