DatriseAI-first ETL

StackAdapt to GoodData Integration

AI-first ETL from StackAdapt into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads StackAdapt into GoodData

Datrise syncs StackAdapt's campaigns, line items, creatives, spend, impressions, and conversions 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

StackAdapt: Programmatic advertising across native and display.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How StackAdapt entities map to GoodData

StackAdapt entityGoodData objectNotes
campaignsstackadapt_campaignsid PK · custom fields → flattened columns
line itemsstackadapt_line_itemsid PK · linked to stackadapt_campaigns
creativesstackadapt_creativesid PK · linked to stackadapt_campaigns
spendstackadapt_spendid PK · linked to stackadapt_campaigns

FAQ

How does Datrise handle StackAdapt'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 StackAdapt to GoodData sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect StackAdapt 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.