Definition
Source Report is an analytics feature in Salesforce that helps users measure, visualize, and understand their business data. It provides tools for building reports, dashboards, or data explorations that turn raw data into actionable insights.
Real-World Example
a data analyst at MarketPulse uses Source Report to uncover trends and patterns hidden in their CRM data. By configuring Source Report, they create visualizations that tell a clear story about business performance. The executive team uses these insights to adjust strategy mid-quarter and the company exceeds its revenue target by 12%.
Why Source Report Matters
A Source Report in Salesforce is the underlying report that feeds data to a dashboard component. Every chart, gauge, table, or metric on a Salesforce dashboard pulls its data from a source report, which defines the filters, groupings, and measures that the component displays. This architecture means that dashboard accuracy is entirely dependent on the quality and configuration of its source reports. If a source report has incorrect filters or missing record types, the dashboard component will display misleading data without any visible warning.
As organizations build sophisticated executive dashboards with dozens of components, managing source reports becomes a governance challenge. Each component requires its own source report, meaning a 20-component dashboard depends on 20 individual reports that must all be maintained. Without clear naming conventions and folder organization, teams end up with orphaned or duplicated source reports that nobody can trace back to their dashboard. Worst case, someone modifies a source report without realizing it feeds a VP's dashboard, causing incorrect data to be presented in a board meeting. Establishing a dedicated report folder for each dashboard and using consistent naming like 'DB - [Dashboard Name] - [Component Name]' prevents these issues.
How Organizations Use Source Report
- MarketPulse Analytics — MarketPulse Analytics built an executive dashboard with 15 components, each tied to a dedicated source report stored in a locked folder. The marketing director can trust that the pipeline-by-source chart always reflects the correct attribution model because only report admins can modify the source reports feeding the dashboard.
- Granite Construction — Granite Construction's ops team discovered their safety incident dashboard was underreporting by 20% because the source report filtered out a recently added Record Type. By auditing the source report's filters, they corrected the dashboard and now perform monthly source report reviews to prevent recurrence.
- Velocity SaaS — Velocity SaaS uses separate source reports for their ARR dashboard — one for new business, one for expansions, and one for churn — each with precisely defined date filters and opportunity stages. This separation ensures each metric is independently verifiable and any discrepancy can be traced to a specific source report.