Google Analytics 4 to Birst Integration

How Datrise loads Google Analytics 4 into Birst

Datrise syncs Google Analytics 4's events, users, sessions, traffic sources, conversions, and audiences into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.

Ideal for networked, governed enterprise BI.

Endpoints

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

Birst: Cloud BI with networked analytics and enterprise semantic layers.

How Google Analytics 4 entities map to Birst

Google Analytics 4 entity	Birst object	Notes
events	`ga4_events`	date/time dimensions 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 Birst?

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

How does the Google Analytics 4 to Birst sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.

Related pipelines

Early access

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