Cohort Targeting

A cohort is a static or dynamic set of users defined in Amplitude. For experiment use cases, cohorts are particularly useful for advanced audience targeting. That said, cohorts aren't always the best solution for targeting, so understanding how cohort targeting works with local vs remote evaluation is important.

Experiment cohort targeting currently only supports targeting user cohorts.

Remote evaluation

When you target a cohort in a remote evaluation flag, the cohort is automatically synced to the Amplitude Experiment destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in remote evaluation aren't real-time. For example, if you target a cohort of users who performed a Sign Up event, users are targeted within an hour of performing the event--not immediately after.

Cohorts targeted for remote evaluation may have a propagation delay on the initial sync or large change, depending on the size of the difference. For example, the first sync of 10-million-user cohort is likely to take a lot more time than later syncs.

Use remote evaluation cohort targeting if...

You are targeting users based on user behavior or properties that aren't available in Experiment targeting segments.
You are ok with some targeting delay introduced by cohort sync intervals.

Don't use remote evaluation cohort targeting if...

Users must be targeted in real-time.

Local evaluation

Local evaluation flags and experiment that are deployed to up-to-date server-side SDKs can also target cohorts. When you target a cohort in a local evaluation flag, the cohort is automatically synced to the Experiment Local Evaluation destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in local evaluation aren't real-time. For example, if you target a cohort of users who performed a Sign Up event, users will be targeted within an hour of performing the event--not immediately after.

Cohorts only support User IDs

Local evaluation cohorts currently only sync user IDs to the SDKs. This means that to target cohorts in local evaluation flags, you must include a user ID in the user object passed to the evaluate function.

SDK Support

Server-side SDKs can target cohorts if configured to do so. Client-side SDKs don't currently support local evaluation cohort targeting.

On initialization, configure the cohort sync configuration with the project API and secret key to enable local evaluation cohort downloading and targeting.

SDK	Cohort Targeting	Version
Node.js	✅	`1.10.0+`
Ruby	✅	`1.5.0+`
JVM	✅	`1.4.0+`
Go	✅	`1.7.0+`
Python	✅	`1.4.0+`
PHP	❌	N/A

1const experiment = Experiment.initializeLocal('DEPLOYMENT_KEY', {
2  // (Recommended) Enable local evaluation cohort targeting.
3  cohortSyncConfig: {
4    apiKey: 'API_KEY',
5    secretKey: 'SECRET_KEY'
6  }
7});

1// (1) Initialize the local evaluation client with a server deployment key.
2LocalEvaluationClient experiment = Experiment.initializeLocal("<DEPLOYMENT_KEY>",
3    // (Recommended) Enable local evaluation cohort targeting.
4    LocalEvaluationConfig.builder()
5        .cohortSyncConfig(new CohortSyncConfig("<API_KEY>", "<SECRET_KEY>"))
6        .build());

1client := local.Initialize("DEPLOYMENT_KEY", &local.Config{
2  // (Recommended) Enable local evaluation cohort targeting.
3  CohortSyncConfig: &local.CohortSyncConfig {
4    ApiKey: "API_KEY",
5    SecretKey: "SECRET_KEY"
6  }
7})

1experiment = Experiment.initialize_local("DEPLOYMENT_KEY", LocalEvaluationConfig(
2  # (Recommended) Enable local evaluation cohort targeting.
3  cohort_sync_config=CohortSyncConfig(api_key="API_KEY", secret_key="SECRET_KEY")
4))

1experiment = AmplitudeExperiment.initialize_local('DEPLOYMENT_KEY',
2  # (Recommended) Enable local evaluation cohort targeting.
3  AmplitudeExperiment::LocalEvaluationConfig.new(
4    cohort_sync_config: AmplitudeExperiment::CohortSyncConfig.new(
5      api_key: 'API_KEY',
6      secret_key: 'SECRET_KEY'
7    )
8  )
9)

Troubleshooting

Troubleshooting cohort targeting can challenging due to the asynchronous nature of dynamic cohorts and cohort syncs in general. If you find that your experiment isn't targeting users who should be in the targeted cohort ...

For local evaluation, check that the SDK version supports local evaluation cohort targeting, and that the cohort sync config has been set on initialization.
Check that the cohort has the required sync (Amplitude Experiment for remote evaluation, Experiment Local Evaluation for local evaluation).
Check that the cohort contains the expected user. If the user is contained in the current cohort, check the sync history of the cohort -- is it possible that the user was added to the cohort in a sync after the evaluation occurred?
Check that the user info passed to fetch/evaluate is correct.