DatriseAI-first ETL

Facebook Marketing Metabase

AI-first ETL from Facebook Marketing into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Facebook Marketing into Metabase

Datrise syncs Facebook Marketing's records, events, and configuration objects 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

Facebook Marketing: SaaS or API data source for analytics and warehouse sync.

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

How Facebook Marketing entities map to Metabase

Facebook Marketing entityMetabase objectNotes
recordsfacebook_marketing_recordsid PK · custom fields → flattened columns for the question builder
eventsfacebook_marketing_eventstemporal columns for trends events
configuration objectsfacebook_marketing_configuration_objectsid PK · linked to facebook_marketing_records

FAQ

How does Datrise handle Facebook Marketing'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 Facebook Marketing to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Facebook Marketing 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.