> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/reporting-and-analytics/analytics-workspace.md). # Analytics Workspace The **Analytics** area (left navigation → **Analytics**) is where you go to understand how your store is performing and where customers run into friction. It is organized into five tabs, each answering a different question: * **Overview** — what's happening right now: revenue, subscriptions, journey conversion, and the signals worth acting on. * **Journeys & Funnels** — where people drop off inside a given journey, and for whom. * **Session Explorer** — the individual sessions behind the numbers, with a full step-by-step timeline for any one of them. * **Retention** — the cancellation funnel: how many save attempts succeed and what's driving the churn that doesn't. * **Experiments** — A/B variant comparison with lift and statistical significance. Most tabs share a **date-range** selector (last 7, 30, 90, or 365 days) in the top-right that scopes everything on the page.
The Analytics workspace Overview tab: an insights-and-anomalies strip, KPI cards for MRR, journey conversion, active subscriptions, and churn with sparklines, a revenue-trend chart, and a conversion funnel

The Analytics workspace — the Overview tab, with auto-surfaced insights up top, KPI trends, and a conversion funnel; the Journeys & Funnels, Session Explorer, Retention, and Experiments tabs go deeper.

All figures are drawn from real order and journey-session data. Internal preview sessions (admin "view as" runs) and sessions an administrator has explicitly excluded from analytics are left out, so the numbers reflect genuine customer activity. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/reporting-and-analytics/analytics-workspace.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.