# Create cohorts with Microscope, file import, or the Segmentation module

Create cohorts from charts, files, and inline definitions.

Source: https://amplitude.com/docs/analytics/create-cohorts

---

On this page

- [Create cohorts with Microscope](#create-cohorts-with-microscope)
- [Import a cohort from a file](#import-a-cohort-from-a-file)
- [Replace a cohort from a file](#replace-a-cohort-from-a-file)
- [Inline behavioral cohorts and interval cohorts](#inline-behavioral-cohorts-and-interval-cohorts)

# Create cohorts with Microscope, file import, or the Segmentation module

## Create cohorts with Microscope

[Microscope's](/docs/analytics/microscope) *Create Cohort* option lets you create a cohort that contains all users captured by the data point you selected. These are usually static cohorts. For some chart types, like basic retention and funnel analyses, you can still create [behavioral cohorts](/docs/analytics/behavioral-cohorts), but static fields are disabled.

Microscope can also create a group cohort from a data point with groups applied.

Cohorts created from within Microscope are static under the following scenarios:

- Composition with cross property values
- Retention if you have multiple returning events
- Usage interval view in retention
- Retention with calendar alignment for charts of weekly or higher intervals
- Funnels with exclusion events
- Funnels that hold a property constant
- Funnels with Combine Events Inline
- Funnels with Compare Events at Step
- Distribution views in funnels (Time to Convert + Frequency)
- Event segmentation for properties (PropSum + PropAvg)
- Any chart depending on a different cohort

## Import a cohort from a file

You can create a static cohort of users or groups by uploading a CSV or text file of [user IDs](/docs/get-started/identify-users) or Amplitude IDs. To upload a file, navigate to *Cohorts & Audiences* and click *Import from CSV*.

If you have the [Accounts](/docs/analytics/account-level-reporting) add-on, you can also create a cohort of groups. The file must contain one ID per line, and can't contain any other text or extra spaces. The file size must be under 100MB.

If a user ID doesn't exist, Amplitude skips the user ID and doesn't include that user in the cohort. If you upload Amplitude IDs, all Amplitude IDs must be valid.

A properly formatted file has no header row, contains values only in the leftmost column, and doesn't include extra spaces or characters.

The following example shows an improperly formatted file.

After you select a file, specify whether the file contains Amplitude IDs, user IDs, or groups.

### Replace a cohort from a file

You can replace your manually uploaded cohorts. This lets you update your cohort in place, and avoid changing all your charts to point to a new cohort.

## Inline behavioral cohorts and interval cohorts

You can create simple behavioral cohorts directly within the Segmentation module of all Amplitude chart types except Compass. This lets you create a behavioral cohort in the context of a specific chart without navigating away to the [Behavioral Cohorts tab](/docs/analytics/behavioral-cohorts).

To do this, click *+ Performed*.

Use this to filter your charts for users who have triggered certain events.

One difference between an inline cohort and one created on the Behavioral Cohorts tab is the *in each* clause. The *in each* clause filters for users who triggered the selected event a certain number of times within the time interval you specify, creating interval cohorts.

For example, this cohort would filter this [Event Segmentation](/docs/analytics/charts/event-segmentation/event-segmentation-build) chart for users in the last four weeks who triggered `Download Song or Video` at least three times in a given week:

Of those users, 143,793 downloaded three or more songs or videos during the week of January 9th **and** triggered the `Purchase Song or Video` event.

Use inline cohorts to measure cohort populations over time. For example, an important milestone in your product might be playing five or more songs longer than three minutes in a single day. This is your highly engaged cohort.

From there, you can add additional *where* filters to specify event properties or user property conditions. By looking at this behavior in each interval, you can measure the population of your highly engaged cohort over time.

Amplitude evaluates interval cohorts for each time bucket in a chart. For each bucket (for example, each day), Amplitude includes users who meet the interval criteria for that specific bucket. A user can appear in some buckets but not others. The overall (collapsed) value is the union of all qualifying users across all buckets, not only users who qualify in every bucket.

Next, learn how to compare and manage your behavioral cohorts.

Was this helpful?

<!--$-->

<!--/$-->