The Agentforce Commerce Client is distributed as an npm package under the name @cimulate/copilot-widget.
Some storefront frameworks require a unique enablement path, such as Storefront Next, which uses the B2C Shopper Agent for setup and container configuration.
Record Connection Channel Settings for Client Installation
The Agentforce Commerce Client requires connection information to communicate to the Salesforce org’s Agentforce messaging channel. SFRA, PWA Kit, and Storefront Next storefronts need these details because all three load the same client and connect to the same back end.
Record the connection values from the Salesforce org’s Embedded Service Deployment. You use them later when configuring the client for your storefront.
Locate the connection settings in your Salesforce org.
In your Salesforce org, go to Setup.
In the Quick Find box, enter and select Embedded Service Deployment.
Select the name of your deployment, and in the Code Snippet tile, click Install Code Snippet.
From the Custom Client Code Snippet, record these values.
Url: Endpoint for the Salesforce real-time messaging platform, SCRT2. Replaces the scrt2Url value in your client configuration settings.
OrganizationId: Salesforce org ID, beginning with 00D. Replaces the salesforceOrgId value in your client configuration settings.
DeveloperName: Embedded deployment service developer name. Replaces the esDeveloperName value in your client configuration settings.
You don’t need the channelAddressIdentifier value.
Log in to Business Manager, and record these values:
Organization ID: The ID of the B2C Commerce org. This ID begins with f_ecom. Go to Administration | Site Development | Salesforce Commerce API Settings.
Site ID: The storefront site ID. Go to Administration | Sites | Manage Sites.
Follow the installation method for your storefront type.