> 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/capture-preferences-on-the-teaser-step.md).

# Capture Preferences on the Teaser Step

Explains how to add button groups to a popup's Teaser step so visitors share a preference before opting in.

Add **button groups** to the **Teaser step** of your Recart popups. Instead of a single “Confirm” button, you can give visitors multiple clickable options — letting them choose what they’re most interested in before they opt in.

Whether it’s **product type**, **gender**, **discount preference**, or any other trait, this feature helps you capture relevant data early — without disrupting the opt-in flow.

### Why this matters

Asking simple questions like “What are you shopping for today?” or “Which offer do you prefer?” right in the teaser builds **early engagement** and unlocks **better targeting** later.

#### Here’s what you can do with it:

* **Customize your Teaser** with multiple CTAs (like “Men’s / Women’s” or “10% Off / Free Shipping”)
* **Learn user intent upfront**, before they enter their phone number
* **Track responses** as subscriber data for future flows and campaigns
* **Style and configure easily** — no code or workarounds required

Every button tap counts as a Teaser confirmation, and the selected preference is saved to that subscriber’s profile — so you can use it later to personalize your messaging.

### How to try it out

1. Open any popup → go to the **Teaser** step
2. Click **“Add Button Group”**

![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FWwprStAeLEyi9BuZi7nx%2FOpt-in%2520tool%2520editor%2520\(6\).png?alt=media)

3. Link them to a Subscriber detail

![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FUfEgjQDndzWREO4w3icE%2FOpt-in%2520tool%2520editor%2520\(7\)Subscriber.png?alt=media)

4. Add your button options (e.g. size, interest, category)

![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FR0lDuk7EcyjgizWlP6YZ%2FOpt-in%2520tool%2520editor%2520\(7\)Options.png?alt=media) ![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FyV0zc3oTmJZmqeWQVsjr%2FOpt-in%2520tool%2520editor%2520\(2\)_.png?alt=media)

5. Customize style, size, spacing, and layout
6. Remove the default buttons if you only want a quiz-style look

![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fwqq48PKs7THgJ3v9mu8r%2FOpt-in%2520tool%2520editor%2520\(3\).png?alt=media)

The editor gives full control over styling — font, button color, border radius, drop shadow, and more — so it fits seamlessly into your brand.


---

# 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/capture-preferences-on-the-teaser-step.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.