Connectors

A connector is how a data source gets its events into Data 360 for Personalization to use — each one is built for a different kind of source (a website, a mobile app, a server you control, or an existing analytics tool), so you pick one connector per data source rather than one for the whole implementation.

Which connector?

Connector comparison
WebsiteMobileIngestion APIGA4Server-to-Server
Best forWeb pages and SPAsiOS / Android / Flutter / React Native appsServer-to-server and backend eventsTeams already running Google Analytics 4Backend systems that need auth sorted first
ClientInteractions SDK (Personalization module)Unified Mobile SDKHTTP + connected app (OAuth)GA4 BigQuery Export (exact mechanism unconfirmed — see its page)Ingestion API REST endpoints via OAuth 2.0 server-to-server flow
CapturesPage views, behavioral eventsIn-app engagement + profile dataAny schema you defineExisting GA4 event and parameter dataAny schema you define, same as the Ingestion API
Setup effortLow–medium (SDK + sitemap)Medium (app integration)Medium–high (auth + schema + streams)Medium (depends on the ingestion mechanism — unconfirmed)Medium–high (connected app + OAuth flow + schema + streams)
Needs app codeSnippet in site headSDK in the app buildBackend integrationNo new tracking code — reuses existing GA4 dataBackend integration

Follow the setup for your connector:

  • Website — SDK, sitemap, event schema, consent and data streams.
  • Mobile — the handover checklist and schema configuration.
  • Ingestion API — connected app, auth, schema, Postman and data stream.
  • GA4 — bring existing Google Analytics 4 data into Data 360 without re-instrumenting your site or app.
  • Server-to-Server — the Ingestion API’s auth-first track for backend systems: connected app and OAuth 2.0 server-to-server flow, then schema and verification.

Discussion

Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).

Support SF Guide

SF Guide is a free, independent guide to Salesforce Personalization, built and maintained in the open. If it saved you time on an implementation, a small contribution helps keep it current and ad-light.