> 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.md).

# Popups

Covers popup types, targeting and display rules, and how to match a popup's design to your brand.

Everything you need to know about popups — the opt-in tool most stores start with. Choose a type, set the targeting and display rules, then make it look like your brand.

### Choose a popup type

* [Welcome Popup](/list-growth/popups/welcome-popup.md) — the standard popup
* [OneClick Popup](/list-growth/popups/oneclick-popup.md) — one-click subscription experience
* [Exit Intent Popup](/list-growth/popups/exit-intent-popup.md) — triggered as a visitor leaves

### Set it up

* [In-Popup Confirmation](/list-growth/popups/opt-in-tools-in-popup-confirmation.md) — what a subscriber sees once they sign up
* [Customize and Manage](/list-growth/popups/customize-and-manage-your-popup.md) — design, targeting and display rules
* [Layout and Containers](/list-growth/popups/layout-and-containers.md) — arrange, add and remove elements to build your own layout
* [Engagement Tools](/list-growth/popups/engagement-tools.md) — add a game like Spin the Wheel, Plinko or Mystery Box to your Teaser step
* [Customize with CSS](/list-growth/popups/customizing-your-popup-with-css.md) — your options are endless
* [Capture Preferences on the Teaser Step](/list-growth/popups/capture-preferences-on-the-teaser-step.md) — ask what shoppers are interested in before they opt in
* [Update Your Discount](/list-growth/popups/updating-your-popup-discount.md) — change the offer without rebuilding the popup
* [Customize Your CTA Button](/list-growth/popups/customizing-your-cta-button-in-popups.md) — choose your button behaviour
* [Best Practices](/list-growth/popups/opt-in-tools-popup-best-practices.md) — what makes a popup convert
* [Preview](/list-growth/popups/opt-in-tools-popup-preview.md) — test it before it goes live

### Popup Settings

* [Visitor Targeting](/list-growth/popups/visitor-targeting.md) — show different popups to new visitors and existing subscribers
* [Target Popups by Klaviyo Segment](/list-growth/popups/target-popups-by-klaviyo-segment.md) — show a popup only to visitors in a Klaviyo segment
* [Re-engage](/list-growth/popups/re-engage.md) — show a popup again to visitors who closed it but kept browsing
* [Cooldown and Frequency Limits](/list-growth/popups/cooldown-and-frequency-limits.md) — control how often a popup can show
* [Email Typo Validation](/list-growth/popups/email-typo-validation.md) — catch mistyped email addresses at signup


---

# 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.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.
