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

# Using Cohorts

The Cohorts you create can be used for targeting across various Hackle features.

### Setting Up Targeting

This section covers how to target a Cohort in an **A/B Test**.

The method for setting up Cohort targeting in Feature Flags and Remote Config is the same.

#### Setting Up a Cohort Filter

![](/files/N4ZcVhhfezqvIOyzLynd)

#### Supported Operators

The Cohort filter currently supports two operators: `=` and `≠`.

![](/files/nEiygOZUXmbB5ojJnyhq)

#### Select the Target Cohort from the List

The User Identifier Basis of the experiment and the User Identifier of the Cohort must be the same.

If the experiment's User Identifier Basis is `deviceId`, the Cohort's User Identifier must also be `deviceId`.

![Experiment User Identifier - deviceId](/files/zKN8zKEufwbFKH5jGB03)

![Targeting - Cohort list](/files/u1LjDzyVtBLEaXTrpNw2)

Therefore, **only Cohorts with the same User Identifier as the experiment are shown in the targeting list**.

![The active user Cohort has deviceId.](/files/gM3hDhWo2wjOKhTYd2AC)

#### Number of Target Users When Using a Cohort

When you use a Cohort for targeting or campaigns, the number of users actually included as targets from the Cohort varies depending on how it is used. **Except for schedule-based sending, only up to 1 million users** are included as targets.

| Usage Method                            | Number of Users Included as Targets |
| --------------------------------------- | ----------------------------------- |
| Schedule-based sending                  | **All** Cohort members included     |
| Event-based · API-based sending         | Up to **1 million** included        |
| In-App Message                          | Up to **1 million** included        |
| A/B Test · Feature Flag · Remote Config | Up to **1 million** included        |

{% hint style="warning" %}
For event-based sending, API-based sending, and In-App Messages, if the number of users included in the Cohort exceeds 1 million, **only up to 1 million users are included in the campaign audience**, and **the rest are dropped from the target**. Even if the campaign appears to work normally, note that the actual reach is limited to 1 million users.
{% endhint %}

***

## Analyzing with Cohorts

You can perform Cohort-level data analysis by setting a Cohort in the user group filter of Data Analytics.

![User Group > Add Filter > Select Cohort](/files/CuTcA0YXMGxtQLEmoIw7)

![Data analysis at the Cohort level](/files/lWgMHvLLhGqorBCS4fFL)

***

## Running CRM Marketing for a Cohort

You can send In-App Messages and Push Messages targeting a specific Cohort.

You can find various Cohort examples applicable to different situations in the Push Message recommended template guide.

![Send a Push Message to a specific Cohort](/files/oT3TV34rMwvd22f5BIL4)


---

# 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.hackle.io/en/cohort/usage.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.