Amplitude Cohorts Destination

When you create an audience in Engage and connect it to the Amplitude Cohorts destination, Segment automatically:

1. Creates a new cohort in Amplitude using the audience name.
2. Adds users to the cohort in Amplitude when they enter the audience.
3. Removes users from the cohort in Amplitude when they exit the audience.

Before you begin, make sure you have access to the following information:

• An Amplitude API Key and Secret Key, which you can find in the General tab of your Amplitude project settings.
• Your Amplitude App ID, also found in the General tab of your Amplitude project settings.
• A Cohort Owner Email address. This is the email of the user who owns the cohorts in Amplitude.
• An Engage Audience that you want to connect to this destination.

1. In Segment, go to Engage > Engage Settings.
2. Click Destinations, then click Add Destination.
3. Search for Amplitude Cohorts (Actions) and click on it.
4. Click Add destination, then click Confirm Source.
5. Under Basic Settings, enter:
   • A name for your destination (for example, "Amplitude Cohorts Prod").
   • Your Amplitude API Key and Secret Key.
   • Your Amplitude App ID.
   • The Cohort Owner Email — the Amplitude user who will own all synced cohorts by default.
   • Your Endpoint Region (North America or Europe).
6. Enable the destination and click Save.

1. Navigate to Connections > Destinations, search for the Amplitude Cohorts (Actions) destination you created, and click on it.
2. Navigate to Mappings > New Mapping and click the Sync To Amplitude Cohort tile.
3. Review the default field mappings. The User ID field maps to $.userId by default. If you plan to sync users by Amplitude ID instead, update the Amplitude ID field mapping accordingly.
4. Click Save.
5. On the Mappings tab, enable the Sync To Amplitude Cohort action.

1. Navigate to Engage > Audiences and select the Audience you want to sync to Amplitude.
2. Click Add Destination and select the Amplitude Cohorts (Actions) destination you created.
3. Configure the per-audience settings:
   • ID Type: Choose User ID to match users by their Segment userId, or Amplitude ID to match by Amplitude's internal identifier.
   • Cohort Name (optional): Override the default cohort name. By default, the Segment audience name is used.
   • Cohort Owner Email (optional): Override the default cohort owner set in destination settings.
   • User ID (optional): A valid User ID that exists in your Amplitude project. Amplitude requires a temporary seed user to create the cohort; this user is added during creation and immediately removed. If left blank, Segment attempts to discover a valid User ID automatically. Set this manually only if the automatic lookup fails or no users are found.
4. Click Save, then click Add 1 Destination. Your audience will begin syncing to Amplitude.

• User ID: Use when Amplitude users are identified by the same ID as your Segment userId. This is the default.
• Amplitude ID: Use when you want to match users by Amplitude's internal numeric identifier instead of your own user ID.

When Segment creates a cohort, Amplitude requires the request to include at least one valid User ID. Amplitude will reject empty cohorts. Because no audience members exist yet at creation time, Segment adds a temporary "seed" user to satisfy this requirement. Once the Amplitude creates the audience, Segment removes the "seed" user.

The seed is always a User ID, even if you set the audience's ID Type to Amplitude ID. Amplitude only supports User IDs when creating a cohort, so cohort creation uses a User ID regardless of the ID Type you sync members with. The ID Type setting still controls how members are added to and removed from the cohort after it exists.

By default, you can leave the User ID field blank, and Segment automatically discovers a valid User ID from your Amplitude project to use as the seed. Set this field manually only if the automatic lookup fails or your project has no discoverable users. If you need to manually set this field, provide any valid User ID that exists in your Amplitude project. The seed user is never left in the cohort.

Yes. The Cohort Owner Email set in destination settings applies to all synced cohorts by default. You can override it on a per-audience basis using the Cohort Owner Email field in the audience destination settings.

The Amplitude Cohorts destination processes Identify and Track calls emitted by Engage. Both are handled the same way — the payload is inspected to determine whether the user should be added to or removed from the Amplitude Cohort. If using Track calls, Segment ignores the event name.

Segment supports two regions: North America (amplitude.com) and Europe (analytics.eu.amplitude.com). Select the appropriate region in the destination settings to ensure Segment routes to the correct Amplitude data center.