DatriseAI-first ETL

Facebook Ads GoodData

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

How Datrise loads Facebook Ads into GoodData

Datrise syncs Facebook Ads's campaigns, ad sets, ads, spend, and conversion 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

Facebook Ads: Meta paid social campaigns and performance insights.

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

How Facebook Ads entities map to GoodData

Facebook Ads entityGoodData objectNotes
campaignsfacebook_ads_campaignsid PK · custom fields → flattened columns
ad setsfacebook_ads_ad_setsid PK · linked to facebook_ads_campaigns
adsfacebook_ads_adsid PK · linked to facebook_ads_campaigns
spendfacebook_ads_spendid PK · linked to facebook_ads_campaigns

FAQ

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

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

Related pipelines

Early access

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