DatriseAI-first ETL

Iterable ThoughtSpot

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

How Datrise loads Iterable into ThoughtSpot

Datrise syncs Iterable's users, campaigns, journeys, message events, and experiments into ThoughtSpot as warehouse tables ThoughtSpot indexes for search. Flexible or custom fields land in flattened columns for searchable fields, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the indexed tables, so re-runs update only what changed. Date-partitioned facts for live-query performance. ThoughtSpot search relies on clear names and relationships, so Datrise lands well-named, joinable tables.

Ideal for natural-language search analytics over a warehouse.

Endpoints

Iterable: Cross-channel marketing automation and journeys.

ThoughtSpot: Search-driven analytics with AI-assisted insights on warehouse data.

How Iterable entities map to ThoughtSpot

Iterable entityThoughtSpot objectNotes
usersiterable_usersid PK · custom fields → flattened columns for searchable fields
campaignsiterable_campaignsid PK · linked to iterable_users
journeysiterable_journeysid PK · linked to iterable_users
message eventsiterable_message_eventsdate/time columns events

FAQ

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

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

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

It runs incrementally — Datrise uses incremental refresh of the indexed tables.

Related pipelines

Early access

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