> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Amplitude as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/amplitude

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Amplitude connector syncs your raw events, cohorts, and annotations into PostHog. It authenticates against Amplitude's Export API, Cohorts API, and Annotations API using your project's API key and secret key.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Amplitude.
3.  You need an API key and secret key from Amplitude. In Amplitude, go to **Settings → Organization settings → Projects** and open the project you want to sync. Copy the project's **API key** and **secret key**. Then choose your **Region** — **US (amplitude.com)** or **EU (analytics.eu.amplitude.com)** — to match where your Amplitude project is hosted.
4.  Back in PostHog, enter the `API key`, `Secret key`, and `Region`, then click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using Amplitude data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `events` | Raw events from Amplitude's Export API (only the last 30 days are pulled on the initial sync) | Incremental |
| `cohorts` | Behavioral cohorts from the Cohorts API | Full refresh |
| `annotations` | Dashboard annotations from the Annotations API | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

The events stream uses Amplitude's Export API, which enforces a roughly 2-hour data latency — events uploaded to Amplitude within the last couple of hours may not yet be available to sync. The initial sync only pulls the last 30 days of events; subsequent incremental syncs fetch newer data using server upload time as the cursor.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |
| `Secret key` | password | Yes |
| `Region` | select | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `events` | Only syncs the last 30 days on initial sync | Incremental, Full refresh | server\_upload\_time | — |
| `cohorts` | A saved group of users in Amplitude defined by behavioral or property criteria. | Full refresh | — | — |
| `annotations` | A chart annotation in Amplitude marking a notable date with a label. | Full refresh | — | — |
| `event_types` | An event type in the project's tracking plan, naming and describing one kind of tracked event. | Full refresh | — | — |
| `event_properties` | An event property definition from the tracking plan, describing one property carried by an event type. | Full refresh | — | — |
| `user_properties` | A user property definition from the tracking plan, describing one property carried on users. | Full refresh | — | — |
| `event_categories` | An event category in the tracking plan, used to group event types. | Full refresh | — | — |
| `group_properties` | A shared group property definition from the tracking plan, describing one property carried on groups (accounts). | Full refresh | — | — |