DatriseAI-first ETL

Outbrain to Supabase Integration

AI-first ETL from Outbrain into Supabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Outbrain into Supabase

Datrise syncs Outbrain's campaigns, promoted links, publishers, spend, clicks, 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

Outbrain: Native content discovery advertising.

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

How Outbrain entities map to Supabase

Outbrain entitySupabase objectNotes
campaignsoutbrain_campaignsid PK · custom fields → jsonb columns
promoted linksoutbrain_promoted_linksid PK · linked to outbrain_campaigns
publishersoutbrain_publishersid PK · linked to outbrain_campaigns
spendoutbrain_spendid PK · linked to outbrain_campaigns

FAQ

How does Datrise handle Outbrain'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 Outbrain 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 Outbrain 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.