You are here:
Usage Types Consumed by the B2C Shopper Agent
The Shopper Agent uses generative AI and Data Cloud to ingest, store, and process data. You’re billed in these categories when you use the Shopper Agent. Before deployment, work with your Salesforce account team to confirm license availability and plan credit usage.
| Card | Type | Description | Notes |
|---|---|---|---|
| Conversations | Agentforce: ASA Messaging | For this subtype of the Agentforce usage type, Salesforce calculates usage based on conversation windows. A conversation window starts:
The end of the conversation window differs for each Digital Engagement channel on which ASA is enabled. For the Enhanced Chat channels:
For these channels, the conversation window ends 24 hours after the start of the conversation:
|
The Shopper Agent (ASA) only supports inbound conversations, which are conversations that a user initiates. See Generative AI Billable Usage Types. |
| Data Services Credits | Batch Data Pipeline | Salesforce calculates usage based on the amount of batch data processed by Data 360 data streams across all connectors. | |
| Data Services Credits | Data Queries | Salesforce calculates usage based on the number of records processed. The count of records processed depends on the structure of a query and other related factors such as the total number of records in the objects being queried. |
|
| Data Services Credits | Unstructured Data Processed | Salesforce calculates usage based on the amount of unstructured data processed. For example, if the search index processes 100 PDF documents that are 1 MB each, Salesforce calculates usage as 100 MB. If the search index processes five audio/video files that are on average 100 MB each, Salesforce calculates usage as 500 MB. In Data 360, unstructured data can be chunked and vectorized using an embedding model. Salesforce computes usage only once across both these activities. For example, if one 100 MB PDF document is chunked and vectorized, Salesforce computes usage as 100 MB, not as 200 MB. |
|
| Data Storage | Storage Beyond Allocation | Salesforce calculates usage based on the amount of storage used above the amount allocated. | Storage refers to the amount of data stored in Data 360. Storage used outside of Data 360, such as data stored on the Salesforce Lightning Platform, isn't counted toward this limit. Data you ingest into Data 360 B2C Shopper Agent conversations is counted toward your storage allocation. If you use more data than allocated, usage is charged. |
| Einstein Requests | Einstein Requests | Einstein Requests is a usage metric for generative AI. The use of generative AI capabilities, in either a production or sandbox environment, consumes Einstein Requests and possibly Data 360 credits. To learn more, see Data Cloud Billable Usage Types. API calls to the LLM gateway use Einstein Requests. For each API call to the LLM gateway, the number of Einstein Requests used depends on the API call size factor and the LLM usage type multiplier. To learn more, see the Rate Card for Einstein Requests. Einstein Requests are available in:
|
See Generative AI Billable Usage Types. |
| Flex Credits | Standard Action | The number of standard agent actions determines usage. Each standard agent action includes the processing of up to 10,000 tokens. Tokens are units of data processed by AI models. Actions exceeding this limit count as a separate standard action each time the action exceeds the 10,000 token limit. For example, processing 20,001 tokens is 3 standard actions. Actions involving lengthy prompts sent to the LLM can count as multiple actions where the action exceeds the 10,000 tokens per action limit. Standard agent actions are actions that are available out-of-the-box. To check the list of standard actions, see Standard Action Reference.  Note Use of
some standard agent actions require that each user who accesses these actions has purchased
a subscription, such as a subscription to Agentforce for Sales Add-on or Agentforce for
Service Add-on. To determine which subscription is required for such standard actions, see
Standard Action Reference at Standard Action Reference. While this
requirement is not technically enforced yet, users who don’t have the required add-on
license will lose access to such actions for which they don’t have a license when
Salesforce enforces the requirement. |
|
| Flex Credits | Custom Action | The number of custom actions determines usage. Each custom action includes the processing of up to 10,000 tokens. Tokens are units of data processed by AI models. Actions exceeding this limit count as a new custom action each time the action exceeds the 10,000 token limit. For example, processing 20,001 tokens is 3 custom actions. Actions involving lengthy prompts sent to the LLM can count as multiple actions where the action exceeds the 10,000 token per-action limit. Custom actions are actions that you create or which result from your modification of a standard action. To learn more about what customer created actions are, see Create a Custom Agent Action. To learn more about how standard actions become custom actions, see Editing Standard Agent Action Reference Actions. |
