You are here:
Attribute Data Query Costs to Agentforce Sessions and API Requests
The CorrelationIdentifier__c field in Digital Wallet billing events connects Data 360 query credit consumption to source processes such as the Agentforce session, AI agent, or API call that triggered the query.
When a request triggers a Data 360 query such as an Agentforce agent action, a prompt, a report, or a direct API call, an identifier propagates through the query pipeline. The identifier is recorded as CorrelationIdentifier__c in the TenantEnrichedUsageEvent data lake object (DLO). You can use this field to attribute data query credit consumption to specific agents, sessions, and users.
CorrelationIdentifier__c can be used to attribute costs for the Data Queries usage type.
Report on Query Costs by Request Origin
To attribute query credit consumption to an Agentforce session or other originating request:
- Query the TenantEnrichedUsageEvent DLO and filter on usage type. Filter for DataCloud_DataQueries if you're using Data Services credits, or for Data360_Queries if your org uses Flex Credits for Data 360.
- Group or filter by CorrelationIdentifier__c to isolate consumption from specific requests or sessions.
- Join CorrelationIdentifier__c to the corresponding trace ID in your Agentforce session data.
You don't consume credits when querying or reporting on the TenantEnrichedUsageEvent DLO directly. Some other reporting methods, such as creating a Tableau visualization, can consume credits.
