DatriseAI-first ETL

Iterable Looker

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

How Datrise loads Iterable into Looker

Datrise syncs Iterable's users, campaigns, journeys, message events, and experiments into Looker as governed warehouse tables with LookML-ready naming. Flexible or custom fields land in flattened columns (nested fields expanded for modeling), and timestamps such as created, updated, and status changes are typed as date/time dimension columns.

Sync is incremental: Datrise uses incremental refresh of the underlying warehouse tables Looker explores, so re-runs update only what changed. Date-partitioned fact tables for PDT performance. Looker models live in LookML on top of SQL, so Datrise lands clean, stable column names rather than churn that would break your views.

Ideal for governed, version-controlled BI on a warehouse.

Endpoints

Iterable: Cross-channel marketing automation and journeys.

Looker: Google Cloud BI with LookML semantic models and governed dashboards.

How Iterable entities map to Looker

Iterable entityLooker objectNotes
usersiterable_usersid PK · custom fields → flattened columns (nested fields expanded for modeling)
campaignsiterable_campaignsid PK · linked to iterable_users
journeysiterable_journeysid PK · linked to iterable_users
message eventsiterable_message_eventsdate/time dimension columns events

FAQ

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

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

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

It runs incrementally — Datrise uses incremental refresh of the underlying warehouse tables Looker explores.

Related pipelines

Early access

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