Dixa → GoodData
AI-first ETL from Dixa into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Dixa into GoodData
Datrise syncs Dixa's conversations, agents, customers, tags, and resolution metrics 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
Dixa: Customer service platform for conversations across channels.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Dixa entities map to GoodData
| Dixa entity | GoodData object | Notes |
|---|---|---|
| conversations | dixa_conversations | id PK · custom fields → flattened columns |
| agents | dixa_agents | id PK · linked to dixa_conversations |
| customers | dixa_customers | id PK · linked to dixa_conversations |
| tags | dixa_tags | id PK · linked to dixa_conversations |
FAQ
How does Datrise handle Dixa'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 Dixa to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Dixa
Early access
Connect Dixa 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.