Sailthru to PostgreSQL Integration

How Datrise loads Sailthru into PostgreSQL

Datrise syncs Sailthru's users, campaigns, blasts, message events, lists, and content items into PostgreSQL as a typed table per source entity. 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 each entity's updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative range partitioning by load date for high-volume tables. PostgreSQL folds unquoted identifiers to lowercase, so Datrise normalizes mixed-case source fields to snake_case.

Ideal for operational analytics and application backends that need fresh, queryable copies of your data.

Endpoints

Sailthru: Personalized email and onsite content targeting.

PostgreSQL: Open-source relational database with strong SQL and extensions.

How Sailthru entities map to PostgreSQL

Sailthru entity	PostgreSQL object	Notes
users	`sailthru_users`	id PK · custom fields → jsonb columns
campaigns	`sailthru_campaigns`	id PK · linked to sailthru_users
blasts	`sailthru_blasts`	id PK · linked to sailthru_users
message events	`sailthru_message_events`	timestamptz events

FAQ

How does Datrise handle Sailthru's custom fields in PostgreSQL?

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 PostgreSQL types.

How does the Sailthru to PostgreSQL sync stay up to date?

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

Related pipelines

Early access

Connect Sailthru to PostgreSQL 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.