DatriseAI-first ETL

Google Ads GoodData

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

How Datrise loads Google Ads into GoodData

Datrise syncs Google Ads's campaigns, ad groups, spend, clicks, conversions, and attribution signals 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

Google Ads: Paid media source for campaign and conversion metrics.

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

How Google Ads entities map to GoodData

Google Ads entityGoodData objectNotes
campaignsgoogle_ads_campaignsid PK · custom fields → flattened columns
ad groupsgoogle_ads_ad_groupsid PK · linked to google_ads_campaigns
spendgoogle_ads_spendid PK · linked to google_ads_campaigns
clicksgoogle_ads_clicksid PK · linked to google_ads_campaigns

FAQ

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

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

Related pipelines

Early access

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