Amplitude → Metabase
AI-first ETL from Amplitude into Metabase. Governed entities, incremental sync, typed landing tables.
How Datrise loads Amplitude into Metabase
Datrise syncs Amplitude's product events, user properties, funnels, cohorts, and retention curves into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.
Ideal for self-serve questions and dashboards for whole teams.
Endpoints
Amplitude: Product analytics source for events, funnels, and cohorts.
Metabase: Open-source analytics with questions, dashboards, and embedded insights.
How Amplitude entities map to Metabase
| Amplitude entity | Metabase object | Notes |
|---|---|---|
| product events | amplitude_product_events | temporal columns for trends events |
| user properties | amplitude_user_properties | id PK · linked to amplitude_product_events |
| funnels | amplitude_funnels | id PK · linked to amplitude_product_events |
| cohorts | amplitude_cohorts | id PK · linked to amplitude_product_events |
FAQ
How does Datrise handle Amplitude's custom fields in Metabase?
Flexible values are stored as flattened columns for the question builder, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Metabase types.
How does the Amplitude to Metabase sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Amplitude
Early access
Connect Amplitude to Metabase the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.