Define the Ingestion API schema

Updated Nov 8, 2026 · Based on Salesforce developer docs retrieved 2026-11-08

A schema file tells the Ingestion API connector what you’re sending: each object type and its fields. Upload it to the connector so Data 360 can validate incoming data and map it into the data model objects (DMOs — the defined data tables in Data Cloud) you’ll use downstream.

Define and upload the schema

1. List the object types you’ll send (for example, a product view event) and each one’s fields and data types.
2. Save that definition as a schema file, following the format your connector’s setup screen specifies.
3. On the Ingestion API connector, upload the schema file.
4. Map the resulting data lake objects (DLOs — the raw, as-ingested tables Data 360 creates from your schema) to the data model objects you need.
5. Validate the schema and resolve any field-type mismatches before sending real traffic.

Illustrative shape only — not a verified Salesforce example:

{
"objectType": "ProductView",
"fields": [
  { "name": "individualId", "type": "string", "required": true },
  { "name": "productId", "type": "string", "required": true },
  { "name": "viewedAt", "type": "datetime", "required": true }
]
}