DatriseAI-first ETL

Segment Supabase

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

How Datrise loads Segment into Supabase

Datrise syncs Segment's sources, destinations, track events, identify calls, and schema catalog 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

Segment: Customer data platform routing events to warehouses.

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

How Segment entities map to Supabase

Segment entitySupabase objectNotes
sourcessegment_sourcesid PK · custom fields → jsonb columns
destinationssegment_destinationsid PK · linked to segment_sources
track eventssegment_track_eventstimestamptz events
identify callssegment_identify_callsid PK · linked to segment_sources

FAQ

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