When you provision Data 360, it's connected to your Salesforce org and has access to data from B2B Commerce and Salesforce Order Management. You can use connectors to bring data into Data 360 from other sources, such as order data from B2C Commerce or engagement data from websites and mobile apps.
This table shows common connectors for commerce, the data they bring into Data 360, how credit consumption applies, and links to resources that explain how the data source objects are mapped to data model objects (DMOs) in Data 360. The table also includes a link to a resource that describes how to set up the connector.
| Connector | Data Source | Credit Consumption | Data Mapping | Learn More |
|---|---|---|---|---|
| Web and Mobile Apps |
|
Ingestion of structured data via this connector is included in Data 360. | Engagement Events Integration Reference | Ingesting B2C Commerce Engagement Events |
| Salesforce B2C Commerce Intelligence |
|
Bath ingestion of structured data via this connector is included with Data 360. Data federation via this connector is included for customers using Data 360 Flex Credits, but metered for customers with Data Services credits. | Create a Salesforce B2C Commerce Intelligence Data Stream | Salesforce B2C Commerce Intelligence Connector |
| Apache Iceberg File Federation |
|
Data federation is included with Data 360 for customers who use Data 360 Flex Credits. For customers who use Data Services credits, data federation is metered. See Billing Considerations for Data Federation. |
B2C Commerce Domain Data Mappings | Ingest B2C Commerce Domain Data Using the Apache Iceberg Connector |
|
Salesforce CRM (connected during Data 360 provisioning) |
|
Ingestion of structured data via this connector is included in Data 360. | Salesforce Commerce Data Bundle Mapping | Salesforce CRM Connector |
| Omnichannel Inventory |
|
This connector is billed as data ingestion or data federation, depending on how you set it up. See Billing Considerations for Data Ingestion and Billing Considerations for Data Federation. |
Omnichannel Inventory Data Mapping | Omnichannel Inventory Connector |
You can also expand your data source possibilities using SDKs, the Ingestion API, the MuleSoft Anypoint Connector, or one of our third-party integrations. See Data 360: Connectors and Integrations for a list of available connectors and their associated documentation. Also see Data 360 Pricing for information about rates.
Activity After Ingestion
Credit consumption for data ingestion or data federation is separate from credit consumption for other Data 360 services. Transforms, queries, and data federation can consume credits. To understand how services in Data 360 are billed,see Data 360 Consumption: Quick Look.
B2C Commerce CDP Connector
The B2C Commerce CDP Connector is no longer recommended. For current connector options, use the connectors in this table.