DatriseAI-first ETL

Iterable PlanetScale

AI-first ETL from Iterable into PlanetScale. Governed entities, incremental sync, typed landing tables.

How Datrise loads Iterable into PlanetScale

Datrise syncs Iterable's users, campaigns, journeys, message events, and experiments into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

Iterable: Cross-channel marketing automation and journeys.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Iterable entities map to PlanetScale

Iterable entityPlanetScale objectNotes
usersiterable_usersid PK · custom fields → JSON columns
campaignsiterable_campaignsid PK · linked to iterable_users
journeysiterable_journeysid PK · linked to iterable_users
message eventsiterable_message_eventsDATETIME events

FAQ

How does Datrise handle Iterable's custom fields in PlanetScale?

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

How does the Iterable to PlanetScale sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Iterable to PlanetScale 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.