# Segment

## Segment management

This is where you create, edit and/or delete segments.

1. The first column displays the segments’ names.
2. The second column displays the segments’ technical IDs (present in the “TC AUDIENCE” cookie we use to store information about a segment).
3. The third column shows the percentage of visitors that are included in a segment.
4. The fourth column specifies the associated streams, using this segment.
5. The fifth column shows when was the last time a segment was modified.
6. The sixth column is where you edit or delete a segment, by clicking the pencil or the trash can.

![](/files/-LquLTDEmIWRnkp5AbLm)

## How to add multiple values in a segment?

Let’s say, for example, you want to match all users with ZIP code equals ‘75009’ or ‘92120’ or ‘94230’… and you realized you have more than 30 different values!

You can type one zip code per one, but it is long.

Or you can also copy and paste directly your values. However, you should **use a separator** between these values **;** or **|**

{% hint style="warning" %}
Don’t forget to add the separator behind the last value also to paste all your values.
{% endhint %}

{% hint style="warning" %}
You can paste-up to 1024 values in the segment
{% endhint %}

## How to segment on conversion items?

You can segment on conversion items, meaning products bought by users. 

First, you have to select '`conversion`' universe and define a condition for conversions, like '`conversion ID exists`' = users have at least 1 conversion. 

![](/files/wmlm9LGauKkm0uGJdke2)

Then the button 'ADD CONDITION' will appear, and you can define more conditions, including conditions for conversion items, select '**product**':

![](/files/5VNvNxT8rRoGjANi5qMV)

Then, you can easily segment on conversion items:

![](/files/qJdRhVI08odMVa75URxy)


---

# 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://community.commandersact.com/datacommander/user-manual/segment.md?ask=<question>
```

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.