You are here:
B2C Commerce Connector
You can connect your B2C Commerce instance to a production site and create a B2C Commerce data stream. The data stream ingests all data from active production sites, both protected or unprotected. This connector is for production sites only. You can’t set up a B2C Commerce connector to test, sandbox, or non-live production site.
The B2C Commerce Order Bundle deploys mappings to Contact Point type data model objects (DMOs). Identity resolution uses the DMOs to link multiple records in order to combine them into a unified customer profile.
In B2C Commerce, you can create custom attributes with the same name that are case-sensitive, for example, Sustainability and sustainability. However, Data 360 doesn’t support case-sensitive field names and converts all field labels to lowercase, which may introduce a conflict. If you have case-sensitive custom product attribute names, modify the field names in B2C Commerce before ingesting this data into Data 360 to avoid any data conflicts.
Reserved Field Names
The following standard field names are reserved and can’t be used as B2C Commerce custom attributes when imported into Data Cloud. If custom attributes using reserved field names are encountered, this may cause inaccurate data to be ingested into Data Cloud, and require transforming the data for that field by, for example, creating a formula field.
- version
- productId
- tenantId
- masterProductId
- simpleProduct
- optionProduct
- mastered
- bundledProduct
- name
- shortDescription
- longDescription
- minOrderQuantityValue
- minOrderQuantityUnit
- stepQuantityValue
- stepQuantityUnit
- unit
- unitQuantityValue
- unitQuantityUnit
- unitMeasure
- taxClassID
- sku
- manufacturerName
- manufacturerSKU
- brand
- upc
- ean
- validFrom
- validTo
- createdDate
- modifiedDate
When you first establish a connection between B2C Commerce and Data 360, the B2C Commerce Connector ingests the last 30 days of historical data. For example, if you establish a connection on May 1, the B2C Commerce Connector ingests historical data from April 2 to May 1. From this point forward, the B2C Commerce Connector continues to ingest data.
The B2C Commerce Order Bundle also deploys these data streams:
- Product Option
- Product Product Option
- Product Option Value
- Sales Order Product Option Value
If you use these objects within your B2C Commerce instance, map them to custom data model objects in Data 360 and configure the appropriate data model relationships.
- Set Up a B2C Commerce Connection
After you create your Data 360 instance, you can set up a B2C Commerce Connection. Then you can control the scope of data ingestion from B2C Commerce. The B2C Commerce connector only supports connections to production instances of B2C Commerce. - B2C Commerce Order Bundle Data Mappings
The B2C Commerce Order Bundle shows a sample of the key mappings organized by source objects. You can view all the mappings by reviewing your data streams after the bundle is deployed. - Create a B2C Commerce Data Stream
The only way to create and map B2C Commerce data streams is to create a data bundle called B2C Commerce Order Bundle. This data bundle includes specific entities, some of which support custom field attributes for mapping to a data model object (DMO), and it doesn't allow for individual data stream deployment. This deployment requires you to be a Data 360 admin. - Required Field Mappings to Activate to B2C Commerce
When activating a segment to B2C Commerce, certain data field mappings are required for B2C Commerce and non-B2C Commerce data sources.
