Segments Other Functions

Public Segments

• Definition: Public segments are visible to members in the app/on the web, and members can self-register to these segments.
• Purpose: Use of the public segment is useful when you want to ask a customer about their preferences. According to these preferences, he will see the content in the app.

---

Set up a Public Segment

• Follow the first 2 steps from the article Segments Set Up.
• In the second step just click on the Public checkbox.

---

Let the customer join this Segment

You just created a segment which is accessible to customer. There are 2 ways how he can self-register into this segment.

1. Onboarding Process

   Do you want to show the list of Public Segments to customer right after registration?
   Setup the onboarding screen of the type Preference Center Screen firstly. Example of this kind of onboarding screen bellow:

   

2. Change of Preferences

   Do you want to let the customer change his preferences later?
   Setup the right widget in the Profile linked to the User Segments so customer can change his preferences easily. Example of the widget settings bellow:

---

Example Use Case

1. Setup the Public Segments.
2. Setup the onboarding screen of the type Preference Center Screen
3. You can also add widget in the Profile linked to the User Segments so customer can change her/his preferences easily

Editing Segments

• Go to Content Cockpit > Members > Segments > Click the desired Segment

• Click on Edit, make your changes, and Save

Duplicating Segments

• Go to Content Cockpit > Members > Segments > Right-click the desired Segment > Duplicate > Edit what is needed and Save

• The duplicated Segment will appear on the All Segments list

Deleting Segments

• Go to Content Cockpit > Members > Segments > Right-click the desired Segment > Delete & Confirm with Yes

Export Segments Analytics

• Go to Content Cockpit > Members > Segments > Right-click the desired Segment > Export to CSV/EXCEL

---

Ongoing management checklist

• Dynamic Integrity: Confirm that Dynamic segments are refreshing automatically as member behaviors change.
• Naming Convention: Ensure internal names remain descriptive (e.g., including the date or specific threshold) for easy team collaboration.
• Integration Parity: Check that segment counts in TRIFFT roughly match the list/segment sizes in Klaviyo or Bloomreach.
• Null Value Handling: Verify that filters correctly account for members with missing data to avoid accidental exclusion.
• Translation Sync: For Public segments, ensure the display name is updated in all active languages after any name change.
• Redundancy Audit: Delete segments that have "0" members for over 90 days or were created for past, non-recurring promotions.

---