Source connector

GA4 connector

GA4 integration for databases, warehouses and BI tools

Event-based web and app analytics from Google. Datrise captures Google Analytics 4 entities such as events, users, sessions, traffic sources, conversions and audiences, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Google Analytics Data API v1 (GA4) authenticates with OAuth 2.0, service account, and GA4 caps calls at 200,000 Core report tokens/property/day and 40,000/property/hour on standard properties (2,000,000/day, 400,000/hour on Analytics 360); 10 concurrent requests per property (50 on 360); 120 potentially-thresholded requests/hour when querying sensitive dimensions like userAgeBracket.

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `ga4_events`) with a schema derived from the GA4 API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the GA4 pipeline page, and join the waitlist to get the GA4 connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Google Analytics 4 data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
events	ga4_events	Append-only, incremental by timestamp
users	ga4_users	Upsert by primary key, incremental on updated-at
sessions	ga4_sessions	Append-only, incremental by timestamp
traffic sources	ga4_traffic_sources	Upsert by primary key, incremental on updated-at
conversions	ga4_conversions	Upsert by primary key, incremental on updated-at
audiences	ga4_audiences	Upsert by primary key, incremental on updated-at

Google Analytics 4 API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Google Analytics Data API v1 (GA4)
Authentication	OAuth 2.0, service account — OAuth 2.0 (user consent) or a Google Cloud service account granted Viewer/Analyst access on the GA4 property; both use standard Google Cloud credential flows.
Pagination	offset — `runReport`/`runPivotReport` return up to 10,000 rows per call and page further with `limit`/`offset`, not a cursor token.
Rate limit	200,000 Core report tokens/property/day and 40,000/property/hour on standard properties (2,000,000/day, 400,000/hour on Analytics 360); 10 concurrent requests per property (50 on 360); 120 potentially-thresholded requests/hour when querying sensitive dimensions like userAgeBracket
Incremental cursor	Not published
Webhooks	No
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Google Analytics 4

Daily-processed data isn't final for 24-48 hours, and reports pulled during that window apply stricter cardinality limits than the eventual daily table, so a connector that reads `today`/`yesterday` immediately and never re-pulls will both undercount and see more `(other)` rows than the final numbers.
High-cardinality dimension combinations collapse excess rows into a single `(other)` bucket once the report table's row limit is hit, silently losing the underlying dimension breakdown rather than erroring.
Standard properties are capped at 200,000 Core tokens/property/day and 40,000/hour, and each report's token cost scales with requested dimensions, metrics, and date-range size, so a wide multi-dimension report can burn the hourly quota in a handful of calls.
Queries on privacy-sensitive dimensions such as `userAgeBracket` or `userGender` are separately capped at roughly 120 potentially-thresholded requests/hour and can return privacy-thresholded (withheld) rows below Google's minimum user count, which a raw row count will not flag as incomplete.

Compare this against every other documented API

Popular destinations for Google Analytics 4

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Google Analytics 4 connector FAQ

What GA4 data does the connector extract?: 6 objects: events, users, sessions, traffic sources, conversions and audiences. Each lands in its own table with types preserved; history-style objects (2: events and sessions) load as append-only streams.
Is the GA4 integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load GA4 data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each GA4 → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Google Analytics 4 pipeline with guided onboarding

Join the waitlist to get priority access for Google Analytics 4 integrations with guided setup, schema-aware mapping, and production-grade incremental sync.