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

# List Growth

Covers the opt-in tools that capture SMS and email subscribers, from popups to keywords, and how to test and schedule them.

Every message Recart sends starts with someone who chose to hear from you. This section covers the tools that capture subscribers — popups, landing pages, embedded forms and keywords — and how to test and improve what they collect.

### Start here

* [Opt-in Tools - Getting Started](/list-growth/opt-in-tools-getting-started.md) — how Recart's opt-in tools fit together

### Popups

The opt-in tool most stores start with.

* [Opt-in Tools - Popup](/list-growth/popups/welcome-popup.md)
* [Opt-in Tools - Popup Best Practices](/list-growth/popups/opt-in-tools-popup-best-practices.md)
* [Customize and Manage Your Popup](/list-growth/popups/customize-and-manage-your-popup.md)

More on popups in the menu.

### Other Opt-in Tools

Landing pages, embedded forms, SMS keywords and social.

* [Opt-in Tools - Landing Page](/list-growth/other-opt-in-tools/landing-page-opt-in-tool.md)
* [Opt-in Tools - Embedded Form](/list-growth/other-opt-in-tools/embedded-form-opt-in-tool.md)
* [Opt-in Tools - SMS Keywords](/list-growth/other-opt-in-tools/opt-in-tools-sms-keywords.md)

More opt-in tools in the menu.

### Testing & Scheduling

Prove what works, and control when it shows.

* [Popup A/B Testing](/list-growth/testing-and-scheduling/popup-a-b-testing.md)
* [Popup Holdout Testing](/list-growth/testing-and-scheduling/how-to-run-a-popup-holdout-test.md)
* [Schedule Your Opt-In Tools](/list-growth/testing-and-scheduling/scheduling-opt-ins.md)

Opt-in performance data lives in [Analytics & Reports](/analytics-and-reports.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://help.recart.com/list-growth.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.