---
schema_version: "1"
id: 72ed055df1d04987cfc1399d27bac45f325936c765e32e7a1e0aa1ce206e8e23
title: Attribute Data Query Costs to Agentforce Sessions and API Requests
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_data_usage_correlation_identifier.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_data_usage_correlation_identifier.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4d34a51e5f72bd977833dbaf02fc4c4f5bd8e4dd4c506acd1d381d399ea7a351
description: 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.
products:
  - Data 360
release: "264"
---
# 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.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note

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:

1. 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.
2. Group or filter by CorrelationIdentifier\_\_c to isolate consumption from specific requests or sessions.
3. 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.

#### See Also

- [_Salesforce Help_: Example: TenantEnrichedUsageEvent Data Lake Objects](https://https://help.salesforce.com/s/articleView?id=xcloud.wallet_teue_reference.htm&type=5/s/articleView?id=xcloud.wallet_custom_report_dcr_dataspace_join.htm&language=en_US)