> 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-bundle-metrics-daily-explore.md). # Subscription bundle metrics daily explore ## Overview Bundle-level performance (multi-product subscriptions). * Grain: **bundle combination per day** ## When to use * Identify top bundle combinations * Compare bundle churn rates * Analyze AOV by bundle ## Key dimensions & metrics | Field | Description | | --------------------------- | ------------------ | | Report Date | Date | | Bundle Key | Unique combo | | Product Titles | Included products | | Product Count | Number of products | | Is Large Bundle | >4 products | | Active Subscription Count | Active subs | | New Subscription Count | New subs | | Churned Subscription Count | Cancelled subs | | Bundle Churn Rate | Churn rate | | Avg Order Value | AOV | | Bundle Rank by Active Count | Popularity | ## Notes & caveats * Large bundles (5+) grouped into **LARGE\_BUNDLE** * Single-product subscriptions excluded ## 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 like Active EOM, LTV EOM) | | **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 **product combinations and cross-sell behavior**. | Product Metrics (Bundle Subscription Count), Bundle Metrics Daily (all bundle fields) | | **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, Category), Events Enriched (Event Type) | | **Provider** | The system managing subscriptions (Recharge, ChordOMS, CustomOMS). | Important context — **data availability and detail vary by provider**, which affects analysis. | All Explores (Provider filter present everywhere) | --- # 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-bundle-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.