Salesforce Docs Portal

Set Up Agentforce Session Tracing

Turn on Agentforce Session Tracing to collect and store, in Data 360, detailed data about agent sessions. By default, Agentforce Session Tracing is off. For orgs with only one dataspace, it’s turned on by default when Agentforce is turned on.

Required Editions

Available in: Enterprise, Performance, and Unlimited Editions with an Einstein for Sales, Einstein for Platform, Einstein for Service, Einstein 1 Service, or Einstein GPT Service add-on. To purchase add-ons, contact your Salesforce account executive.
User Permissions Needed
To turn on data collection: View Setup
  AND
  Customize Application
Important
Important For the Platform Integration User, turn on the "View Setup and Configuration" system permission in the Data Cloud Salesforce Connector permission set.
Note
Note
  • Turning on Agentforce automatically turns on Agentforce Session Tracing, Agent Analytics, Agent Optimization, and Agent Health Monitoring. However, turning off Agentforce doesn't automatically turn these observability features off. You turn them off manually in Setup.
  • Agentforce Session Tracing requires Salesforce Standard Data Model version 1.130 or higher.
  • Salesforce stores Agentforce Session Tracing data in a data space in Data 360. See Data Model for Agentforce Session Tracing.
  1. Verify that you have the latest version of the Salesforce Standard Data Model (version 1.130 or higher) in your org (sandbox or production). From Setup, go to Apps -> Packaging -> Installed Packages -> Salesforce Standard Data Model. To get the required version, click here and follow the instructions.
  2. Turn on Einstein Generative AI (see Set Up Einstein Generative AI) and Agentforce (see Enable Agentforce).
  3. From Setup, in the Quick Find box, enter Einstein Generative AI, and then select Einstein Audit, Analytics, and Monitoring Setup.
  4. Scroll down to Agentforce Session Tracing.
  5. Turn Agentforce Session Tracing on or off.
    Toggle for Agentforce Session Tracing in Setup
    1. Turn on Agentforce Session Tracing to start collecting data in Data 360. The system provisions your data model, which can take a few minutes, and then starts collecting data. Data collection recurs at five-minute intervals.
    2. Turn off Agentforce Session Tracing to stop collecting data and automatically turn off any dependent features.
      Suspending data collection keeps your existing data so that you can resume later. Dashboards, queries, and reports show a gap during which data collection is off.
  6. If prompted (for example, your org has multiple data spaces), select a target data space to store the session trace data.
    • To add data to previously collected Session Tracing data, select the previously selected data space.
    • If you use a Data Cloud One companion connection to connect your orgs to Data 360, you see only the data spaces that are shared with your companion org.
    • To use a data space that is shared with your companion org, verify that the initialization status for the shared data space is active. See Monitor Data Cloud Companion Connections and Data Cloud One Companion Connection Statuses.
    • If you change the data space, then the system provisions the data model in the new data space. Any data collection stops in the previous data space, and that data remains until it’s manually deleted. Data isn't migrated to the new data space.
    • Be sure to communicate any changes to your data space selection internally and with your Salesforce Admin team.
  7. Protect access to collected Agentforce Session Tracing data that is sensitive. Hide sensitive data from unauthorized users. Stored data can contain personally identifying information (PII), protected health information (PHI), payment card information (PCI), and other sensitive information.
    • Use dynamic data masking to redact, nullify, or round sensitive data. For instructions, see Dynamic Data Masking Policies in Data 360.
    • Apply permissions at the data space level. That way, only authorized users can view or query this data. By default, users with the Data Cloud Architect (formerly the Data Cloud Admin) permission set have access to all the data. For instructions, see Implement Data Governance Permissions for Agentforce Session Tracing Objects.
    • The Salesforce System Admin profile includes the Manage All Data Space definition permission, which grants users access to all Data Spaces. If the default Allow All policy is active in the org, users with the System Admin profile can query all Data 360 DMOs. To preserve data security, we recommend deleting the default Allow All policy or editing its scope to apply to specific users. For instructions, see Data Governance in Data 360.