Build a Data 360 report that uses the User ID field to see which individual users are
driving Agentforce credit consumption in your org. Because you build this report directly on the
TenantEnrichedUsageEvent data lake object (DLO), you don't incur costs.
Required Editions
User Permissions Needed
To create a Data 360 report
“Create and Customize Reports”
See Salesforce Help: Digital Wallet Permissions to make sure that you
have all the required permissions to access Digital Wallet, access Data 360 objects, and create
this report.
Before you begin, be sure
that the TenantEnrichedUsageEvent DLO is added to a data space.
The User ID field in the TenantEnrichedUsageEvent DLO contains the 18-character, 005-prefix
Salesforce user ID of the person who performed the action. With this field populated, you can
group and filter your reports directly by user, so you can see exactly which individuals are
driving credit consumption. This field is restricted to Employee Users using an Agentforce
Employee Agent, meaning it only populates for authenticated internal employees interacting with
internal-facing agents. It doesn’t capture user identifiers for external customers, guest users,
automation/agentic users, or participants using public-facing Service Agents.
User ID is populated for Employee Agent events only, specifically:
Usage Type
Description
Agentforce_StandardAction
Standard actions executed by Employee agents
Agentforce_CustomAction
Custom actions executed by Employee agents
From the App Launcher, select Data Cloud.
Go to Reports, then click New Report.
In the category panel on the left, select Data Cloud.
Select the TenantEnrichedUsageEvent DLO, then click Start
Report.
For Group Rows, select User ID.
For Columns, select the following:
Usage Type Developer Name — which credit type was consumed.
Resource ID or API Name — which resource was triggered by the user.
Units Consumed — the number of credits.
Click Run, then save the report.
The User ID field contains the 18-character, 005-prefix Salesforce user record ID. To see more
details about the user in your report, such as first name, last name, username, department, cost
center, or country, bring the standard User object into Data Cloud using the CRM connector, then
join it to the Digital Wallet TenantEnrichedUsageEvent
DLO
on the User ID field. This method is likely to incur costs.
Then you can build reports such as these:
Consumption by user name
Consumption by team or department
Consumption by region or country
Any other grouping driven by fields on the User object
Konnten Sie Ihr Problem mithilfe dieses Artikels lösen?
Geben Sie uns Feedback, damit wir uns verbessern können.
Laden
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.