DatriseAI-first ETL

Pinterest Ads to Birst Integration

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

How Datrise loads Pinterest Ads into Birst

Datrise syncs Pinterest Ads's campaigns, ad groups, pin promotions, spend, impressions, and conversions into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.

Ideal for networked, governed enterprise BI.

Endpoints

Pinterest Ads: Paid pin campaigns and shopping performance.

Birst: Cloud BI with networked analytics and enterprise semantic layers.

How Pinterest Ads entities map to Birst

Pinterest Ads entityBirst 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 Birst?

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 Birst types.

How does the Pinterest Ads to Birst sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.

Related pipelines

Early access

Connect Pinterest Ads to Birst 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.