--- schema_version: "1" id: e657d50aefd066a102d8f207928ce98eed5533a76e69c892e26c6240d56d4c69 title: Ingest B2C Commerce Domain Data Using the Apache Iceberg Connector collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_data_cloud_iceberg_domain_data.md canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_data_cloud_iceberg_domain_data.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: adc48d005deb00fd38316ee3c4e74c2db8e9c6293791d4283f069a33122e8cc1 description: Set up the Apache Iceberg File Federation connection to ingest B2C Commerce domain data—including products, orders, customer profiles, and custom attributes for products and customer profiles—into Data 360. products: - Commerce - B2C Commerce release: "264" --- # Ingest B2C Commerce Domain Data Using the Apache Iceberg Connector Set up the Apache Iceberg File Federation connection to ingest B2C Commerce domain data—including products, orders, customer profiles, and custom attributes for products and customer profiles—into Data 360. ### Required Editions
User Permissions Needed
To create a connection: System Admin profile or Data Cloud Architect permission set
Before you set up the Apache Iceberg connection, complete these prerequisite steps: - [Configure Catalog and Order Feeds for B2C Commerce Einstein Deployment](https://help.salesforce.com/s/articleView?id=cc.b2c_configure_einstein_deployment.htm&language=en_US) - [Configure the Export of Registered Shopper Profiles](https://help.salesforce.com/s/articleView?id=cc.b2c_data_cloud_configure_shopper_profiles_feature.htm&release=264.0.0&type=5 "Export registered B2C Commerce shopper profiles for specific sites and profiles modified after a certain date. The exported profiles are then ingested into Data 360 using the Apache Iceberg connector. A job that performs the ingestion runs once a day. Shopper profiles are visible in Data 360 about an hour after the job completes.") Data is automatically available only from live production instances. For more information about non-production instances, see [Using Non-Production B2C Commerce Environments with Data 360](https://help.salesforce.com/s/articleView?id=cc.b2c_data_cloud_non_production_environments.htm&language=en_US&type=5). The Apache Iceberg File Federation connector enables you to ingest all B2C Commerce domain data into Data 360. This includes: - Products (goods products, master products, bundles) - Product catalogs and categories - Sales orders and order details - Customer profiles - Custom attributes for products and customer profiles After you set up the connection, you must manually map the source objects to Data Model Objects (DMOs). For information about the available source objects and their mappings, see [B2C Commerce Domain Data Mappings](https://help.salesforce.com/s/articleView?id=cc.b2c_data_cloud_domain_data_mappings.htm&release=264.0.0&type=5 "When ingesting B2C Commerce domain data using the Apache Iceberg connector, you must manually map these source objects to Data Model Objects (DMOs) in Data 360."). For detailed information about the source table schemas, see [B2C Commerce Lakehouse Schema Reference](https://help.salesforce.com/s/articleView?id=cc.b2c_data_cloud_lakehouse_entity_tables.htm&release=264.0.0&type=5 "The B2C Commerce Data Lakehouse stores product catalog, customer, and sales order data in entity tables that use the ccdl_ prefix."). 1. In Data 360, click **Setup**, and select **Data Cloud Setup**. 2. Under External Integrations, select **Other Connectors**. 3. Click **New**. 4. On the Source tab, select **Apache Iceberg File Federation** and click **Next**. 5. Enter a connection name and connection API name. 6. Enter the authentication details. B2C Commerce data store's REST catalog supports storage credential vending, so select Storage Type as **CATALOG\_PROVIDED**. For REST Catalog, in the **Client Access Token** field, enter the Base64 encoded value of `{tenant_id}:{account_manager_client_id}:{account_manager_client_secret}`. To obtain these values: - **tenant\_id**: The tenant ID is part of your B2C Commerce organization ID. The organization ID has the format `f_ecom_{tenant_id}`. For example, if your organization ID is `f_ecom_zzzz_001`, the tenant ID is `zzzz_001`. - **account\_manager\_client\_id**: The Client ID generated when you create an API client in Account Manager. - **account\_manager\_client\_secret**: The password you set when creating the API client in Account Manager. The Account Manager client must have the **Salesforce Commerce API** role. When you assign this role, use the instance filter to find and add your production B2C Commerce instance. For information about creating an Account Manager API client, see [Add an API Client in B2C Commerce](https://help.salesforce.com/s/articleView?id=cc.b2c_account_manager_add_api_client_id.htm&release=264.0.0&type=5 "Account administrators use Account Manager to create API clients. To access Salesforce Commerce API (Shopper Commerce API [SCAPI]) or Open Commerce API [OCAPI]), use an API client. Append the API client ID to the URLs that you use to access these APIs. The On-Demand Sandbox API also requires an API client."). When performing the steps in that topic to set up an API client for the Iceberg connector, perform step 9 (assigning the Salesforce Commerce API role with instance filters) because it is required for the Iceberg connector. Do not perform steps 10 and 11 (Default Scopes and OpenID Connect settings) because they don't apply to this connector. 7. Enter the Connection Details. For **Catalog Endpoint**, enter the Data Cloud accessible HTTPS URL of the Apache Iceberg REST catalog: - **Production**: `https://iceberg-catalog.analytics.commercecloud.salesforce.com` - **Non-production**: `https://iceberg-catalog.stg.analytics.commercecloud.salesforce.com` Leave the optional **Warehouse** field blank. 8. To review your configuration, click **Test Connection**. 9. Click **Save**. After the connector details are accepted, the connection is created and listed under Connectors. Now you can create data streams and map your B2C Commerce data to DMOs. After setting up the connection, create data streams for the B2C Commerce objects you want to ingest. For information about creating data streams and mapping source objects to DMOs, see [Create an Apache Iceberg File Federation Data Stream](https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-create-apacheiceberg-file-fed-data-stream.html). - **[B2C Commerce Domain Data Mappings](https://help.salesforce.com/s/articleView?id=cc.b2c_data_cloud_domain_data_mappings.htm&release=264.0.0&type=5)** When ingesting B2C Commerce domain data using the Apache Iceberg connector, you must manually map these source objects to Data Model Objects (DMOs) in Data 360. - **[B2C Commerce Lakehouse Schema Reference](https://help.salesforce.com/s/articleView?id=cc.b2c_data_cloud_lakehouse_entity_tables.htm&release=264.0.0&type=5)** The B2C Commerce Data Lakehouse stores product catalog, customer, and sales order data in entity tables that use the `ccdl_` prefix. #### See Also - [Set Up an Apache Iceberg File Federation Connection](https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-set-up-apacheiceberg-file-fed-connection.html) - [Create an Apache Iceberg File Federation Data Stream](https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-create-apacheiceberg-file-fed-data-stream.html)