Loading
Salesforce now sends email only from verified domains. Read More
About Salesforce Data 360
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Create a B2C Commerce Data Stream

            You are here:

            1. Salesforce Help
            2. Docs
            3. Data 360

            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 Editions

            Available in: All Editions supported by Data 360. See Data 360 edition availability.
            User Permissions Needed
            To create a data stream Permission set: Data Cloud Architect
            1. Enable Commerce Einstein tracking in your B2C Commerce instance.
              The Order Bundle includes these entities:
              • Bundle Product (supports custom field attributes)
              • Goods Product (supports custom field attributes)
              • Master Product (supports custom field attributes)
              • Product Catalog
              • Product Category
              • Product Category Product
              • Product Option
              • Product Option Value
              • Product Product Option
              • Sales Order
              • Sales Order Customer
              • Sales Order Product
              • Sales Order Product Option Value
              • Customer Profile
            2. In Data 360, go to the Data Streams tab and click New.
            3. Select the B2C Commerce data source and click Next.
            4. Select a B2C Commerce instance and click Next.
              Only a B2C Commerce production instance can be selected. If you have only one instance connected to Data 360, it’s selected by default.
            5. Select the order bundle that includes the order, product, and customer data.
              If you have only one instance, its order bundle is selected by default.
            6. Review the fields to include in your data stream, and deselect the fields that you don’t want.
            7. To add a formula field, click New Formula Fields.
              1. Add a display name for the Field Label. Refer to the list of reserved field names below. Don't use any of the names from this list in your formula fields.
              2. If desired, update the Field API name.
              3. Enter the Formula Return Type, which is the field’s data type.
              4. Define a formula using the search function, attributes, and transformation formula options.
              5. Click Save.
            8. Review the data stream and click Next.
            9. Click Deploy.
              Allow at least 24 hours for the data to ingest.

            When you establish a connection between B2C Commerce and Data 360, the B2C Commerce Connector ingests 30 days of historical data. For example, if you establish a connection on May 1, the connector ingests historical data from April 2 to May 1. From that date forward, the connector continues to ingest data.

            Note
            Note For customers who have opted out of tracking using the B2C Commerce standard do-not-track (DNT) cookie, the B2C Commerce Connector prevents data ingestion. If a customer opts in to data tracking, and later opts out, new data isn’t ingested into Data 360, but previously ingested data remains. Customers can use the Data 360 data deletion feature to remove user data.

            Reserved Field Names: The following standard field names are reserved and can’t be used as B2C Commerce custom attributes when imported into Data 360. If custom attributes using reserved field names are encountered, this may cause inaccurate data to be ingested into Data 360, 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

            Rights of ALBERT EINSTEIN are used with permission of The Hebrew University of Jerusalem. Represented exclusively by Greenlight.

            See Also

             
            Loading
            Salesforce Help | Article