> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cohorts

> Named attendee groups — hand-picked or rule-driven — built once and applied from any email send draft.

A cohort is a named set of your event's attendees: *VIP guests*, *Speakers*, *Everyone still pending*. You build it once on the **Cohorts** page, then apply it wherever a recipient selection is needed — an [email send draft](/en/marketing/emails) today, and [automations](/en/marketing/automations) can add people to one or branch on membership.

## Create a cohort

<Steps>
  <Step title="Name it">
    Click **Create cohort** and give it a name. Members are picked on its page.
  </Step>

  <Step title="Choose how membership is maintained">
    * **Static** — you maintain the members; the set changes only when you change it.
    * **Dynamic** — rules maintain the members; attendees who start or stop matching move in and out automatically.
  </Step>

  <Step title="Fill it">
    A static cohort's members come from **picking from attendees** — filter or search the table and tick people in — or from **freezing the current result of rules** as a one-time snapshot. A dynamic cohort just keeps its rules; the member list is whoever matches right now.
  </Step>
</Steps>

<Tip>
  You can also create a static cohort without visiting this page: on any email send draft, tick your recipients and click **Save as cohort**.
</Tip>

## Rules

Rules are conditions combined with a match mode — **match all conditions** (intersection) or **match any condition**. Each condition tests one fact about a registration:

| Field           | Tests                                                                                                                  | Operators                       |
| --------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------- |
| **Status**      | The registration's status                                                                                              | is / is not                     |
| **Ticket type** | The registration's [ticket type](/en/ticketing/ticket-types)                                                           | is / is not                     |
| **Perk**        | The person's effective [perks](/en/ticketing/perks) — from their ticket, their redemption code and grants of their own | holds / does not hold           |
| **Exhibitor**   | Whether they staff a given [exhibitor](/en/exhibition/exhibitors)                                                      | belongs to / does not belong to |

With no conditions, the rules match every attendee — add conditions to narrow. A live **Preview** shows how many attendees match right now, and every condition needs a value before the cohort can be saved.

## Static vs. dynamic

|              | Static                       | Dynamic                                                |
| ------------ | ---------------------------- | ------------------------------------------------------ |
| Members      | The list you saved           | Whoever matches the rules, resolved fresh on every use |
| Changes when | You edit it                  | Attendees start or stop matching                       |
| Rules        | Optional — a snapshot source | Required                                               |

A dynamic cohort applied to a send draft brings in its *current* members at that moment; the send then records exactly who was addressed.

## Rules to know

* **Cohorts are per event** and live under the event's **Marketing** group.
* **Membership resolves against the live attendee list when applied** — registrations that no longer exist drop out automatically.
* **A snapshot does not follow its rules.** Freezing the result of rules into a static cohort keeps those people even as the facts change; use a dynamic cohort if you want the set to track reality.
* **Automations can only add people to a static cohort** — a dynamic one derives its own members and cannot be added to by hand or by flow.
* **Deleting a cohort is allowed** and does not touch anything sent with it: send records keep their own recipient lists.

## Next

<CardGroup cols={2}>
  <Card title="Sending email" icon="send" href="/en/marketing/emails">
    Apply a cohort as the audience of a send draft.
  </Card>

  <Card title="Automations" icon="workflow" href="/en/marketing/automations">
    Add people to a cohort automatically, or branch a flow on membership.
  </Card>
</CardGroup>