Pinterest Ads to Supabase Integration

How Datrise loads Pinterest Ads into Supabase

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Pinterest Ads: Paid pin campaigns and shopping performance.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Pinterest Ads entities map to Supabase

Pinterest Ads entity	Supabase object	Notes
campaigns	`pinterest_ads_campaigns`	id PK · custom fields → jsonb columns
ad groups	`pinterest_ads_ad_groups`	id PK · linked to pinterest_ads_campaigns
pin promotions	`pinterest_ads_pin_promotions`	id PK · linked to pinterest_ads_campaigns
spend	`pinterest_ads_spend`	id PK · linked to pinterest_ads_campaigns

FAQ

How does Datrise handle Pinterest Ads's custom fields in Supabase?

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

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

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

Related pipelines

Early access

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