Vitally to GoodData Integration
AI-first ETL from Vitally into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Vitally into GoodData
Datrise syncs Vitally's accounts, users, health scores, tasks, playbooks, and product usage 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
Vitally: Customer success health and account analytics.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Vitally entities map to GoodData
| Vitally entity | GoodData object | Notes |
|---|---|---|
| accounts | vitally_accounts | id PK · custom fields → flattened columns |
| users | vitally_users | id PK · linked to vitally_accounts |
| health scores | vitally_health_scores | id PK · linked to vitally_accounts |
| tasks | vitally_tasks | id PK · linked to vitally_accounts |
FAQ
How does Datrise handle Vitally'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 Vitally to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Vitally
Early access
Connect Vitally 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.