DatriseAI-first ETL

Omnisend to Looker Integration

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

How Datrise loads Omnisend into Looker

Datrise syncs Omnisend's contacts, campaigns, automations, orders, message events, and segments 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

Omnisend: Ecommerce email and SMS marketing automation.

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

How Omnisend entities map to Looker

Omnisend entityLooker objectNotes
contactsomnisend_contactsid PK · custom fields → flattened columns (nested fields expanded for modeling)
campaignsomnisend_campaignsid PK · linked to omnisend_contacts
automationsomnisend_automationsid PK · linked to omnisend_contacts
ordersomnisend_ordersid PK · linked to omnisend_contacts

FAQ

How does Datrise handle Omnisend'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 Omnisend 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 Omnisend 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.