> 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/experiments.md). # Experiments The **Experiments** tab compares the variants of an A/B experiment so you can tell what to ship. ## Choosing an experiment Use the **experiment** picker in the top-right. It defaults to a running experiment if one exists. The header summarizes the experiment's goal (its primary metric — completion rate or save rate), total sessions, and status, along with a **significance** badge: * **Significant** — the difference is statistically significant (with the p-value shown). * **Trending** — a difference is emerging but isn't significant yet. * **Not enough data** — too few sessions or conversions to call. ## Comparing variants Two cards show **Variant A (Control)** and **Variant B** side by side: the variant's rate on the primary metric, its sample size, and the underlying counts (completed/abandoned for completion-rate experiments, or saved/cancelled for save-rate experiments). When the result is at least trending, the leading variant is marked as the winner. The **Verdict** explains the result in plain language, including the relative **lift** of Variant B versus A and whether the experiment is significant yet or should keep running. If no experiments exist, the tab invites you to create one on a journey. --- # 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/experiments.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.