> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/commerce-data-models/subscriptions/subscription-metrics-daily-explore.md). # Subscription metrics daily explore ## Overview Daily summary of subscription counts and flows. * Grain: **1 row per day** * Purpose: monitor **growth, churn, and overall health** ## When to use * Track subscription health on dashboards * Monitor churn trends over time * Evaluate net growth vs decline * Support executive-level reporting ## Key dimensions & metrics | Field | Description | | ---------------------------------- | ------------------------------------------------------------------------------- | | Report Date | Date of snapshot | | Active Count | Total active subscriptions | | New Count | Subscriptions created that day | | Churned Count | Subscriptions cancelled that day | | Reactivated Count | Previously cancelled → active | | Paused Count | Subscriptions paused that day | | Resumed Count | Subscriptions resumed that day | | Net New Count | New + Reactivated − Churned | | Churn Rate | Churned / previous day active | | Cancelled Cumulative Count | Running total cancellations | | Active Subscribers Count | Point-in-time count of customers with ≥1 active sub and no paused subs | | Partially Paused Subscribers Count | Point-in-time count of customers with both active AND paused subs | | Fully Paused Subscribers Count | Point-in-time count of customers with only paused subs | | Canceled Subscribers Count | Point-in-time count of customers whose only remaining subs are canceled | | Prepaid Subscribers Count | Point-in-time count of customers with ≥1 prepaid (non-gift) sub (ChordOMS only) | | Gifted Subscribers Count | Point-in-time count of customers currently receiving a gift sub (ChordOMS only) | | Gift Purchasers Count | Cumulative count of customers who have purchased a gift sub (ChordOMS only) | ## Example business questions * Daily churn trend (last 90 days) * Net growth trend over time * Monthly adds vs losses ## Notes & caveats * **Churn = cancellation only** (pauses excluded) * Paused/Resumed counts are **distinct subscription counts**, not event counts * Churn rate returns **NULL** if no previous-day active subscriptions * The subscriber counts above are **point-in-time (recalculated per report\_date)** * **Gift Purchasers Count is cumulative** — once a customer has bought a gift, they remain counted * **Prepaid, Gifted, and Gift Purchasers are ChordOMS-only** — Recharge and CustomOMS tenants will always show 0 ## Glossary | Term | What it Means | How to Interpret / Use | Where You’ll See It in Chord Analytics | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Active Subscription** | A subscription that is currently ongoing. Includes both fully active and paused subscriptions. | Use this to understand the **current size of your subscriber base**. Note that paused users are still counted. | Subscription Metrics Daily (Active Count), Subscriber Journey (Is Active Subscriber), Subscriber Journey Monthly (Is Active Subscriber EOM), Product & Bundle Explores (Active Subscription Count) | | **Churn / Churned** | A subscription that has been cancelled. Does not include pauses. | Represents **true customer loss**. Track this to understand retention issues. | Subscription Metrics Daily (Churned Count, Churn Rate), Subscriber Journey (Is Churned, Churn Count), Monthly (Is Churned EOM, Cancellations This Month), Events Enriched (Event Type = canceled), Movements (status\_cancelled) | | **Winback** | A subscriber who cancelled all subscriptions and later returned by subscribing again. | Indicates **successful re-engagement** after churn. | Subscriber Journey (Is Winback), Subscriber Journey Monthly (Has Reactivated By EOM) | | **Reactivation** | A previously cancelled subscription that becomes active again (subscription-level). | Measures **recovery of churned subscriptions**. | Subscription Metrics Daily (Reactivated Count), Movements (status\_reactivated), Events Enriched (Event Type = reactivated) | | **Net New** | Net change in subscriptions: New + Reactivated − Cancelled. | Indicates **overall growth vs decline**. | Subscription Metrics Daily (Net New Count) | | **LTV (Lifetime Value)** | Total revenue generated by a subscriber across all subscription orders. | Use to understand **customer value over time** and compare cohorts or segments. | Subscriber Journey (LTV Gross / Net Revenue), Subscriber Journey Monthly (LTV Gross Revenue EOM) | | **EOM (End of Month)** | Metrics calculated as of the last day of a month. | Used for **consistent month-over-month comparisons** (retention, LTV growth). | Subscriber Journey Monthly (all EOM fields) | | **Subscriber Category** | Mutually-exclusive current-state classification of a customer: active / partially\_paused / fully\_paused / canceled / never\_subscribed. | Use to segment customers by **current lifecycle state**. A reactivated customer returns to *active*. | Subscriber Journey, Subscriber Journey Monthly (current value) | | **Partially Paused** | Customer has at least one active AND at least one paused subscription simultaneously. | Identifies **at-risk users** scaling down but not fully churned. | Subscription Metrics Daily (Partially Paused Subscribers Count), Subscriber Journey (Subscriber Category) | | **Fully Paused** | Customer's only non-canceled subscriptions are paused. | A **softer churn signal** — these users may still reactivate. | Subscription Metrics Daily (Fully Paused Subscribers Count), Subscriber Journey (Subscriber Category) | | **Never Subscribed** | Customer exists in the system but has never had a subscription. | Useful for sizing **first-subscription / cross-sell opportunity**. | Subscriber Journey only | | **Prepaid Subscriber** | Customer has at least one prepaid (non-gift) subscription. | Identifies **upfront billing behavior**. ChordOMS only. | Subscription Metrics Daily (Prepaid Subscribers Count), Subscriber Journey (Is Prepaid Subscriber) | | **Gift Purchaser** | Customer has purchased one or more gift subscriptions for someone else. | Useful for **marketing segmentation and gifting behavior**. ChordOMS only. | Subscription Metrics Daily (Gift Purchasers Count — cumulative), Subscriber Journey (Is Gift Purchaser) | | **Gifted Subscriber** | Customer is receiving a gift subscription (someone else purchased it). | Useful for **conversion strategies** (turning recipients into paying users). ChordOMS only. | Subscription Metrics Daily (Gifted Subscribers Count), Subscriber Journey (Is Gifted Subscriber) | | **Solo Subscription** | A subscription that contains only one product. | Helps identify products that perform well **individually**. | Subscription Product Metrics Daily (Solo Subscription Count) | | **Bundle** | A subscription that contains two or more products. | Useful for analyzing **cross-sell and product combinations**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily | | **Movement** | Any change in a subscription’s state (created, cancelled, paused, resumed, reactivated, quantity/price change). | Use to understand **operational changes and trends** in subscriptions. | Subscription Movements Daily (Movement Type), Events Enriched (Event Type) | | **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability varies by provider**, impacting analysis. | All Explores | --- # 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.chord.co/model-your-data/commerce-data-models/subscriptions/subscription-metrics-daily-explore.md?ask=&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.