Considerations for the Campaign Creation Agent in Marketing Cloud Next

Prompt Defense (system policies and prompt injection detection)

Einstein Requests is one of the usage metrics for generative AI. The use of generative AI capabilities, in either a production or sandbox environment, can consume Einstein Requests and possibly Data 360 credits. To learn when Einstein Requests applies, see Metering for Agentforce and Generative AI Usage.

Direct API calls to the LLM gateway use Einstein Requests. To learn more, see the Rate Card for Einstein Requests.

Einstein Requests are available in:

• Enterprise, Performance, and Unlimited editions with an Einstein for Sales, Einstein for Platform, or Einstein for Service add-on. To purchase the Einstein for Sales, Einstein for Platform, or Einstein for Service add-on, contact your Salesforce account executive.
• All Einstein 1 Editions
• Salesforce Enterprise and Unlimited Editions with Marketing Cloud Next Growth or Advanced Edition

Usage is determined by the number of standard actions called by the agent in a text conversation. Currently, every standard action called by the agent is metered as one standard action, irrespective of the number of tokens processed.

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 a subscription has been purchased for each user that accesses these actions, 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 the requirement is enforced.

Usage is determined by the number of custom actions called by the agent in a text conversation. Currently, every custom action called by the agent is metered as one custom action, irrespective of the number of tokens processed.

Usage is determined by the number of standard actions executed by the agent in a voice conversation.

Note Use of some standard agent actions require that a subscription has been purchased for each user that accesses these actions, 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 the requirement is enforced.

Usage is determined by the number of custom actions called by the agent in a voice conversation.

Custom actions are actions that are created by you 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.

Usage is calculated based on two factors: the number of direct requests to the LLM via the LLM gateway, and whether the gateway uses a Bring Your Own Large Language Model (BYOLLM).

Each starter prompt includes the processing of up to 2,000 tokens. Prompt usage is counted in chunks of 2,000 tokens, rounded up. Prompts that exceed this limit will be metered as multiple prompts, with each additional 2,000-token chunk counting as a new prompt. For example, a prompt with a total of 6,500 input and output tokens will be metered as 4 prompts.

Tokens are units of data processed by the AI models.

Standard Prompts

Basic Prompts

Advanced Prompts

Usage is calculated based on two factors: the number of direct requests to the LLM via the LLM gateway, and whether the gateway uses a Salesforce managed large language model. The specific category depends on the model that is used. See Large Language Model Support to find out which usage types apply.

All Standard, Basic, and Advanced prompts process up to 2,000 tokens per prompt. Token usage is rounded up in 2,000-token increments. All Standard, Basic, and Advanced prompts that exceed this limit will be metered as multiple prompts, with each additional 2,000-token chunk counting as a new prompt. For example, a prompt with a total of 6,500 input and output tokens will be metered as 4 prompts.

Tokens are units of data processed by the AI models.

Translation converts text from one human language into text of another, a process executed by machine translation models. Translation usage is metered by the number of characters processed for the translation.

To understand how your consumption appears in the Digital Wallet, consider a scenario where you process 9,000 characters for translation. Because this usage is in units of one million characters, your actual consumption is 0.009 units (9,000 divided by 1,000,000). In the Digital wallet, this usage is rounded to two decimal places and the value is displayed as 0.01 units.

Usage is determined by the duration of the voice call between an end user and Agentforce Voice. Usage is rounded up to the next full minute, meaning any fraction of a minute is treated as a full minute.

For example,

• A call of 60 seconds is billed as 1 minute.
• A call of 61 seconds is billed as 2 minutes.

If your org has both Agentforce Voice Actions and Agentforce Voice Minutes enabled, Voice Minutes take precedence for billing. When Agentforce Voice Minutes are available in your org, only Agentforce Voice Minutes are metered, and Voice Actions usage types are not applied to the same activity.

Text-to-Speech converts written text into natural-sounding spoken audio, a process run by automatic Speech Synthesis models. Usage is metered by the number of text characters processed for the speech generation. In the Digital Wallet, this usage is aggregated and displayed in units of million characters.

To understand how your consumption appears in the Digital Wallet, consider a scenario where you process 9,000 characters for conversion from text to speech. Because this usage is in units of one million characters, your actual consumption is 0.009 units (9,000 divided by 1,000,000). In the Digital wallet, this usage is rounded to two decimal places and the value is displayed as 0.01 units.

Usage is calculated based on the number of interactions resolved by Help Agent through Enhanced Chat or a portal. A resolution is defined as up to 2 hours of interaction. If the user interacts with the agent for more than 2 hours, it is counted as a second resolution.