Amplitude → GoodData
AI-first ETL from Amplitude into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Amplitude into GoodData
Datrise syncs Amplitude's product events, user properties, funnels, cohorts, and retention curves into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Amplitude: Product analytics source for events, funnels, and cohorts.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Amplitude entities map to GoodData
| Amplitude entity | GoodData object | Notes |
|---|---|---|
| product events | amplitude_product_events | date dimensions 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 GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Amplitude to GoodData 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 GoodData 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.