Listrak to Metabase Integration

How Datrise loads Listrak into Metabase

Datrise syncs Listrak's contacts, lists, campaigns, message events, orders, and segments into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Listrak: Retail email, SMS, and behavioral marketing.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Listrak entities map to Metabase

Listrak entity	Metabase object	Notes
contacts	`listrak_contacts`	id PK · custom fields → flattened columns for the question builder
lists	`listrak_lists`	id PK · linked to listrak_contacts
campaigns	`listrak_campaigns`	id PK · linked to listrak_contacts
message events	`listrak_message_events`	temporal columns for trends events

FAQ

How does Datrise handle Listrak's custom fields in Metabase?

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

How does the Listrak to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Listrak to Metabase 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.