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

# Segments

The **Segments** in SprintHub allow you to organize your contacts strategically, making marketing actions, automations, reports, and more targeted support easier. With them, you can separate your contact base by specific criteria, making communication much more efficient.

***

### What are Segments?

Segments are **contact groups** created from rules or manual selections. They help you to:

* Target campaigns to specific audiences;
* Create customized automations;
* Analyze results by contact profile;
* Improve database organization.

In SprintHub, there are **two types of segments**: **Static Segments** and **Dynamic Segments**.

Sure! To include in the article of **Segments**, I suggest adding a specific section about the new inclusion rule, making the explanation clear and objective:

#### Inclusion and Repopulation Rule

The **Segments** have an inclusion rule that determines how often contacts that meet the criteria will be added to the segment.

* **Custom time:** it is possible to specify the interval in **minutes** for the segment to be updated and new contacts to be included.
* **Blank field:** if no time is provided, the system will use the default interval of **360 minutes (6 hours)**.
* **Manual Repopulation:** The segment has the **Repopulate**button, which allows you to manually start a new contact check.

  Access and repopulation frequency vary according to user type:

  * **Administrator:** can use the **Repopulate button without limitation**, respecting only the time interval configured in the **inclusion rule**.

  * **Standard user:** can use the **Repopulate every 10 minutes**.

  > **Important:** manual repopulation does not change the inclusion rule configured in the segment. The system will continue following the interval defined for future automatic updates.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FKIz3gWvci7EDlgKTbiHE%2Fimage.png?alt=media&amp;token=e121f407-4eb2-49dd-9d65-039e85f392c6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FKEwe2m6OeUn7OJAoKuky%2Fimage.png?alt=media&amp;token=9faa775c-5c33-451e-87b9-8f28898c90ac" alt=""><figcaption></figcaption></figure>

***

### How to access Segments

To access and create segments in SprintHub:

1. Go to the **Menu**;
2. Click on **Link**;
3. Select **Segments**.

🔎 **Quick access:** use the **Find services**, type **Segments** and click the displayed option.

{% embed url="<https://youtu.be/auDAg_kwCGI>" %}

***

### Static Segments

The **static segments** are made up of contacts added manually or through specific system actions.

#### Characteristics:

* Contacts **can be included or removed manually or via automations**;
* Contacts **do not change automatically**;
* Ideal for fixed lists, such as event participants, VIP customers, or imported leads;

#### Usage example:

* Event contact list;
* Customers who bought a specific product;
* Leads received from a one-time campaign.

***

### Dynamic Segments (with filter)

The **dynamic segments** are created from **smart filters**. This means that contacts enter or leave the segment automatically, as they meet (or no longer meet) the defined criteria.

#### Characteristics:

* Automatic contact updates;
* Based on filters such as status, source, tags, custom fields, dates, among others;
* Ideal for automations, recurring campaigns, and ongoing analyses.

#### Usage example:

* Contacts with the status "Lead";
* Customers who have a valid WhatsApp;
* Contacts created in the last 30 days;
* Leads that have not had recent interaction.

***

### ⚠️ Limitation of Dynamic Segments by Plan

The **dynamic segments (with filter)** have **usage limitations according to the contracted plan** in SprintHub.

This means that:

* Each plan allows a **maximum number of dynamic segments**;
* When the limit is reached, it will not be possible to create new dynamic segments until:
  * Delete an existing segment, or
  * Upgrade the plan.

> ✅ **Important:** Static segments **are not subject to this limitation**, and can be created freely.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F16nLBZclrAiMgD7iRKHO%2Fimage.png?alt=media&amp;token=af423d72-562b-4e1c-9ada-3939473cf8c0" alt=""><figcaption></figcaption></figure>

***

### When should each type of segment be used?

**Use Static Segments when:**

* The contact list does not need to update itself;
* You work with fixed groups;
* The action is one-time.

**Use Dynamic Segments when:**

* You need automatic updates;
* You work with recurring campaigns;
* You use automations and smart flows;
* You want to always reach the right audience.

***

### Conclusion

Segments are an essential tool to get the most out of SprintHub. Understanding the difference between **static segments** and **dynamic**, as well as the **plan limitations**, ensures greater efficiency in contact management and avoids blocks when creating new strategies.

If you need more dynamic segments, consider upgrading your plan or optimizing the segments already in place to keep your operation organized and scalable.


---

# 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.sprinthub.com/en/topics/relate/segments.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.
