> 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/holiday-playbooks/bfcm/3-smarter-list-growth.md).

# BFCM #3 - Smarter List Growth Starts Now

Shows how to use Recart's tools, like button groups, to grow a list of subscribers more likely to convert for BFCM.

If you’re only thinking about collecting more subscribers, you’re missing half the equation. BFCM success starts with the *right* subscribers — the ones who are more likely to convert. Here’s how to optimize list growth using Recart’s built-in tools:

### 1. Use Button Groups to Capture Preferences

Ask smart questions like “What are you shopping for today?” or “Who are you buying for?” right inside your popup. Use responses to segment your list and personalize flows.

[Learn more about Button Groups here.](/list-growth/popups/capture-preferences-on-the-teaser-step.md)

### 2. Auto-Apply Discounts for Faster Signups

Skip the manual copy-paste. Auto-apply discounts right at your success step of your popup. Reduce friction and improve conversion from popup to purchase.

[Learn more about Customizing your CTA here.](/list-growth/popups/customizing-your-cta-button-in-popups.md)

### 3. Clean Your List While You Grow

Use filters to exclude disengaged subscribers or test popups that only show for new traffic. Better list = better ROI.

[Learn more about Segmentation here.](/sms/subscribers-and-lists/sms-segmentation-conditions-and-filters.md)

### 4. A/B Test Popup Variants

Test popup variations (design, offer, timing) to see what drives the best results. Use what works to double down before peak season.

[Learn more about A/B Testing here.](/list-growth/testing-and-scheduling/popup-a-b-testing.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/holiday-playbooks/bfcm/3-smarter-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.