> 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/re-engage.md).

# Re-engage

Explains Re-engage, the renamed and rebuilt Smart Trigger that re-displays a popup based on active browsing.

Smarter Popup Re-display — Built for Visitors Who Are Still Browsing

**Smart Trigger** has been renamed **Re-engage** and rebuilt with stronger intent signals.

The old version fired based on time alone. Re-engage is different: it only fires when a visitor is genuinely still browsing — they need to navigate to a new page first, and the timer counts active seconds on that new page. A much stronger signal of real intent.

### What's new

* Navigation to a new page is now required before Re-engage can fire
* The timer counts active time on the new page (resets on every page load)
* New popups have Re-engage **enabled by default** (1 attempt, 40s delayed display)
* Existing popups with Smart Trigger off stay off — no change.

### Where to make changes

Re-engage settings are in **Popup editor → Trigger settings**. You can configure max attempts, required navigations, delayed display, and scroll depth independently.

![HA\_re-engage](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2F9UqvmuzR9yjRu3g0ECGd%2FHA_re-engage.png?alt=media)

If you turned Smart Trigger off before, it's worth turning Re-engage back on — the navigation requirement makes re-display far less intrusive than before.

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/re-engage.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.