> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/marketing/segmentation.md).

# Segmentation

## 🏷️ Segmentation Registration

### Overview

Segmentations allow grouping **people** or **organizations** that share common characteristics. These groups can be used in campaigns, filters, automations, analyses, and other features that depend on selecting specific sets of contacts.

By creating segmentations, management becomes more organized, making it easier to identify strategic groups and carry out targeted actions.

{% hint style="info" %}
Segmentations can be created for **People** or **Organizations**, but never both at the same time.
{% endhint %}

***

## 📌 What is a segmentation?

A segmentation is a custom grouping created from user-defined criteria. It can bring together people or organizations based on:

* Registration information.
* Specific attributes.
* Behaviors.
* Manual selection.
* Automatic rules.

Its main purpose is to make searches, organization, and targeted actions easier.

{% hint style="success" %}
Segmentations help reduce repetitive work and make campaigns, filters, and automations much more efficient.
{% endhint %}

***

## ⚙️ How to set up

Fill in the following fields when creating a new segmentation:

| Field              | Description                                                                           |
| ------------------ | ------------------------------------------------------------------------------------- |
| 📝 **Name**        | Identifier name of the segmentation. Use a title that clearly represents its purpose. |
| 📄 **Description** | Describe the purpose of the segmentation and how it should be used by the team.       |
| 👥 **Type**        | Defines whether the segmentation will be used for **People** or **Organizations**.    |
| 🔄 **Result Type** | Defines whether the segmentation will be **Fixed** or **Dynamic**.                    |

{% hint style="info" %}
Use clear names, such as **Premium Clients**, **New Leads**, **Active Partners** or **Organizations with Active Contract**.
{% endhint %}

***

## 🔄 Result types

### Fixed

In the segmentation **Fixed**, participants are added manually or through automation flows.

The group will remain unchanged until a user or automation makes a new change.

#### Suitable for

* VIP Clients.
* Strategic lists.
* Event attendees.
* Manually selected contacts.

***

### Dynamic

In the segmentation **Dynamic**, participants are automatically included or removed as they meet the defined criteria.

After configuring the filters, the system keeps the segmentation always up to date, with no need for manual changes.

#### Filter examples

* People with the tag **New Lead.**
* Organizations with status **Active.**
* People registered in the last **30 days.**
* People from the city **São Paulo**.

{% hint style="warning" %}
In dynamic segmentations, manually added participants will be removed if they do not meet the defined criteria.
{% endhint %}

***

## ❓ Frequently asked questions

#### Can I change the result type after creating the segmentation?

**No.** After the segmentation is created, the result type (**Fixed** or **Dynamic**) cannot be changed.

***

#### Can I manually add participants in a dynamic segmentation?

**No.** Participants are controlled exclusively by the rules configured in the segmentation.

***

## 🚀 Applications

Segmentations can be used in various system features.

#### 📢 Campaigns and communication

Select specific groups for sending campaigns, notifications, or targeted communications.

#### 📊 Analyses and indicators

Evaluate the behavior of specific groups and track relevant metrics for decision-making.

#### 📁 Internal organization

Structure people and organizations according to internal processes, eliminating manual lists or external controls.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.hablla.com/hablla-docs-en/hablla/marketing/segmentation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.