GA4 connector

Updated Nov 7, 2026 · Based on web research dated 2026-11-07

Google Analytics 4 (GA4) is Google’s event-based web and app analytics platform — most teams already have it installed on their site or app to track page views, clicks and conversions. The GA4 connector brings that existing GA4 data into Data 360, so Personalization can reuse it for segments, recommendations and experiences without re-instrumenting your site or app.

GA4 itself only exposes raw, event-level data in bulk through BigQuery Export — a daily or streaming export of your GA4 property’s events into a Google Cloud BigQuery dataset you own. Whether that export is what Data 360 reads from for this connector is part of the ingestion mechanism flagged above as unconfirmed.

When to use the GA4 connector

• You already run GA4 on your website or app and don’t want to add a second tracking SDK alongside it.
• You want existing GA4 engagement history, not just events captured from today onward.

Use the Website or Mobile connector instead if you don’t have GA4 in place, or if you need guaranteed real-time event delivery — this connector’s delivery timing isn’t confirmed (see the Callout above). Use the Ingestion API instead for server-to-server events that never pass through GA4 at all.

Setup flow at a glance

Work through these pages in order:

• Prerequisites and access — confirm your GA4 property and the Salesforce permissions you need before you start (see the Callout above — the exact access required depends on the ingestion mechanism).
• Connect the data source — set up the connection between Data 360 and your GA4 data (see the Callout above for the mechanism this depends on).
• Map the schema — match GA4’s event and parameter fields to Data 360 objects.
• Verify and create the data stream — confirm data is arriving, then turn it into a stream Personalization can use.