Commerce Cloud connects the customer journey and drives success from anywhere with customer-centric commerce built for every industry.
Completely connect your digital customer journey.
- Personalize engagement with customer-centric commerce.
- Unify data, personalize every interaction, and grow revenue across channels with automation, AI, and a single source of truth.
Connect commerce to the customer journey.
- Convert more customers and drive loyalty with a seamless customer journey from marketing to sales, commerce, fulfillment, service, and beyond. Build with your choice of clicks- or code-based tools.
Adapt quickly with an agile, scalable, and secure platform.
- Innovate at the speed of your customers, scale easily across the globe, and meet any level of demand. Extend your commerce with a partner ecosystem of apps to deliver experiences like augmented reality, marketplaces, and more.
- Salesforce Commerce Cloud Import Integration will provide the following abilities:
- Authenticate using API Client via OAuth.
- Ingest customer information for a specific list
- Ingest of Customer resources, for example:
- customer information
- name, gender, email
- Ingest Product resource, for example:
- a list of products
- product information
- Ingest Inventory and Product Inventories resource, for example:
- list of inventories
- product inventory allocation
- product inventory stock level
- product inventory ID
- Ingest Category and Product Assignments resource, for example:
- category information
- product belongs to each category
- Ingest Store resources, for example:
- all stores
- store information including id, address, postal code, country, inventory id
- Ingest Catalog resources, for example:
- catalog info
- assigned product counts
- Basic Knowledge of Treasure Data
- Basic knowledge of Treasure Data CLI
- Basic knowledge of Salesforce Commerce Cloud
- Basic knowledge of Open Commerce Cloud API
- Commerce Cloud Account Manager System Access
- The application secret should not contain the
%character. Due to an internal issue with the SFCC authentication server, any secret the contains the% character, is not able to authenticate. - Incremental loading is only supported for Creation Date, not Modified Date
- A large volume of data may cause low performance
- In preview mode, the connector does not support generating the detailed data preview because of time restrictions on fetching the data preview.
- An Inventory List with no product is still inserted as one record, the properties belong to the Product Inventory List and will be null.
Incremental loading is loading only new or updated records from a source into Treasure Data. It is helpful because it runs efficiently compared to full loads, particularly for large data sets.
Incremental loading is available for many of the Treasure Data integrations. In some cases, it is a simple checkbox choice; in others, after you select incremental loading, you are provided with other fields that must be specified.
Treasure Data Incremental loading has four patterns (3 types of data connector + 1 workflow td_load operator.), and the 3 data connector loading examples are as follows:
Cloud storage service (e.g., AWS S3, GCS, etc.)
- Lexicographic order of file name
Query (e.g., MySQL, BigQuery, etc.)
- Date time
Variable period (Google Analytics, etc)
- Use start_date for loading
If incremental loading is selected, data for the connector is loaded incrementally.
This mode is useful when fetching just the object targets that have changed since the previously scheduled run.
For example, in the UI:

Database integrations, such as MySQL, BigQuery, and SQL Server, require column or field names to load incremental data.

Learn more about Database-Based Integrations.
- For some integrations, if you choose incremental loading, you might need to ensure that the columns have an index to avoid a full table scan.
- Only Timestamp, Datetime, and numerical columns are supported as incremental_columns.
- The incremental_columns is required for the raw query because it cannot detect the Primary keys for a complex query.
These steps are necessary to create the credentials that are needed to define the authentication for your integration.
- Navigate to the Salesforce Cloud Commerce UI and login. For example, Account Manager UI.

- Select API Client.

- Select Add API Client.

- Type values for:
- Display Name
- Password
- Confirm Password
Select Access Control to enable it.
In the Organizations area, select your organization.
In the Roles area, select Add.
Select the appropriate role. For example, Sandbox API User.

Select Add.
After the role is added, select all the sandboxes associated with it.

Select Add.
Scroll down to Open ID Connect.
Add Default Scopes:
- roles
- tenantFilter
- profile
- Add Redirect URI. For example:
https://admin.us01.dx.commercecloud.salesforce.com/oauth2-redirect.html
Scroll totheToken Endpoint Auth Methodsection.
Select client_secret_basic.
Select JWT for Access Token Format.

Select Save.
You are taken back to the API Client screen.

- Write down or save in a secure location the API Client ID and Password.
These are used as Authentication credentials to integrate with your SFCC instance.
These steps enable your API Client to be used with the Data APIand Salesforce B2C Commerce Cloud connector.
- Open Business Manager. For example:
Select Administration.
Select Open Commerce API Settings.

Select Type as Data.

The configuration for Data API appears.
- Type or copy the following into the text field:
{
"_v": "21.6",
"clients": [
{
"client_id": "your_api_client_id",
"resources": [
{
"methods": [
"get",
"post",
"put",
"patch",
"delete"
],
"read_attributes": "(**)",
"write_attributes": "(**)",
"resource_id": "/**"
}
]
}
]
}- For Select Context choose Global (organization-wide).

- Select Save.
Wait for at least 3 minutes.
Your API Client is ready to be used with Data APIand Salesforce B2C Commerce Cloud connector.
In Treasure Data, you must create and configure the data connection prior to running your query. As part of the data connection, you provide authentication to access the integration.
Open TD Console.
Navigate to Integrations Hub > Catalog.
Search for and select Salesforce B2C Commerce Cloud.

Choose Create Authentication.
The following dialog opens:

Type or select the required information:
| Parameter | Description |
|---|---|
| API Client ID | Key which you got after create your application on Commerce Cloud's Account Manager Application. |
| API Client Password | The password for your API Client when you create on Commerce Cloud's Account Manager Application. |
| Base URI | URL for accessing your Business Manager Application. Example value https://xxxx.commercecloud.salesforce.com/ |
- Type a name for your connection.

- Select Continue.
After creating the authenticated connection, you are automatically taken to Authentications.
- Search for the connection you created.

Select New Source.
Type a name for your Source in the Data Transfer field**.**

Select Next.
The Source Table dialog opens.
Edit the following parameters:

| Parameters | Description | Description of Data Types |
|---|---|---|
| Data Type | The data objects that you want to ingest into Treasure Data: | |
| Customers From List | The customer info from a specific customer list | |
| Products | Product info of Salesforce Commerce Cloud account | |
| Categories and Product Assignments | Product category info and products belong to each category | |
| Inventory Lists and Product Inventories | Inventory list and product in each inventory list | |
| Stores | Store info, location, and inventory belongs to stores | |
| Catalogs | Product catalog info and count of products for each catalog | |
| Customer List ID | The customer List ID you want to import customer information from | |
| Incremental loading | Select to ingest only newly created data since the previous ingestion. | |
| Created From | The specific time you would like to ingest the data (YYYYMMDDHH format). |
Select Next.
The Data Settings page can be modified for your needs or you can skip the page.
Optionally, edit the following parameters:

- Select Next.
You can see a preview of your data before running the import by selecting Generate Preview. Data preview is optional and you can safely skip to the next page of the dialog if you choose to.
- Select Next. The Data Preview page opens.
- If you want to preview your data, select Generate Preview.
- Verify the data.
For data placement, select the target database and table where you want your data placed and indicate how often the import should run.
Select Next. Under Storage, you will create a new or select an existing database and create a new or select an existing table for where you want to place the imported data.
Select a Database > Select an existing or Create New Database.
Optionally, type a database name.
Select a Table> Select an existing or Create New Table.
Optionally, type a table name.
Choose the method for importing the data.
- Append (default)-Data import results are appended to the table. If the table does not exist, it will be created.
- Always Replace-Replaces the entire content of an existing table with the result output of the query. If the table does not exist, a new table is created.
- Replace on New Data-Only replace the entire content of an existing table with the result output when there is new data.
Select the Timestamp-based Partition Key column. If you want to set a different partition key seed than the default key, you can specify the long or timestamp column as the partitioning time. As a default time column, it uses upload_time with the add_time filter.
Select the Timezone for your data storage.
Under Schedule, you can choose when and how often you want to run this query.
- Select Off.
- Select Scheduling Timezone.
- Select Create & Run Now.
- Select On.
- Select the Schedule. The UI provides these four options: @hourly, @daily and @monthly or custom cron.
- You can also select Delay Transfer and add a delay of execution time.
- Select Scheduling Timezone.
- Select Create & Run Now.
After your transfer has run, you can see the results of your transfer in Data Workbench > Databases.
| Configuration name | Type | Available when | Required | Sample value | Description |
|---|---|---|---|---|---|
| base_url | STRING | default | yes | https://xxxx.example.com | SFCC’s instance base url |
| catalog_id | STRING | target = categories | no | test | Catalog’s ID |
| client_id | STRING | default | yes | abcdef | Application’s ID |
| client_secret | STRING | default | yes | abcdef | Application’s Secret |
| customer_list_id | STRING | target = customers | yes if target = customers | test | Customer List Id |
| incremental | BOOLEAN | target = customers target = products target = catalog | no | true | Ingest incremental or not |
| initial_retry_wait | LONG | default | no | 1 | First wait time when retrying (in seconds) |
| inventory_list_id | STRING | target = inventory_lists | no | test | Inventory List’s ID |
| last_value | STRING | target = customers target = products target = catalog | no | 2021-05-25T02:49:29.000Z | The timestamp to start ingest data |
| levels | LONG | target = categories | yes if target = categories | 0 | Level of sub-category to ingest when target = categories |
| maximum_retries | LONG | default | no | 5 | Maximum number of retry |
| maximum_retry_wait | LONG | default | no | 120 | Max wait time when retrying (in seconds) |
| site_id | STRING | target = products target = stores | yes if target = stores | test | The Site ID |
| target | ENUM (customers , stores , categories , products , catalogs , inventory_lists ) | default | yes | customers | Target data type to ingest |
| product_inventory_records_count | INTEGER | target = inventory_lists | no | 300 | Count for retrieving only a subset of Product Inventory records. Default: 200, Min: 25 |
in:
type: salesforce_commerce_cloud
client_id: xxx
client_secret: yyy
base_url: https://{realm_id}-001.sandbox.us01.dx.commercecloud.salesforce.com/
target: customers
customer_list_id: phu_test
last_value: 2021-05-25T02:49:29.000Z
incremental: truein:
type: salesforce_commerce_cloud
client_id: xxx
client_secret: yyy
base_url: https://{realm_id}-001.sandbox.us01.dx.commercecloud.salesforce.com/
target: products
site_id: phu_test
incremental: true
last_value: 2021-05-25T02:55:28.000Zin:
type: salesforce_commerce_cloud
client_id: xxx
client_secret: yyy
base_url: https://{realm_id}-001.sandbox.us01.dx.commercecloud.salesforce.com/
target: stores
site_id: phu_test2in:
type: salesforce_commerce_cloud
client_id: xxx
client_secret: yyy
base_url: https://{realm_id}-001.sandbox.us01.dx.commercecloud.salesforce.com/
target: INVENTORY_LISTSin:
type: salesforce_commerce_cloud
client_id: xxx
client_secret: yyy
base_url: https://{realm_id}-001.sandbox.us01.dx.commercecloud.salesforce.com/
target: categories
catalog_id: phu_catin:
type: salesforce_commerce_cloud
client_id: xxx
client_secret: yyy
base_url: https://{realm_id}-001.sandbox.us01.dx.commercecloud.salesforce.com/
target: catalogs
incremental: true
last_value: 2021-05-26T02:55:28.000Z