Short.io to GoodData Integration
AI-first ETL from Short.io into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Short.io into GoodData
Datrise syncs Short.io's links, domains, clicks, referrers, countries, and link tags 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
Short.io: Branded short links and click analytics.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Short.io entities map to GoodData
| Short.io entity | GoodData object | Notes |
|---|---|---|
| links | short_io_links | id PK · custom fields → flattened columns |
| domains | short_io_domains | id PK · linked to short_io_links |
| clicks | short_io_clicks | id PK · linked to short_io_links |
| referrers | short_io_referrers | id PK · linked to short_io_links |
FAQ
How does Datrise handle Short.io'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 Short.io to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Short.io
Early access
Connect Short.io 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.