Legacy Agentforce Analytics versus Agent Analytics
Key Takeaway
Legacy Agentforce Analytics was scheduled for retirement on May 31, 2026. Salesforce recommends Agent Analytics, which replaces it.
Legacy Agentforce Analytics was the original way to measure agents. It was a fixed set of Data 360 reports and dashboards for each agent type. The reports showed who uses the agents, how successful they are, and how well they are adopted. Agent Analytics replaces it and shows its results as dashboards and session views in Agentforce Studio.
Legacy Agentforce Analytics
Each agent type had its own legacy reports. The two main sets were for Agentforce (Default) and for Agentforce Service Agent.
| Set | Focus | Example reports |
|---|---|---|
| Agentforce (Default) | Adoption and satisfaction | Adoption Rate, Weekly Active Users, Stickiness, Latency, Subagent Use, Satisfaction Rate |
| Agentforce Service Agent | Session outcomes | Total Session, Engaged Session, Deflection Session, Abandoned Session, Actions Usage, Subagents Usage |
Satisfaction Rate measured thumbs up out of all implicit feedback. The Agentforce Service Agent reports roll up into the Agentforce Service Agent Overview dashboard.
When feedback was enabled, Agentforce (Default) also had Utterance Analysis reports, which group user input into categories. These reports ran on weekends, so new data appeared only once a week.
Legacy reports had their own fixes for common problems.
If legacy reports couldn't be viewed...
The org needed a user assigned to the system admin role.
If a legacy report showed no data...
The agent needed to be active.
If a legacy dashboard said the admin disabled the reports or that relationships changed...
You cloned the dashboard and worked with the clone.