DatriseAI-first ETL

Twitter Ads to GoodData Integration

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

How Datrise loads Twitter Ads into GoodData

Datrise syncs Twitter Ads's campaigns, line items, promoted tweets, 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

Twitter Ads: Paid campaign delivery and performance on X.

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

How Twitter Ads entities map to GoodData

Twitter Ads entityGoodData objectNotes
campaignstwitter_ads_campaignsid PK · custom fields → flattened columns
line itemstwitter_ads_line_itemsid PK · linked to twitter_ads_campaigns
promoted tweetstwitter_ads_promoted_tweetsid PK · linked to twitter_ads_campaigns
spendtwitter_ads_spendid PK · linked to twitter_ads_campaigns

FAQ

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

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

Related pipelines

Early access

Connect Twitter Ads 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.