Google Analytics 4 to Metabase Integration

How Datrise loads Google Analytics 4 into Metabase

Datrise syncs Google Analytics 4's events, users, sessions, traffic sources, conversions, and audiences 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

Google Analytics 4: Event-based web and app analytics from Google.

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

How Google Analytics 4 entities map to Metabase

Google Analytics 4 entity	Metabase object	Notes
events	`ga4_events`	temporal columns for trends events
users	`ga4_users`	id PK · linked to ga4_events
sessions	`ga4_sessions`	id PK · linked to ga4_events
traffic sources	`ga4_traffic_sources`	id PK · linked to ga4_events

FAQ

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

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

Related pipelines

Early access

Connect Google Analytics 4 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.