> 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/analytics-and-reports/popup-bounce-rate.md).

# Popup Bounce Rate

See how often visitors leave your site while a popup is still on screen, so you can spot popups that get in the way.

Bounce rate shows how often visitors leave your site while one of your popups is still open, so you can tell whether a popup is adding friction and compare variants in an A/B test on the same number. It's already switched on for every Recart account, so there's nothing to set up — you just need a popup that has been live since tracking started.

### How bounce rate is calculated

Bounce rate is the percentage of sessions where the visitor left your site with the popup open on the page.

A session counts as a bounce when it ends while a full-screen step of the popup is showing:

* Teaser step
* Email or SMS step
* Gamified step, like a spin-to-win wheel
* Success step

These don't count as a bounce:

* The visitor closed the popup and then left
* The popup was minimized when the visitor left
* The popup never showed

{% hint style="info" %}
There's no timer. A visitor who leaves three seconds after the popup appears counts the same as one who browses for ten minutes and then leaves with it still open.
{% endhint %}

### Where to find bounce rate

#### Popup details page

1. Go to [**Opt-in Tools**](https://app.recart.com/optin-tools) and click the popup you want to check
2. In the **Opt-in performance** chart, open the **Bounce rate** tab

The number above the chart is the average for the time period you've selected, and the chart shows the daily breakdown.

<figure><img src="https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fgkeq4129ZghbTaqu4ibn%2Fbounce%20rate%20tab.png?alt=media&amp;token=2ae59265-7048-4987-9b35-a484ba53fb87" alt=""><figcaption></figcaption></figure>

#### A/B test results

1. Go to [**Opt-in Tools**](https://app.recart.com/optin-tools), then the [**Popup A/B Tests**](https://app.recart.com/optin-tools/experiments) tab
2. Click a test to open its results

Bounce rate is in the **Opt-in metrics** section of the **All results** table. Each variant shows its bounce rate as a percentage, along with how much it changed compared to the control. Lower is better, so a lower bounce rate shows in green. You will also find your bounce rate at the bottom of the interaction breakdown of the specific AB test you are viewing.&#x20;

<figure><img src="https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FQK861DC9Nj0vdgeTkFvF%2FScreenshot%202026-09-28%20at%2016.32.25.png?alt=media&amp;token=d0297bfe-26fe-465b-8af4-a58bba429d4c" alt=""><figcaption></figcaption></figure>

#### Through your AI assistant

If you've connected an AI assistant to Recart, bounce rate is included in your popup statistics. Ask something like "What's the bounce rate on my welcome popup this month?"

### How to read your bounce rate

* **Lower is better, but a bounce isn't always the popup's fault.** Bounce rate tells you a visitor left while the popup was open, not why. People leave for lots of reasons — they were only browsing, found what they needed, or got distracted — so treat it as one signal alongside your opt-in and conversion rates, not proof on its own that the popup drove visitors away
* **Expect numbers in the tens of percent.** Bounce rate counts every exit with the popup open, not just visitors who leave the moment it appears, so it's normal for it to sit well above single digits. It's most useful for comparing variants in an A/B test, or for watching one popup over time
* **Exit-intent and back-in-stock popups run high.** Exit-intent popups show to visitors who are already leaving, and back-in-stock popups appear on sold-out product pages. A high number on these reflects the situation rather than the popup, so focus on opt-in rate and conversion rate instead
* **Data starts from 7 September 2026.** Days before tracking started show no bounce rate, so a chart that covers earlier dates can make the first few weeks look like a sudden jump. Choose a time range that starts after that date

### Good to know

* **Nothing changes about your popups.** Bounce rate is a new number on reports you already use. It doesn't change how your popups trigger or display
* **A small number of exits can't be detected.** Some in-app browsers, and apps that are closed very quickly, don't signal that the visitor left, so a few bounces go uncounted. This affects every variant equally, so A/B comparisons stay fair — just read the exact number with a little caution
* **Want to know whether a popup helps revenue overall?** A holdout test compares showing the popup with showing nothing at all. See Popup Holdout Testing

If you have any questions, do not hesitate to contact the Recart Support team. We'd be happy to help!


---

# 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/analytics-and-reports/popup-bounce-rate.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.
