Server-to-Server connector

Updated Nov 7, 2026 · Based on Salesforce docs updated 2026-08-27

The Server-to-Server connector covers getting backend and server data into Data 360 for Personalization using the Ingestion API’s REST endpoints, authenticated through Salesforce’s OAuth 2.0 server-to-server flow (JWT bearer or client credentials) instead of a user login.

How this differs from the other connectors

• Website / Mobile SDK — client-side; code runs in the browser or app, and auth uses a publishable key tied to that SDK. No backend secrets.
• Ingestion API — the same REST surface this connector also uses, written for teams who already think of their integration as “call the Ingestion API.”
• Server-to-Server — the same Ingestion API REST surface, but set up auth-first: stand up a connected app, complete a JWT-bearer or client-credentials OAuth flow, and exchange that for a Data 360 access token before sending a single event. Pick this track if your starting point is a backend system that needs its server-to-server auth sorted before anything else.

Work through these pages in order:

• Set up auth and credentials — create a connected app and complete the server-to-server OAuth flow.
• Map your event schema — define and map the objects and fields your backend sends.
• Verify and hand over — confirm data is flowing and complete the handover checklist.