# Organizing Segments with Collections

## Why Segment Collections Matter

* Segments help you slice insights by different lenses: customer profiles, behavior, lifecycle status, etc.
* But not every segment type is directly comparable.
* Segment Collections keep these lenses organized, so you don’t compare unlike groups or lose track of valuable cuts.

## How Segment Collections Work

* Each Collection groups a family of segments.
* Users can:
  * Compare segments within the same collection (e.g. churned vs. retained customers).
  * Avoid mixing cross-domain comparisons that don’t make sense (e.g. Industry vs. Daily Active).
* Collections can be named intuitively (“CRM Status”, “Behavioral Cohorts”, “Firmographics”) so everyone navigates insights smoothly.

## Best Practices for Organizing Segments

* Create one collection per “dimension” of segmentation (Firmographics, Behaviors, Lifecycle).
* Agree internally on naming conventions (e.g. “DAU > 30” vs. “High DAU”).
* Use Collections as a training tool — new team members will quickly see “how we slice data here.”
* Review Collections quarterly: retire unused segments, align with evolving CRM or analytics sources.

## How to create a collection of Segments

{% stepper %}
{% step %}

### Open Segments in Exploration

Navigate to your Segments tab in Exploration.
{% endstep %}

{% step %}

### Select Segments to Group

Select the Segment you want to group into a collection (e.g.: These 3 segments related to Customer Size).

![](https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FmOtwazh3o8EnjddmSnHT%2FScreenshot%202026-04-02%20at%2017.15.36.png?alt=media\&token=31827d21-72a4-4009-a9fb-d19339403a5f)
{% endstep %}

{% step %}

### Save as a Collection

Click Save Collection.

![](https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2Ffi2yIJveSGbgmYbyyWl5%2Fss_exploration_save-segment-collection-modal_v1.png?alt=media\&token=ceec9e1f-209b-4263-ad1a-5d28fe1922f6)
{% endstep %}

{% step %}

### Name the Collection

Give your Collection a name.
{% endstep %}

{% step %}

### Group View by Collections

Change Segments table to group by collections.

![](https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FByrCDZE0dk6wp9Ss2pe5%2Fss_exploration_group-segments-collection_v1.png?alt=media\&token=3b8c41d9-794d-4e90-8bc0-2593db530f78)
{% endstep %}

{% step %}

### Done

Now, get even more insightful analysis from your segmented data.

![](https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2Fhe20WXcQYH0f4sjfUVx1%2Fss_exploration_segments-metrics-table-grouped-by-collection_v1.png?alt=media\&token=64cb20ab-7628-4e8a-8973-b48b1bfde6b1)
{% endstep %}
{% endstepper %}


---

# 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://ask.birdie.ai/voice-of-customer/exploration-and-analysis/organizing-segments-with-collections.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.