> 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/popup-a-b-testing-page.md).

# A/B Testing Just Got Easier to Track

Announces the Popup A/B Tests tab, which shows all your popup experiments and results in one place.

We’ve upgraded the way you access and analyze your popup experiments.

You can now view all your **popup A/B tests in one place** — right from the new **Popup A/B Tests** tab inside the Recart dashboard.

No more digging through filters. No more guesswork. Just clean, visual results — right where you need them.

### Why this matters

Whether you’re testing a 10% vs 20% offer or comparing opt-in flows, A/B testing helps you find out what *actually works*. But until now, analyzing those results in Recart meant jumping between filters and exports. **That changes today!**

### What’s new

* **Dedicated A/B Testing Tab**

  Find all your popup experiments under one roof — active, scheduled, or completed.

![Popup AB tests list-](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fw8R3Jvd1KnHOB1iedekJ%2FPopup%2520AB%2520tests%2520list-.png?alt=media)

* **In-app Analytics Page**

  Each test now comes with visual metrics like opt-in rates, conversion rates, and revenue per visitor.

![AB test results page (1)-](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fp0HfsLAdapkZeslmDw5G%2FAB%2520test%2520results%2520page%2520\(1\)-.png?alt=media)

* **Variant Comparison & Funnel View**

  See how each popup performs across the full funnel, from impression to conversion.

![AB test results page funnel](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FVizeKf1lwkhbo6waVUwk%2FAB%2520test%2520results%2520page%2520funnel.png?alt=media)

* **Quick Search & Filters**

  Easily locate specific tests by name or status.

![Popup AB tests list filter-](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FGXK6TIhM3X0xOYT1lyRn%2FPopup%2520AB%2520tests%2520list%2520filter-.png?alt=media)

* **Smart Ordering**

  Tests are sorted by active → scheduled → ended, making it easy to track what’s live.

###

### Where to find it

Head to your Recart dashboard → [**Opt-in Tools**](https://app.recart.com/optin-tools) → [**Popup A/B Tests**](https://app.recart.com/optin-tools/experiments)

This is your new command center for analyzing what drives the highest engagement and revenue from your popups.

![Popup AB tests list-](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fw8R3Jvd1KnHOB1iedekJ%2FPopup%2520AB%2520tests%2520list-.png?alt=media)

#### **Coming soon:** Create new Popup A/B Tests directly from this page — stay tuned!

### Want the full how-to?

Check out the [full article](/list-growth/testing-and-scheduling/popup-a-b-testing.md) for step-by-step instructions on creating, managing, and analyzing popup tests.

### More ways to win with your popups

This update is part of our ongoing effort to make Recart the easiest, smartest place to grow your list and revenue.

*Last updated: October 2025*


---

# 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/popup-a-b-testing-page.md?ask=<question>&goal=<user_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.