Adjust to Supabase Integration

How Datrise loads Adjust into Supabase

Datrise syncs Adjust's installs, sessions, in-app events, campaigns, cohorts, and attribution touchpoints 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

Adjust: Mobile measurement and attribution platform.

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

How Adjust entities map to Supabase

Adjust entity	Supabase object	Notes
installs	`adjust_installs`	id PK · custom fields → jsonb columns
sessions	`adjust_sessions`	id PK · linked to adjust_installs
in-app events	`adjust_in_app_events`	timestamptz events
campaigns	`adjust_campaigns`	id PK · linked to adjust_installs

FAQ

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