> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/~/revisions/5vNgx1SBLaM9wSz456q7/integrations-and-data-ingestion/how-to-integrate-with/amplitude-cohort-sync.md).

# Amplitude (Cohort Sync)

### Overview

The Mixpanel integration for Birdie is a push connector that can be used to process webhook requests from a Cohorts integration configured Mixpanel. It works by receiving requests from Mixpanel with incremental syncs of updates to your cohorts. Birdie will store this information and consolidate into a single record so you can use your Cohorts as filters for data within Birdie.

### Requirements

* You need a paid Amplitude plan to enable this integration
* You must enable this integration in each Amplitude project you want to use it in
* At least one cohort configured in your amplitude account, but you can configure more than one and Birdie will consolidate them at the user level
* An active Birdie account and its Organization\_id: <https://app.birdie.ai/settings/organization>
* An API Key from Birdie to setup the integration (Reach out and we'll provide you with one)
* A field that can be matched to your feedbacks within Birdie. It's important for your cohort exports to contain at least one field (account\_id) that also exists within the Birdie feedbacks so we can match them
* Amplitude sends email alerts for job success and failures, keeping you informed about the status of your cohort syncs

### Setup in Amplitude

{% stepper %}
{% step %}

### Open Destinations

In Amplitude Data, click Catalog and select the Destinations tab.
{% endstep %}

{% step %}

### Choose Cohort destination

In the Cohort section, click Birdie.
{% endstep %}

{% step %}

### Enter Birdie details

Enter your Birdie API Key, your Organization\_id and select your endpoint:

<https://api.birdie.ai/ingestion/amplitude/cohorts>
{% endstep %}

{% step %}

### Select hierarchy mappings

Select the hierarchy of mappings you want to map users to.

* If you select User alias as the target object, add a User alias label. Otherwise, you can leave it empty.
* Make sure you have a matching field for the account\_id, existent in your Birdie’s feedback records.
  {% endstep %}

{% step %}

### Save

When finished, save.
{% endstep %}
{% endstepper %}

### Send a cohort

{% stepper %}
{% step %}

### Open cohort and start sync

In Amplitude, open the cohort you want to sync, then click Sync.
{% endstep %}

{% step %}

### Select Birdie

Select Birdie, then click Next.
{% endstep %}

{% step %}

### Choose account

Choose the account you want to sync to.
{% endstep %}

{% step %}

### Choose sync cadence

Choose the sync cadence. Select One-Time Sync, Scheduled Sync, or Real-Time sync. For more information about cohort syncing, see Sync to third-party destinations:

<https://amplitude.com/docs/data/audiences/third-party-syncs>
{% endstep %}

{% step %}

### Save

When finished, save your work.
{% endstep %}
{% endstepper %}

### Data in scope

This connector receives incremental cohort membership updates from Amplitude for the cohorts you configure to sync, and stores them in Birdie so they can be used as filters alongside your other data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ask.birdie.ai/~/revisions/5vNgx1SBLaM9wSz456q7/integrations-and-data-ingestion/how-to-integrate-with/amplitude-cohort-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.