# Segments

## Overview

Segments app manages segments of audiences created by the data available in **CDP 365** or combined with external data. 

It includes 2 tabs which are **Segments** and **Computation Histories**.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdxYmT_Bma9zzrQmGPcGkBzxSTcd7Z1iuVTUrcGwuF-jYqfvn-XiuiS02B-dIiZUjWDlFxEYZIck-G2LfEwGPuJm2bOYO2bI3Q2uzUDRq8f4O4GYv1z9k3LOmAzDq9-SoE6qxaCQdkxsl7e9M-rr7QxtgHs?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

## Segments tab

The tab provides segment creation and management.

### Create a Segment

Following these steps to create a **Segment**:

1. Click <img src="/files/KF2MllyTbydhoUDL6Mnm" alt="" data-size="line">&#x20;
2. Select a type of segment&#x20;
3. Set the configure of segment
4. Click **Save**
5. After clicking Save, a pop-up will appear confirming whether to build the segment right away.
   * If it is agreed upon, the segment will be built immediately.&#x20;
   * Otherwise, the segment will build according to the setting.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeVpNUqd5JewGFXDOwVxRwZVI4_3-PhsMYCXQPBW9oG0Hyeugvv5cseVzjZK_k91fJaLcKog4ZE1g-JB4SMsxZkQklglWTQs170cciosK9iFkl_T4oyKUW8Cy1D8Mrrj2uuUtKngBBNZYHEscaegqLmlXMN?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcBjfBSun6H39rnCctfDkhgN84RlpuP6wmcuCCnAEIyx5bvJwyKKpAvhj2-7shJtTwscPGUhiKC24OOQKnlrdImX2DKSmGRxa2FEwLjXH7ncJqFTmXzV78l6E_HjeGfw9uA_XgNUsO6opn8t_m_rAmeUhOw?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

#### Segment types

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfGQfpNGDJir6b2cJrdY1mAdTZ3UB71sssRCkt4oICH2R7WNgQTM0ZF59-ywO6W8vwngCGT1wdQYqPjQQhv_fZ5TLK2xMyTwBlEsyIKdp3r0D9q-1UJVJHMj_MffaTfbj8V-1X4Kk0DuQT_V0UEweaeIjU?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

There are 2 groups of segments based on the types of audiences:&#x20;

<table><thead><tr><th width="160.33333333333331">Audience type</th><th width="221">Segment type</th><th>Description </th></tr></thead><tbody><tr><td>Customers</td><td>Customer Segment</td><td>Create a segment based on the data available in the <strong>Customer</strong> business object</td></tr><tr><td></td><td>Customers and Segment</td><td><p>Include 2 steps: </p><ul><li>Upload data to the Customer business object </li><li>Create the segment  </li></ul></td></tr><tr><td>Visitors</td><td>Visitor Segment</td><td>Create a segment based on the data available in the <strong>Visitor</strong> business object </td></tr><tr><td></td><td>Visitors and Segment</td><td><p>Include 2 steps: </p><ul><li>Upload data to the Visitor business object </li><li>Create the segment  </li></ul></td></tr></tbody></table>

#### The configuration of a segment

***General information***&#x20;

Audience name: the name of the segment&#x20;

Description: describe the segment

***Update segment***

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe_NcaFm1Q_IctQ5TTR21-n1PrxuNLyqwVVktifH0x7WxpLruSKvNvuEdz6dJrw3BzVxLChE3XfstA7oKZit6oGZ6yjjY-8FcxiO8hZJKRcCdcDzi_362NwPUFXHS4ZQ1z5BSa4-Ssv1DHCL23EbvmfrBQD?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

Does the segment update?

<table><thead><tr><th width="179">Update Segment</th><th>Description</th></tr></thead><tbody><tr><td>Static </td><td>The segment is built only once corresponding to the setting.</td></tr><tr><td>Dynamic </td><td>The segment is built and updated by a schedule corresponding to the setting.</td></tr></tbody></table>

> Create a customer segment of those who shopped 3 times per week, for example, the result was 2,000 customers after creating.&#x20;
>
> * Static segment, the segment was built only once and the result was 2,000 customers.
> * Dynamic segment, the segment was updated and the result changed over the computation schedules.

#### ***Member input method*** <a href="#member-input-method" id="member-input-method"></a>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe9BO7XgGAFNNqIehZ5eSGsU8jeMbSZ2QoMZtv97wrvejz0JHePHRwBaAImVZqjqvJ7Ck9aHi5tStS0ssZjWDfr-BUHPcFYMtCOnFvRwU-w0xwZy1TJIjuYn6HgRatCzZjSvD8EFoXrBgMq6ym1tm1OpLA?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

What are the characteristics of the audience in a segment?

<table><thead><tr><th width="221">Member input method</th><th>Description</th></tr></thead><tbody><tr><td><strong>Conditions</strong></td><td><p>Based on the data available in CDP 365</p><ul><li>Perform event: filter audiences based on the interactions/events of customers or visitors. For example, build a segment for customers who have more than 3 successful orders this month. </li><li>Have attribute: filter audiences based on the attributes of the customer or visitor business objects. For example, build a segment for visitors who locate in Ho Chi Minh city.</li></ul></td></tr><tr><td><strong>Matching file</strong></td><td>Filter audiences based on the combination of CDP 365's data and uploaded data. </td></tr><tr><td><strong>Empty segment</strong></td><td>Create an empty-value segment to be updated from marketing campaign scenarios in Customer Journeys.</td></tr><tr><td><strong>Unsubscribe segment</strong></td><td>Audiences are the people who unsubscribe from emails.</td></tr></tbody></table>

#### ***Segment Member***

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcwmOsK4FJs6IOAbNu4CtKWqpv5PBlTfN8ayX1-4bm1Sp0ph1q0XoMzeWoRH7H6TiXmy0iqhW58NZSJh8XWsHir35dbCZRHPhkezzhinYVwXLqqngSUL_kJcax2Or_S-STQ5FlLRQo_hFEo9By70tBBPd9F?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

Limit the number of audiences in a segment.

<table><thead><tr><th width="191">Segment member</th><th>Description</th></tr></thead><tbody><tr><td>No Limit</td><td>An unlimited number of members in the segment.</td></tr><tr><td>Limit</td><td><p>Limit the number of member in the segment, by:</p><ul><li>Get top of: the number of member</li><li>Sort by: attribute of the customer or visitor business object</li><li>Sort order: ascending/descending</li></ul></td></tr></tbody></table>

***Notification Setup***

<figure><img src="/files/r1K4nVLIlc2uksD9qYI2" alt=""><figcaption></figcaption></figure>

* **Account**: set up account(s) receiving notification
* **Notify options**: the notification can be sent by email or pushed notification when the computation complete success or fail

#### ***Forecast***&#x20;

The feature gives a statistical report of the to-be-built segment which includes

* The number of members the segment could have
* The percentage of the members in the segment compared to the total number of customers or visitors in the CDP 365.&#x20;

<figure><img src="/files/q5tTCDWJ4F4QBMNjd8zu" alt=""><figcaption></figcaption></figure>

#### ***Version History***&#x20;

The feature allows not only viewing details of edit history but also restoring a specific version.&#x20;

Each version is recorded after a time of saving.

<figure><img src="/files/I8PXJyj8rhfm982XhBj6" alt=""><figcaption></figcaption></figure>

### Check segments

After creating a segment, check at data table of Segments tab.&#x20;

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcgvczq-gGjaViiQeaOvRz-xpGT8UTj1DrpCQlzSDReznVJva2miaW9V82riXJW7tjSRaM9tAJGDVlMcGM-fxp9ubAnPRth-VHc0K3YjG76ksxv_2WSTBClMD0td2qgPKYn8YTJsN7xhgJ9yM8F_tsIS9Ng?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

#### Action with segment

Select at least one segment, click ACTION to adjust the status of a segment

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcSGZBHOgCj8_U6IhMPj7cWD1QhFyLgHDO_psyae9NYt-BLlC_XH-vFuwWNfJaR5V13CEd4f7ctZdVO-a8ENyuGCtZHv4KIjguAne22uN_iy0SCI0iyELWLslJu9xtKQwNUZYE8B-JGMabKPMh2ASEEhctm?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="147">Action</th><th>Description</th></tr></thead><tbody><tr><td>Enable</td><td><ul><li>When enabled, the segment status change to ENABLE</li><li>Enable means the segment is enabled to update its data</li><li>After a set time not being used, the segment automatically changes to disable.</li></ul></td></tr><tr><td>Disable</td><td><ul><li>When disabled, the segment status change to DISABLE</li><li>Disable means the segment is disabled to update its data</li><li>After a set time not being used, the segment automatically changes to archive.</li></ul></td></tr><tr><td>Archive</td><td><ul><li>When archived, the segment status change to ARCHIVE </li><li>The segment is unavailable to search or use in other apps. Using filter by the archive status to find it</li><li>After a set time not being used, the segment is automatically deleted. </li></ul></td></tr><tr><td>Recover</td><td><ul><li>Restore archived segments</li><li>During recovery, can't interact with the segment. </li></ul></td></tr><tr><td>Make a copy</td><td><ul><li>If demanding creates a segment with similar condition settings to an existing segment, use <strong>Make a copy</strong></li><li>Make a copy of the segment by following steps</li></ul><ol><li>Select an original segment </li><li>Select Make a copy in Action </li><li><strong>Name and confirm</strong> creating a copy </li><li>Adjust conditions </li><li>Save</li></ol></td></tr></tbody></table>

{% hint style="warning" %}
Note: The copy is only saved and calculated when you complete the step of clicking SAVE
{% endhint %}

#### Label

Label helps management of segments more productive.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe-mRo7py9A8SjXVsnntnVYDGIav5ZLkZkbdtccDvWX7MPBE-I-z6Yh7OZQ6KSmMGCtBUU49w30UMDEGi0rlbxlKTnYrGmNBOq5N0A5T6Z8ES31C4GmiLhtMtECPEyYrW1Y7RhCr4HC0dNo2i6InId8uFxD?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

#### Status of a Segment

Segment status can be changed by switching the toggle of Status.&#x20;

It indicates the status of a segment.

* ![](/files/2SzTr3PYZUe9gKtG1X4u) means the segment status is 'Disable'. Turn on to force the segment to be built immediately.
* ![](/files/zSMljC33nOko3pRYLd7O) means the segment status is 'Enable'. Turn off to disable the computation ability of a segment.&#x20;

#### Name

By hovering over the name of a segment could have functions of&#x20;

* Go to the detailed settings of a segment, click ![](/files/YdfGHUXRuy2fD4RLHrxg)
* Explore the member of a segment, click ![](/files/j409aTkIatdoW9W39PAd)
* Rename the segment, click ![](/files/Nio2UQaYD2ep4snoadmp)

<figure><img src="/files/lTSt4BrpYTkqOHb8AIo6" alt=""><figcaption><p>Segment name</p></figcaption></figure>

#### Update method

It indicates the type of update method that the segment is applied.&#x20;

#### Segment status and Last computation status

The computation of a segment includes 3 steps

* Step 1: check the resources in CDP 365 to compute the segment
* Step 2: compute members of the segment&#x20;
* Step 3: store the data of the segment in CDP 365

<table><thead><tr><th width="237">Last computation status</th><th>Description</th></tr></thead><tbody><tr><td>Waiting Initial</td><td>The segment is waiting for the computation schedule</td></tr><tr><td>Waiting</td><td>The segment is in step 1</td></tr><tr><td>Computing</td><td>The segment is in step 2</td></tr><tr><td>Ready to use</td><td>The segment is done computing but in the progress of step 3</td></tr><tr><td>Success</td><td>The status is done step 3</td></tr><tr><td>Unsuccess</td><td>The segment has been built unsuccessfully</td></tr></tbody></table>

{% hint style="warning" %}
There is a relationship between Segment status and Last computation status.

* If the segment status is 'enable', the last computation status could be updated based on the computation schedule or forced to update.
* Otherwise, its last computation status is updated once after the first build.
  {% endhint %}

#### Source

It indicates the type of member input method used to build the segment, including

* Matching file means the segment is built by the matching file method&#x20;
* Customer/Visitor attribute means the segment is built by the condition method using Have attribute condition&#x20;
* Sources mean the segment is built by the condition method using Perform event condition.

#### Members

It shows the number of members included in a segment.&#x20;

{% hint style="warning" %}
Attributes shown in Segment tab could be modified in Column.&#x20;
{% endhint %}

## Computation Histories tab

**Computation Histories** provides information about the history of each computation by computation ID.&#x20;

* Segment name and segment version give details of which version of a segment was computed. By clicking the version, it could direct to the version history of that version.
* Time-related of information includes the time of start and end and the duration
* Computation trigger means who triggered the computation, including user (force to compute) or system (following the computation schedule)&#x20;
* Error info gives a reason for the unsuccess status

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdHIyl6-z6jFMVR3hIL_HWID_ilJlyUSFU-lorFcEhdS45GSjV4cRh4k7I6fN-VItCVRzYf0JFvRr5w4Mm4w1PZJgZPuqRDTSBU9ouFbOkuZCij6esFiOc5GTW5JApslDfxSZTd-LfjCRtg0VyvkFa_8FIt?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

### Details of Member input method&#x20;

Explain more details of two methods: Condition and Matching file

#### Condition&#x20;

There are two options for the condition method that requires different settings

* ***Perform event***

When creating a segment, users can leverage event data to define conditions. Various types of computations can be applied to event data to derive meaningful insights and segment users effectively.

**1/ Event Counter**

Counts the number of times a specific event occurs based on defined conditions.

Example: Create a segment includes "Users who have made at least 3 purchases in the last 30 days."\
→ Condition: Order Completed event count ≥ 3<br>

**2/ Aggregation**\
Uses event attributes to calculate aggregated values such as Min, Max, Sum, and Average.

Examples: Using event attribute Order Value in event Purchase

* Min: "Users whose lowest purchase value is below $10." → Condition: Minimum (Order Value) < 10
* Max: "Users whose highest purchase value is over $500." → Condition: Maximum (Order Value) > 500
* Sum: "Users who have spent at least $1000 in total." → Condition: Sum (Order Value) ≥ 1000
* Average: "Users whose average purchase value is above $50." → Condition: Average (Order Value) > 50

**3/ Most Frequent**\
Identifies the most commonly occurring value in the event data.

Example: Using event attribute Product Category in event Purchase

"Users who most frequently purchase from category 'Electronics'."  → Condition: Most frequent (Product Category) = 'Electronics'<br>

**4/ First Value**\
Finds the first recorded value of a specific event attribute.

Example: Using event attribute Product Category in event Purchase

"Users whose first purchase category was 'Books'." → Condition: First (Product Category) = 'Books'<br>

**5/ Last Value**\
Finds the most recent value recorded for a specific event attribute.

Example: Using event attribute Product Name in event Purchase

"Users whose last purchased product was 'iPhone 15'." → Condition: Last (Product Name) = 'iPhone 15'<br>

**6/ Unique Count**\
Counts the number of distinct values in a list based on event attributes.

Example: Using event attribute Product Category in event Purchase

"Users who have purchased from at least 5 different product categories."  → Condition: Unique count (Product Category) ≥ 5

<figure><img src="/files/7a9XzEvA7VKrssDxxNZW" alt=""><figcaption></figcaption></figure>

After choosing a computation type, there appears a box to choose a specific event to set as condition

<figure><img src="/files/Si3FPWgklo76cowB0wqK" alt=""><figcaption></figcaption></figure>

1. **Select event** is the interaction of visitors or customers. **Select event** includes 3 steps: select an event, select comparing method, and input value of comparison&#x20;
2. **Aggregation type:** Only appears if computation type is Aggregation to choose the type of calculation you want for selected event attribute
3. **In any source of** is the domain where the event happened. After selecting an event, **CDP 365** will propose a list of sources that have the event
4. **Where** is a filter of the selected event. **Where** could combine more than one event attribute by **AND** logic&#x20;
5. **Time range** is the time in which the event occurred.&#x20;

* ***Have attribute*** is the attribute of customers or visitors, including steps: select attribute, select comparing method, and input the comparison value.

*Could have more than one condition combined by **AND** and **OR** logic. If selecting an attribute or an event that isn't updated, CDP 365 will give a warning note.*

<figure><img src="/files/WfCY7CS55LrlRUdkD9ND" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdM5GrzGg9EuWWiLrrTmDO9lUnUbmHaOiBfxJmjuOTtqBCpKl8eJ0ddtIa4doGVT4aoYwE_4nqhp-mNYLqWTFyP0mVQ7AZXMK7cLlbygd9VogcK7Hk2rYNpMvaMtbJ2VSVSnRAU29EH3SBhjbq-Me3O5wu0?key=nsg4PmgvSxrd7fjFkMggfQ" alt=""><figcaption></figcaption></figure>

#### Matching file

This method includes two steps:&#x20;

* Upload data of customers or visitors into CDP 365
  * If selecting the static update segment, don't have the 'Choose update method' setting&#x20;
  * If selecting the dynamic update segment, have the 'Choose update method' setting
  * 'Choose update method' includes 'Replace the current audiences' (default by CDP 365) and 'Add more audiences'.
* 'Select the criteria to find suitable audiences for the segment' is an optional setting. The segment is created based on the data matched between CDP 365 and the uploaded file.&#x20;

<figure><img src="/files/3qGCBL8beWk8JgIHEeZa" alt=""><figcaption></figcaption></figure>

## Use cases of Segment

### [How to create a Dynamic Segment](/cdp-365-user-guide-en/use-cases/personas/segments/how-to-create-a-dynamic-segment.md)

### [How to create a Static Segment (Matching file)](/cdp-365-user-guide-en/use-cases/personas/segments/how-to-create-a-static-segment-matching-file.md)


---

# 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.antsomi.com/cdp-365-user-guide-en/personas/segments.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.