Source connector

Amplitude connector

Amplitude integration for databases, warehouses and BI tools

Product analytics source for events, funnels, and cohorts. Datrise captures Amplitude entities such as product events, user properties, funnels, cohorts, and retention curves, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Amplitude Export API (api/2/export) authenticates with HTTP Basic, incremental runs key on start/end hourly window (YYYYMMDDTHH) combined with each event's server_upload_time, and Amplitude caps calls at 5 concurrent requests across all Amplitude REST API endpoints (Amplitude does not publish an Export-API-specific per-hour cap).

Of the 5 objects, 4 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `amplitude_product_events`) with a schema derived from the Amplitude API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Amplitude pipeline page, and join the waitlist to get the Amplitude connector (Product analytics) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Amplitude data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
product events	amplitude_product_events	Append-only, incremental by timestamp
user properties	amplitude_user_properties	Upsert by primary key, incremental on updated-at
funnels	amplitude_funnels	Upsert by primary key, incremental on updated-at
cohorts	amplitude_cohorts	Upsert by primary key, incremental on updated-at
retention curves	amplitude_retention_curves	Upsert by primary key, incremental on updated-at

Amplitude API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Amplitude Export API (api/2/export)
Authentication	HTTP Basic — HTTP Basic Auth with the project's API key as username and secret key as password.
Pagination	none — Each call returns a single zipped archive of newline-delimited JSON files for the requested `start`/`end` hour range; there is no page token, so a connector pages by advancing the hourly window itself.
Rate limit	5 concurrent requests across all Amplitude REST API endpoints (Amplitude does not publish an Export-API-specific per-hour cap)
Incremental cursor	start/end hourly window (YYYYMMDDTHH) combined with each event's server_upload_time — Events become available for export only about 2 hours after Amplitude's servers receive them, so incremental pulls need a trailing buffer to avoid missing late-arriving events.
Webhooks	No
Bulk export	Yes — Export API (zipped NDJSON, up to a 365-day range per request)
Deletes detectable	No

Official API reference

What bites when replicating Amplitude

A single export request is capped at 365 days and 4 GB of compressed output; requests over the 4 GB ceiling return HTTP 400 and must be split into smaller `start`/`end` windows.
Exported data lags ingestion by up to 2 hours, so polling right up to `now` on every run silently drops the most recent events until the next sync catches them.
GDPR/CCPA user-deletion jobs purge events and user properties from Amplitude's servers within 30 days but do not emit a delete event through the Export API, so a downstream warehouse copy is not automatically reconciled.
A deleted user's `user_id`/`amplitude_id` is not remembered after purge: if that same user later sends new events, Amplitude treats them as a brand-new user rather than re-linking history.

Compare this against every other documented API

Popular destinations for Amplitude

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Amplitude connector FAQ

What Amplitude data does the connector extract?: 5 objects: product events, user properties, funnels, cohorts and retention curves. Each lands in its own table with types preserved; history-style objects (1: product events) load as append-only streams.
Is the Amplitude integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Amplitude data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Amplitude → destination pair has its own page with the object-to-table mapping.

Related Product analytics sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Amplitude pipeline with guided onboarding

Join the waitlist to get priority access for Amplitude integrations with guided setup, schema-aware mapping, and production-grade incremental sync.