# Lists
Why they're useful:
* Customer control: Public lists let customers subscribe/unsubscribe themselves
* Preference management: Perfect for organizing contacts by interests or characteristics
* Targeted campaigns: Send relevant messages to specific segments instead of everyone
* Better engagement: More targeted = higher open rates and conversions
## How to Create a List
In order to create new lists:
1. Navigate to [Tags](https://manager.cymbal.co/tags):
2. Hit the "Create" button in the top right hand corner
3. Click "Create a List".
4. Give the list a name and description:
1. Select whether you want a "Public" or a "Private" list
2. Toggle whether to import ALL current contacts to this list or not
3. Click Create!
5. Created lists can be found in the Audience tab
***
## How to use a List in Cymbal:
Lists are powerful tools for organizing and targeting your audience effectively. How to use lists:
* Add contacts during CSV uploads and choose whether to make them public or private
* Use them in our targeting modal to send campaigns to specific groups
* Combine with other filters using AND/OR logic for precise targeting
* Access through our API using the list\_id (found in your Audience tab URL)
### Example: Using a List in a Form
1. Navigate to [Pages & Forms](https://manager.cymbal.co/pages)
2. Click into an existing form or create a new form
3. Once in the form select the form editor
4. Once the editor is open select "Lists" from the option bar
5. Select which "List" you'd like to sort new contacts who fill the form out into
6. All submissions from the form will be subscribed to your list. You can now use this list for more targeted marketing campaigns.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cymbal.co/help/segmentation/lists.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.