> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/exit-intent.md).

# Exit Intent

Show a message when a visitor moves to leave your Action Page. Set the exit intent title, body, and image in the Anedot Page Builder's Workflows group.

**Exit intent** shows a message to visitors as they move to leave your Action Page, before they're gone. Use it to remind supporters why their action matters and invite them back to the form. You'll find it in the Page Builder under **Workflows > Exit intent**. Exit intent is available on Donation Pages, Event Pages, and Lead Pages. This article covers how to set it up and what visitors see.

## Before You Begin

* To save changes, you need **Action Pages: Edit permissions**.

## Open Exit Intent

To open Exit intent:

1. Go to **Action Pages > Pages**.
2. Click the name of the page you want to edit.
3. Select **Workflows > Exit intent**.

You can also open it from **Workflows > Donor journey**, which shows exit intent and your other workflows in order.

## Set Up the Message

In the **Message** section, add any of the following:

* **Title:** The heading of the message.
* **Body:** A message that encourages visitors to stay.
* **Image:** An image or GIF to show with the message. Choose one from your image library or upload a new one.

There's no separate on or off switch. Exit intent turns on when the message has a title, a body, or an image. To turn it off, clear all three.

When you're done, click **Save**.

## What Visitors See

When a visitor moves their pointer off the top of the page, such as toward the browser's tabs or address bar, a message window opens with your title, image, and body. The button at the bottom returns them to the page:

| Page Type      | Button Text              |
| -------------- | ------------------------ |
| Donation Pages | Complete your donation   |
| Event Pages    | Continue to checkout     |
| Lead Pages     | Continue your submission |

Each visitor sees the message once per visit. If they come back to the same page after about 30 minutes, they can see it again.

Exit intent doesn't appear in the Page Builder preview, so moving between the preview and the editor won't open it. To see it, open your live page and move your pointer off the top of the window.

## Pair Exit Intent With Abandoned Actions

Exit intent works best with a follow-up. If a visitor closes the message and leaves anyway, [Abandoned Actions](/action-pages/page-builder/abandoned-actions.md) can send them a recovery email when they've entered an email address. If Abandoned Actions is off, the Donor journey shows a reminder to add it.

## Related Articles

* [Page Builder Overview](/action-pages/page-builder.md)
* [Abandoned Actions](/action-pages/page-builder/abandoned-actions.md)
* [Upsells and Upgrades](/action-pages/page-builder/upsells-and-upgrades.md)
* [Content and Layout](/action-pages/page-builder/content-and-layout.md)
* [Branding](/action-pages/page-builder/branding.md)


---

# 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://docs.anedot.com/action-pages/page-builder/exit-intent.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.