Google Analytics 4 to DuckDB Integration

How Datrise loads Google Analytics 4 into DuckDB

Datrise syncs Google Analytics 4's events, users, sessions, traffic sources, conversions, and audiences into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

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

DuckDB: In-process analytics database for fast local OLAP.

How Google Analytics 4 entities map to DuckDB

Google Analytics 4 entity	DuckDB object	Notes
events	`ga4_events`	TIMESTAMP WITH TIME ZONE 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 DuckDB?

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

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

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

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