# Define a new cohort Define behavioral cohorts with events, properties, and groups. Source: https://amplitude.com/docs/analytics/define-cohort --- On this page - [Define the cohort](#define-the-cohort) - [User property clauses](#user-property-clauses) - [Group-level cohorts](#group-level-cohorts) # Define a new cohort Amplitude Academy Create, Analyze, and Activate User Groups with Behavioral Cohorts Learn to group users who share a trait or a set of traits into cohorts. [Get started](https://academy.amplitude.com/create-user-groups-with-behavioral-cohorts?utm_source=docs\&utm_medium=in-product\&utm_campaign=academy-link) ## Define the cohort To define a new [cohort](/docs/analytics/behavioral-cohorts), follow these steps: 1. Click *Create > Cohort*. This opens the new cohort page, where you can set cohort parameters, upload a CSV of users into a new behavioral cohort, select and edit a predictive cohort template, or [create a prediction for a predictive cohort](/docs/data/audiences/predictions). 2. You can click any of the conditions (performed event, had been active, had been new, had property, or had propensity) listed to begin defining your cohort. However, since this is a behavioral cohort, let's start by clicking *...performed event*. You can add other conditions to your cohort definition later. 3. Click *Select event...* and select the event you're interested in. 4. Begin setting the parameters that define your behavioral cohort: First, tell Amplitude how to count events. The **with** dropdown includes six options: - **Count.** The number of times users trigger your event. For example, all users who triggered Favorite Song or Video more than five times during the last 30 days. Refer to the [Behavioral cohorts FAQ](https://help.amplitude.com/hc/en-us/articles/4402840043789) to learn more about creating a cohort of users who lack user properties or didn't perform an event. - **Relative count.** Amplitude compares two different event frequencies. For example, all users who triggered Play Song or Video at a greater frequency than Favorite Song or Video during the last 30 days. You have the option to add "where" clauses for both events under comparison. - **Total sum of property.** Filters for users who triggered events with a particular event or user property sum. These event or user properties must have numerical values. For example, all users in the last 30 days who triggered Play or Search Song with total Duration value greater than 60 seconds. - **Distinct values of property.** Filters event or user properties down to a specific value or set of values. For example, only users who favorited a song or video on more than one device. - **Historical count.** Your cohort contains users who triggered the event a specific number of times, between one and five. Refer to [how Historical Count works in Amplitude](/docs/analytics/historical-count-1) to learn more. - **Count in interval**. Filter for users who triggered the event at least one time on each of the number of distinct days within a given interval. This enables you to specify behavior that occurred within distinct days in a defined time period. For example, you could filter for users who triggered the event at least once on each of a certain number of distinct days (you define how many) within a given interval. This differs from daily, weekly, or monthly behavior, which doesn't require the behavior to occur on different days. When you use an interval cohort as a segment in a chart, Amplitude evaluates the cohort for each time bucket. For each bucket in the chart (for example, each day in a daily chart), Amplitude checks whether the user meets the interval criteria for that specific bucket and includes them in that bucket's results. This means a user can appear in some time buckets but not others. The overall (collapsed) value represents the union of all users across all time buckets, not only users who meet the criteria in every bucket. Refer to [how stickiness analysis works in Amplitude](/docs/analytics/charts/stickiness/stickiness-interpret) for more information. 5. Set the **operator** (equal to, greater than, less than, and so on) and the **value** (such as the count value) of this parameter. 6. Tell Amplitude when these events must have taken place. The **any time** dropdown includes these options: - **During.** Includes all events triggered within the **date range** you choose in the date picker. You can use a range between two specific dates or a dynamic range, like *Last 30 Days*. In the latter case, the range updates every day and drops users who haven't triggered the event in X number of days from the cohort. - **Since.** Includes all events triggered since the **calendar date** you choose in the date picker. - **Within.** Looks at events triggered within each cohort member's X days of first use. This is useful when you're interested in the group of users who triggered a specific event within X days of becoming a new user. 7. You can add more events by clicking **...then** and repeating the previous steps. Adding an event using **...then** means users must trigger both events in the specified order to qualify for the cohort. If you want to add another event **without** requiring users trigger them in a specific order, use **+ Add**, as described in the next step. 8. Add an *...or* clause, or add another event, property, propensity, cohort, or new user. To view options for an Or clause, hover over the cohort definition. To view options for adding to your cohort definition, click *+ Add* below your current cohort definition. When you add a condition using an *Or* clause, Amplitude includes users who meet **either** of those conditions. When you add to your cohort definition with *+ Add*, Amplitude treats that as an *And* clause: A user must meet **both** conditions to be included in the cohort. When you use *+ Add* to add components to your cohort, you can specify inclusion or exclusion. Select *did not* for events, user properties, and propensities; *not part* for cohorts; and *had not been* for new users. Amplitude excludes items that meet the exclusion condition from the cohort, even if the items meet all other specified conditions. In this example, the cohort contains users who triggered the Play or Search Song event more than eight times, triggered the Favorited a Song or Video event more than four times between April 1 and April 30, and are from the United States. For the most accurate results, put a date range around any user properties you include. ## User property clauses When you include a user property condition in a cohort, Amplitude evaluates user properties instead of events. Amplitude includes users who had a specific value for a specific user property at a certain time. Properties and events use different options: - **Most recently:** This selects only users whose **most recent value** for the user property you're interested in matches the value you've specified. This value comes from a user's most recent active event. This is useful if you have a user property where the values change frequently, but you want the cohort to look at the most recent value only. For example, you might want to only include users whose push notifications are enabled, since many new users (those in their first 30 days) may not have enabled them yet. For numerical property values, Amplitude interprets a missing value as 0. - **Any time:** This selects users who had the specified value for the user property you're interested in at **any time in the date range** you select. For example, users who had the Country property of United States anytime during the last 30 days: Even if some users may have left the United States (which would mean their most recent Country property value is different), this cohort definition would still include them. ## Group-level cohorts If you have instrumented group types, you can create group cohorts from the cohort detail page (where you define or upload a cohort). To do this, when defining your cohort, select the group name on the left side of the definition. When applying the group cohort to a chart, add the group by clicking *+ Filter by*, and then *Cohort*. Then select the group name from the list. Group cohorts are compatible with all Amplitude chart types except Personas and Compass. Was this helpful?