> 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/list-growth/popups/exit-intent-popup.md).
# Exit Intent Popup
Shows how to set up an Exit Intent Popup that appears as a visitor is about to leave your store.
An Exit Intent Popup appears just as a visitor is about to leave your site, grabbing their attention, giving you one last chance to grab their attention. When set up right, it can boost conversions and turn abandoning visitors into subscribers or even customers.
### How to Create an Exit Intent Popup
1. Go to [Opt-in Tools](https://app.recart.com/opt-in-tools) and click “**Create New**”
2. Select **Popup** as your type of opt-in tool type
3. Name your popup and choose your preferred settings.
4. On the General page under Settings, link your popup to an active welcome flow and set the trigger to “On user’s exit intent.”
5. Choose your exit trigger:
* Customer scrolls up fast
* Opens a new tab
* Cursor is leaving the viewport (desktop only)
6. Set behavior if another minimized popup is visible
* Open exit popup instead of the other popup’s minimized view
* Don’t open exit popup
7. Design your exit intent popup to suit your brand’s needs
8. **Save and activate** your Exit Intent Popup. It will now appear in your Opt-in Tools list.
### Some examples to get inspired by
If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md) 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/list-growth/popups/exit-intent-popup.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.
