> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/analytics/overview/sitewide-analytics/performance-p-and-l.md). # Performance P\&L ### **Overview** The **Performance P\&L** is a unified store-level performance dashboard with the following features: * Recent Performance Snapshot: View recent performance snapshots and all data observed since installation. * Compare PPV, RPV, CVR, AOV, and Gross Margin and more. * Historic Performance Over Time: Trend metrics over time with weekly or monthly grouping. * Profit and Loss Details: View full P\&L in table form with profit and revenue breakdowns. * Filter capabilities: Filter by device, visitor type, channel, z-score, country, and landing page. #### Filter Details * **Matched to Session:** Orders where checkout journey was directly observed via Intelligems script. * **All Orders:** Includes POS, subscriptions, and non-web orders. Orders that didn’t reach checkout in any way. By default, our views are filtered to Orders Matched to Session in order to enable visitor-based metrics as well as visitor-based filters The remaining filters are consistent in definition and operation with [filters in Experiment Analytics](/analytics/overview/experiment-analytics/filters.md)
#### Metric Definitions: Metric definitions are consistent between Experiment Analytics and Sitewide Analytics. Details around specific metrics can be found [here](/analytics/overview/experiment-analytics/metric-definitions.md). #### --- # 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.intelligems.io/analytics/overview/sitewide-analytics/performance-p-and-l.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.