DatriseAI-first ETL

Pinterest Ads to GoodData Integration

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

How Datrise loads Pinterest Ads into GoodData

Datrise syncs Pinterest Ads's campaigns, ad groups, pin promotions, 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

Pinterest Ads: Paid pin campaigns and shopping performance.

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

How Pinterest Ads entities map to GoodData

Pinterest Ads entityGoodData objectNotes
campaignspinterest_ads_campaignsid PK · custom fields → flattened columns
ad groupspinterest_ads_ad_groupsid PK · linked to pinterest_ads_campaigns
pin promotionspinterest_ads_pin_promotionsid PK · linked to pinterest_ads_campaigns
spendpinterest_ads_spendid PK · linked to pinterest_ads_campaigns

FAQ

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

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

Related pipelines

Early access

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