> For the complete documentation index, see [llms.txt](https://docs.2checkout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.2checkout.com/subscriptions/subscriptions/subscription-reporting/churn-overview-report.md).

# Churn Overview Report

## Overview

***

The Churn Overview Report shows how many subscriptions you lost in a selected period, how much recurring revenue they represented, why and how they ended, and which active subscriptions are at risk of churning next. It is built on Snowflake data and embedded directly in your Control Panel.

A subscription is considered **churned** when it ends with a churn date in the selected interval — either **cancelled**, or **expired without renewal** at the end of its grace period. Subscriptions that are still active or still in their grace period are not churn; if they show an early-warning signal, they appear as **at risk** instead.

## Benefits

***

* Know how many subscriptions and how much monthly recurring revenue (MRR) you lost in any period, and how that compares with the previous period and the same period last year
* Distinguish voluntary churn (the shopper or you ended the subscription) from involuntary churn (the renewal failed without a decision to leave)
* See the churn path — the sequence of events that led to churn — and the churn reason, so each segment can get the right intervention
* Act before the loss is final: export at-risk subscriptions (auto-renewal switched off, or previously switched off and back on) for save campaigns
* Export churned subscriptions for win-back and refund-recovery campaigns

## Availability

***

The report is available to all subscription merchants with the following packages: 2Subscribe, 2Monetize, and 4Enterprise (if subscription capabilities are enabled).

## Scope

***

* **Ecommerce subscriptions only.** Partner subscriptions are not included.
* **Fraud orders are excluded** from the report entirely.
* **Test, trial / zero-value, and lifetime subscriptions** are excluded by default. Each can be included using the report options (see [Filters and report options](#filters-and-report-options)).

## Workflow

***

1. Log in to your [Merchant Control Panel](https://secure.2checkout.com/cpanel/).
2. Navigate to **Reports center** > **Main reports** > **Subscription reports** and open the churn report.
3. Select the **Reporting interval**. The report opens on the last full month by default.
4. Optionally narrow the results with the filters and report options described below.
5. Review the **Subscriptions at interval start** and **Churn** cards, then use the breakdown chart to see churn by **churn path**, **churn reason**, or **billing cycle**.
6. Use **Export CSV** to download churned and at-risk subscriptions for your campaigns.
7. Scroll to the **Legend** at the bottom of the report for the definition of every metric and filter.

## Filters and report options

***

* **Reporting interval** — the period in which churn dates are counted. Use fixed date ranges (for example, one calendar month). Relative presets such as "Last 2 months" form one combined window, not a month-by-month series, and subscriptions at interval start are measured at the start of that window.
* **Churn type** — voluntary or involuntary.
* **Churn reason** — the reason recorded for the churn (see [Churn reason](#churn-reason)).
* **Expiration date** — filters churn by billing-cycle end date. Use it to put this report on the same basis as the [Renewal Performance Report](https://docs.2checkout.com/subscriptions/subscriptions/subscription-reporting/renewal-performance-report.md). Churn rate is not 1 − renewal rate, because the denominators differ, but the two should be in the same range.
* **Product**, **Country**, **Payment method**, **Billing cycle length** — segment filters.

Product, Country, Payment method, and Billing cycle length apply to every number in the report. Churn type and Churn reason narrow the churned counts and the at-risk lists only; Subscriptions at interval start stays the total, so the voluntary and involuntary rates add up to the total rate.

**Report options** (all checked by default):

* **Exclude test subscriptions** — uncheck to include test subscriptions everywhere.
* **Exclude trials and 0-value subscriptions** — trials and $0 subscriptions (free trials, card-validity checks) churn at very different rates and would distort the churn rate. Uncheck to include them.
* **Exclude lifetime subscriptions** — lifetime subscriptions never come up for renewal and can only churn by cancellation, so including them dilutes the churn rate. Uncheck to add them to both Subscriptions at interval start and churn.

## Metrics

***

### Subscriptions at interval start

All subscriptions that were active or past due (in their grace period) at the start of the interval, including any that churned later in the interval. The card also shows **MRR at start** — the recurring-revenue value of these subscriptions — which is the denominator for the MRR churn rate.

### Churn card

One card, two columns:

* **Subscriptions** — the number of subscriptions churned in the interval and the **churn rate** (churned subscriptions ÷ subscriptions at interval start).
* **MRR** — the recurring revenue of those same churned subscriptions and the **MRR churn rate** (churned MRR ÷ MRR at interval start). It is calculated as its own ratio, because churned subscriptions don't carry the same average value as the overall base.

Both columns show the voluntary / involuntary split, which always adds up to the column total.

**MRR** is the monthly value of each subscription, based on its next-renewal net price (if that price is missing, the last or initial order price is used), divided by the billing-cycle length in months and converted to USD.

### Comparison indicators

Each card compares against the previous interval of the same length and against the same interval one year earlier. ▲/▼ show the direction of change; green/red show whether the change is favorable — more subscriptions at start is good, more churn is bad.

### Churn date

* A **cancellation** is dated on the day it was cancelled.
* An **expiration** is dated at the end of the grace period (for products without a grace period, at the billing-cycle end), so expired-churn counts are final when reported.
* A subscription that renews late after being counted is removed from churn, so past numbers can drop slightly.

## Voluntary and involuntary churn

***

* **Voluntary** — the shopper or the vendor ended the subscription: cancellations, auto-renewal switched off by the shopper or the vendor, a declined retention offer, a removed card or payment agreement, refunds, and chargebacks.
* **Involuntary** — the renewal failed without a decision to leave: failed renewal payments, permanently declined cards, auto-renewal switched off by the system, currency, country, or product no longer available, and contracts that ended.

## Churn path

***

The sequence of events that led to churn — for example, "auto-renewal switched off, then expired", "cancelled immediately by the shopper", or "refunded — cancelled via refund". Churn path is the recommended lead dimension for campaign targeting, because each path points to a different action. Several different reasons can share one path.

Segments marked with **\*** are provisional: the source of an auto-renewal change is not always passed to the report yet, so their size may shrink as attribution improves.

## Churn reason

***

Why the subscription ended, as recorded on the subscription's own event history: the reason recorded on its last cancellation or auto-renewal-off event within its final 2 billing cycles — the most recent one wins. Reasons come from a fixed list covering shopper survey answers, payment and wallet events, and vendor actions, grouped into voluntary and involuntary. When nothing was recorded, the subscription shows **No reason given** (common with older API integrations).

To collect more churn reasons from your shoppers, see [How to collect churn reasons](https://docs.2checkout.com/subscriptions/subscriptions/subscription-reporting/how-to-collect-churn-reasons.md).

## At-risk subscriptions

***

Active subscriptions that haven't churned but show an early-warning signal. They are counted in Subscriptions at interval start, never in churn, and are always the full current list, whatever interval is selected.

* **At risk — AR off** — auto-renewal is off, or the subscription is past due and still in its grace period. It will lapse unless renewed.
* **At risk — reactivated before** — auto-renewal was switched off in the last 24 months and later switched back on: a demonstrated risk, even though the subscription is currently healthy.

## Export

***

**Export CSV** downloads one file covering all four record types, with the customer email for campaign upload and a **Record type** column to split the audience:

| Record type                  | Meaning                                          | Suggested action                     |
| ---------------------------- | ------------------------------------------------ | ------------------------------------ |
| Churned                      | Churned in the interval                          | Win-back / dunning follow-up         |
| Churned — refund             | Churned through a refund                         | Refund recovery (not a dunning send) |
| At risk — AR off             | Auto-renewal off, still active                   | Save campaign before expiry          |
| At risk — reactivated before | Previously switched auto-renewal off and back on | Proactive retention                  |

The dashboard shows a summary of the export — row counts per record type — instead of the full listing.

## FAQs

<details>

<summary>Why doesn't turning off auto-renewal count as churn?</summary>

The subscription stays active until the end of its billing cycle and can still be renewed. It is shown as **At risk — AR off** so you can target it with a save campaign, and is counted as churn only if it reaches the end of its grace period without renewing.

</details>

<details>

<summary>Why does the Churn Overview Report show different numbers than the Renewal Performance Report?</summary>

The two reports use different anchors and denominators. This report counts churn by churn date against subscriptions active at the start of the interval; the Renewal Performance Report looks at subscriptions whose expiration date falls in the interval. Use the **Expiration date** filter to put both reports on the same period basis; the results should then be in the same range, but churn rate is not expected to equal 1 − renewal rate.

</details>

<details>

<summary>Are partner subscriptions included?</summary>

No. The report covers ecommerce subscriptions only.

</details>

<details>

<summary>Are trial and lifetime subscriptions included?</summary>

Not by default. Uncheck **Exclude trials and 0-value subscriptions** or **Exclude lifetime subscriptions** to include them.

</details>

<details>

<summary>Why can last month's churn number change slightly?</summary>

A subscription that renews late, after being counted as churned, is removed from churn.

</details>

<details>

<summary>Do renewal promotions or quantity reductions count as churn?</summary>

No. Only subscriptions that were cancelled or expired without renewal are churn.

</details>


---

# 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://docs.2checkout.com/subscriptions/subscriptions/subscription-reporting/churn-overview-report.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.
