DatriseAI-first ETL

Iterable Looker Studio

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

How Datrise loads Iterable into Looker Studio

Datrise syncs Iterable's users, campaigns, journeys, message events, and experiments into Looker Studio as warehouse tables Looker Studio connects to. Flexible or custom fields land in flattened columns for chart fields, and timestamps such as created, updated, and status changes are typed as date dimension columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned tables to keep extract refresh fast. Looker Studio performs best on pre-aggregated tables, so Datrise lands tidy, report-shaped tables rather than raw API payloads.

Ideal for free, shareable dashboards on Google data sources.

Endpoints

Iterable: Cross-channel marketing automation and journeys.

Looker Studio: Google self-service dashboards and reporting (formerly Data Studio).

How Iterable entities map to Looker Studio

Iterable entityLooker Studio objectNotes
usersiterable_usersid PK · custom fields → flattened columns for chart fields
campaignsiterable_campaignsid PK · linked to iterable_users
journeysiterable_journeysid PK · linked to iterable_users
message eventsiterable_message_eventsdate dimension columns events

FAQ

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

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

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

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

Related pipelines

Early access

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