# Run promotional campaigns for Amplitude cohorts

> In Amplitude CDP, behavioral cohorts are defined by user actions taken within a specific time period. They allow you to group different users based on their actions in your product.

> For the complete documentation index, see [llms.txt](https://docs.talon.one/llms.txt).

For example,
users who watch the entire first season of a TV show
within 24 hours of signing up for the video streaming service form a cohort.

Amplitude CDP allows you to configure the data source for tracking user actions
and the destination with which cohort data is synchronized.
By configuring Talon.One as a destination, you can reference an Amplitude cohort
as an audience in your Talon.One campaigns. You can then,
for example, reward your users
for completing the first season of a popular and promoted TV show on the day of sign-up.

:::important
The user update rate for this integration is 1000 users per minute.
For example, for a cohort of 100000 users,
it takes 100 minutes to send all the user data to Talon.One.
:::

Let's configure Talon.One as a destination and define a cohort in Amplitude CDP.

## Prerequisites

- You are an admin user in Talon.One and Amplitude CDP.
- In Amplitude CDP, you configured a [data source](https://amplitude.com/docs/data/).
  Amplitude CDP requires this data source to track user actions.
- In Talon.One, you created
  a [CDP-specific API key](/docs/product/applications/manage-third-party-api-keys.md).

## Set up the integration

<StepsContainer>

### Configure Talon.One as a destination

Amplitude CDP tracks user action data coming from the data source and passes it to a valid destination.

To configure Talon.One as a destination:

1. In the **Amplitude Data** dashboard, click **Destinations** > **Add Destination**.
1. On the **Catalog** > **Destinations** page, click **Messaging Destinations** > **Talon.One**
   or, using **Search**, select **Talon.One**.
1. In the **Connect to Talon.One** modal, enter the following details:
   1. In **Name**, type a name for the destination.
   1. In **API Key**, type `ApiKey-v1 <API key>`,
      where `<API key>` represents the CDP-specific API key you created as a prerequisite.
   1. In **Destination Hostname**, type the base URL of your Talon.One deployment.
   1. In **User ID Mapping**, verify that the desired `User ID` property is selected.
   1. Click **Save**.
1. Verify that the **Status** column for **Talon.One** reads **Connected**.

### Define an Amplitude cohort

In Amplitude Analytics, you can define the cohort based on your business requirements.

To define the cohort:

1. In the **Amplitude Analytics** dashboard, click **Cohorts** > **New Cohort**.
1. In the **Create cohort by definition** > **The Users who** section, click **...performed event**.
   1. Click **Select event...** and select the user action you're tracking.
1. To save the cohort definition, click **Save**.
   1. In the **Save** modal, in **Name**, type a name for the cohort.
   1. Click **Save**.

:::tip
- When defining the cohort, in **The Users who** section, you can also use the other available criteria,
  such as **...had property**, **...had been active**, and **...had been new**.
- To learn about tracking user actions in Amplitude CDP,
  see the [Amplitude Help Center](https://amplitude.com/docs/get-started/select-events).
:::

### Synchronize the Amplitude cohort

Synchronize the cohort you created for Talon.One
to make it available as an audience for referencing in your Talon.One campaign.

To synchronize the cohort:

1. In the cohort you created, on the top bar, click **Sync to...** > **Talon.One**.
1. In **API Target**, select the destination you created earlier for Talon.One.
1. In **Select a sync type**, select a sync frequency depending on your use case and click **Save Sync**.

:::note
You should synchronize the cohort you created for Talon.One at least once
to be able to view it as an audience in the Rule Builder.
:::

:::tip
- The **Syncs** tab shows the sync status of your cohort.
- To learn about sync types, see the [Amplitude Help Center](https://amplitude.com/docs/cdp/audiences/third-party-syncs).
:::

### Build the rule in Talon.One

In your Talon.One [campaign](/docs/product/campaigns/overview.md),
you can now reference the cohort you defined in Amplitude CDP as an audience.
In your [rule](/docs/product/rules/overview.md),
use the **Is member of an audience** condition to act on the users in the cohort.

:::tip
- You can also use the other available
  [audience conditions](/docs/product/rules/conditions/available-conditions.md#audience-conditions)
  in the Rule Builder.
- A synchronized cohort appears in the audience list with a short delay.
  To refresh the list, save your changes and reload the Rule Builder page.
:::

</StepsContainer>

## Related pages

- [Overview of Amplitude Data](https://amplitude.com/docs/data/data-overview)
- [Behavioral cohorts: Identify users with similar behaviors](https://amplitude.com/docs/analytics/behavioral-cohorts)
- [Define a new cohort](https://amplitude.com/docs/analytics/define-cohort)