Product Updates
Back to All
Added

Salesforce Data Cloud — bidirectional integration with imports, streaming exports, and zero-copy bulk

2 days ago

The Salesforce Data Cloud integration connects Lytics with Salesforce Data Cloud so you can import unified Individual profiles, segment membership, and calculated insights into Lytics, and send Lytics audiences and user fields back to Data Cloud either in real time via the Ingestion API or in bulk via Google Cloud Storage for zero-copy ingestion.

What's included

  • Imports

    • Import Data Cloud Segment Membership — pulls the unified Individual DMO plus UnifiedContactPointEmail, UnifiedContactPointPhone, UnifiedContactPointAddress, and segment membership into Lytics streams (sdc_individuals, sdc_contact_point_emails, sdc_contact_point_phones, sdc_contact_point_addresses, sdc_segments). Active segment names are accumulated into a Lytics user field for direct audience targeting.
    • Import Data Cloud Calculated Insights — pulls calculated insight results into a Lytics stream on a configurable schedule.
    • Import Data Cloud Change Events — polls Data Cloud for CREATE / UPDATE / DELETE events on selected Data Model Objects, with a configurable poll interval and lookback window.

  • Exports

    • Export Audience Membership to Data Cloud — keeps a Lytics audience in sync with a Data Cloud Ingestion API target object in real time, sending adds and removes keyed by a chosen match field.
    • Export Users to Data Cloud — streams Lytics user fields to a Data Cloud Ingestion API object using a custom field mapping, with a configurable batch size (max 200, the Data Cloud limit) and per-hour rate limit.
    • Bulk Export to Data Cloud via GCS — stages a CSV or newline-delimited JSON file in a Google Cloud Storage bucket for Data Cloud zero-copy ingestion — the high-volume path when per-record API calls aren't a fit.

What you need to do

  • Create a Salesforce Data Cloud authorization in Lytics using JWT Bearer Token (or JWT Bearer Token (Sandbox)). The integration requires a Salesforce External Client App configured with the Data Cloud OAuth scopes (cdp_query_api, cdp_ingest_api, cdp_profile_api, cdp_calculated_insight_api, cdp_segment_api) and digital-signature auth — there is no browser-based OAuth flow for Data Cloud.
  • For Ingestion API exports, your Salesforce admin needs to set up an Ingestion API source and target object in Data Cloud first.
  • For the GCS bulk export, you need a Google Cloud Storage bucket configured as a Data Cloud zero-copy data source.

See Salesforce Data Cloud for the full setup walkthrough, including the External Client App prerequisites, field mappings for each import stream, and per-job configuration steps.