Smaily to Amazon Redshift Integration

How Datrise loads Smaily into Amazon Redshift

Datrise syncs Smaily's subscribers, campaigns, lists, autoresponders, email events, and segments into Amazon Redshift as a typed table per source entity. Flexible or custom fields land in SUPER columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMPTZ.

Sync is incremental: Datrise uses COPY from staged files, then a delete-and-insert merge on stable id, so re-runs update only what changed. A DISTKEY on the join id and a SORTKEY on the load timestamp. Redshift performance hinges on dist/sort keys, so Datrise picks them from your entity ids and sync timestamps rather than defaulting to EVEN distribution.

Ideal for AWS-native warehouses already using the Redshift ecosystem.

Endpoints

Smaily: Email and SMS campaigns with subscriber segments.

Amazon Redshift: AWS petabyte-scale warehouse with Spectrum.

How Smaily entities map to Amazon Redshift

Smaily entity	Amazon Redshift object	Notes
subscribers	`smaily_subscribers`	id PK · custom fields → SUPER columns
campaigns	`smaily_campaigns`	id PK · linked to smaily_subscribers
lists	`smaily_lists`	id PK · linked to smaily_subscribers
autoresponders	`smaily_autoresponders`	id PK · linked to smaily_subscribers

FAQ

How does Datrise handle Smaily's custom fields in Amazon Redshift?

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

How does the Smaily to Amazon Redshift sync stay up to date?

It runs incrementally — Datrise uses COPY from staged files, then a delete-and-insert merge on stable id.

Related pipelines

Early access

Connect Smaily to Amazon Redshift 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.