> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/latest-news/introducing-popup-holdout-a-b-testing.md). # Introducing Popup Holdout A/B Testing Announces popup holdout testing, which measures a popup's real revenue impact against showing nothing at all. Prove the real impact of your popups Ever wondered whether your popup is actually driving revenue — or whether visitors would have converted anyway? With Recart's popup holdout test, you can find out. A holdout test is a type of A/B test where one variant is intentionally hidden from visitors. Instead of testing two different popup designs against each other, you're testing your popup against nothing at all. This gives you a clear, data-backed answer to one of the most common questions in conversion optimization: **is this popup making a difference?** ### How it works Traffic is split between your live popup and an invisible holdout variant. Recart attributes revenue to both groups using Shopify session data — so at the end of the test, you can directly compare revenue per visitor and conversion rate between the two groups. If your popup group outperforms the holdout, you have proof that your popup is driving incremental value. We recommend running the test for a minimum of 2–4 weeks to ensure reliable, statistically significant results. ### Getting started Holdout tests are set up with support from the Recart team. To get started, reach out to your dedicated CSM or contact us at [**support@recart.com**](mailto:support@recart.com). For full setup details, check out our help article: How to Run a Popup Holdout Test --- # 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://help.recart.com/latest-news/introducing-popup-holdout-a-b-testing.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.