DatriseAI-first ETL

Pinterest Ads to PlanetScale Integration

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

How Datrise loads Pinterest Ads into PlanetScale

Datrise syncs Pinterest Ads's campaigns, ad groups, pin promotions, spend, impressions, and conversions into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

Pinterest Ads: Paid pin campaigns and shopping performance.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Pinterest Ads entities map to PlanetScale

Pinterest Ads entityPlanetScale objectNotes
campaignspinterest_ads_campaignsid PK · custom fields → JSON 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 PlanetScale?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native PlanetScale types.

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

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