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.

Segments tab

The tab provides segment creation and management.

Create a Segment

Following these steps to create a Segment:

1. Click

2. Select a type of segment

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.

   • Otherwise, the segment will build according to the setting.

Segment types

There are 2 groups of segments based on the types of audiences:

The configuration of a segment

General information

Audience name: the name of the segment

Description: describe the segment

Update segment

Does the segment update?

Create a customer segment of those who shopped 3 times per week, for example, the result was 2,000 customers after creating.

• 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

What are the characteristics of the audience in a segment?

Segment Member

Limit the number of audiences in a segment.

Notification Setup

• 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

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.

Version History

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

Each version is recorded after a time of saving.

Check segments

After creating a segment, check at data table of Segments tab.

Action with segment

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

Label

Label helps management of segments more productive.

Status of a Segment

Segment status can be changed by switching the toggle of Status.

It indicates the status of a segment.

• means the segment status is 'Disable'. Turn on to force the segment to be built immediately.

• means the segment status is 'Enable'. Turn off to disable the computation ability of a segment.

Name

By hovering over the name of a segment could have functions of

• Go to the detailed settings of a segment, click

• Explore the member of a segment, click

• Rename the segment, click

Update method

It indicates the type of update method that the segment is applied.

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

• Step 3: store the data of the segment in CDP 365

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

• Customer/Visitor attribute means the segment is built by the condition method using Have attribute condition

• 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.

Computation Histories tab

Computation Histories provides information about the history of each computation by computation ID.

• 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)

• Error info gives a reason for the unsuccess status

Details of Member input method

Explain more details of two methods: Condition and Matching file

Condition

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

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'

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'

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'

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

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

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

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

5. Time range is the time in which the event occurred.

• 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.

Matching file

This method includes two steps:

• Upload data of customers or visitors into CDP 365

  • If selecting the static update segment, don't have the 'Choose update method' setting

  • 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.

Use cases of Segment

How to create a Dynamic Segment

How to create a Static Segment (Matching file)