Real-Time Ingestion

Data 360 can ingest data in real-time using your existing Ingestion API integrations. To do so for an Ingestion API Data Lake Object (DLO), make sure that the Data Model Object (DMO) the DLO is mapped to, is a member of a real-time data graph.

After ingestion, the data is available in the real-time layer instantly so that it can power real-time identity resolution, real-time calculated insights, real-time segmentation, and real-time actions.

In typical production scenarios, 95% of events complete end-to-end ingestion from capture through real-time layer activation within approximately 500 milliseconds under the Sub-Second Real-Time Profile. Actual performance can vary based on your source system, network conditions, data volume, transformation logic, and real-time data graph configuration. Real-time ingestion supports multiple channels, including Web SDK, Mobile SDK, and Server-to-Server (S2S) ingestion.

  • Only streaming data ingestion is supported: Bulk data ingestion is not supported for real-time data ingestion.
  • Ingested objects need a foreign key relationship with the DMO: Real-time ingestion only ingests objects that have a foreign key qualifier field mapped to the primary DMO of the real-time data graph. Events without the foreign key qualifier field are synced through the standard Data 360 pipeline. For example, if your data graph is of a unified individual the primary DMO is an individual. See Fully Qualified Key in Data Objects.
  • Cannot delete data in real-time: Data can only be appended or updated in real-time. Any delete operation is performed using the standard Data 360 pipeline ingestion process.
  • During Upsert, old records aren’t deleted in real-time: Any new data that is upserted will be done so in real-time. However, any deletes to be made on the old records are not in real-time and are only performed using the standard Data 360 pipeline.
  • Billing is based on SSRT events and API usage type: Your Data 360 Services card is charged for events ingested in real-time.
  • Real-time data ingestion is enabled by default for all newly created real-time data graphs: If you don’t want to ingest data in real-time, you can disable it.

If you don't want to ingest data in real-time, navigate to the Real-Time Consumption Limits page in the New Data Graph window and toggle Real-Time Data Ingestion to Off. When you turn off real-time ingestion, data is synced through the standard Data 360 pipeline.

Imagine you work for an auto manufacturer. Your objective is to create a service where you can identify when a vehicle has broken down, and proactively reach out to the customer who owns the vehicle, and send roadside assistance. Using Real-Time Ingestion API, you can ingest the vehicle telemetry data in real-time into Data 360. With this data, you can identify a break-down in real-time and create a support case in Service Cloud to send assistance.