How to Create a Salesforce Dashboard That Matters
Most Salesforce dashboards are wallpaper. They look impressive, refresh on schedule, and nobody opens them.
The dashboards people actually use have one thing in common: they answer one specific question for one specific person, daily. This guide walks how to build dashboards that get used.
Estimated read time: 9 minutes
The 30-second rule
Before you build anything: define who opens this dashboard, when, and what decision it informs.
If you can't answer all three in one sentence — "The VP of Sales opens this every Monday morning to decide where to spend pipeline review time" — don't build it. Or build a different one.
Dashboard anatomy
A Salesforce dashboard is up to 20 components arranged on a grid. Each component is built from one source report.
Component types:
- Chart — bar, line, donut, funnel, scatter
- Gauge — single number with thresholds
- Metric — single number, no chart
- Table — top N rows from a report
- Lightning Component — custom (advanced)
Best practice: 6-8 components per dashboard. More than that, nobody scans it.
Step-by-step: build your first dashboard
Step 1: Create reports first
Dashboard components require source reports. Build the reports first, validate the numbers, then build the dashboard.
For a Sales Pipeline dashboard, start with these reports:
- Pipeline by Stage (summary, grouped by Stage, summing Amount)
- Pipeline by Owner (summary, grouped by Owner)
- Aging Opportunities (tabular, filtered to days in stage > 30)
- Top 10 Open Deals (tabular, sorted by Amount descending)
- Win Rate by Quarter (matrix, Quarter × Win/Loss)
- Closed This Month (summary)
Step 2: Create the dashboard
App Launcher → Dashboards → New Dashboard.
Name it descriptively: "VP Sales Weekly Pipeline Review."
Step 3: Add components
Click + Component. Pick a source report. Choose component type. Configure:
- Title (be specific — "Open Pipeline by Stage" not "Pipeline")
- Display settings per type
- Conditional formatting if numeric
Drag to reorder. Resize as needed.
Step 4: Configure the dashboard
Top of dashboard → Settings:
- Run As: Critical. The dashboard data reflects what this user can see. For exec dashboards, run as "Logged-in User" only if everyone has the same access; otherwise pick a fixed user with broad visibility.
- Refresh Settings: Manual or Scheduled. Schedule for early morning before people open it.
Step 5: Subscribe stakeholders
Click Subscribe → set frequency, time, recipients.
Subscriptions email a snapshot — useful when the audience won't actively log in.
The components that always belong
Across hundreds of dashboards, four component types earn their slot:
- One headline metric — the number this dashboard exists to track. Big and at the top.
- Trend over time — line chart showing the headline metric monthly/quarterly. Context.
- Breakdown by dimension — bar or donut showing the metric by Owner, Region, Product, etc.
- Action list — table of records that need attention (stale deals, unassigned leads, overdue activities).
Most dashboards bloat by adding charts that don't drive action.
The components that almost never belong
- Pie charts of more than 5 slices — unreadable
- Component titles like "Sales" — too vague
- Tables of all open opportunities — that's a list view, not a dashboard
- Metrics without comparison — "$2.4M" means nothing without context (last quarter? target?)
Filters: the underused feature
Dashboard filters let one dashboard serve multiple users. Add up to 5 filters per dashboard (Region, Quarter, Product Line). Each user sets their own filter values.
Use case: a "Regional Sales Dashboard" filtered by Region, used by all 6 Regional VPs from one dashboard instead of six.
Common mistakes
- Running As Logged-in User when access varies. Numbers change per user. Confusing.
- Charts pulled from reports with the wrong filters. Dashboard chart looks weird → check the source report's filters.
- Refreshing manually. Set a schedule. People assume the data is current.
- Ignoring mobile. Most exec dashboards get viewed on phones. Test the layout.
- Too many dashboards. Build one excellent dashboard per persona, not 12 mediocre ones.
Want a dashboard suite built for you?
A working dashboard suite — properly scoped per persona, validated against source data, scheduled to subscribers — is a 3-4 week project most teams never finish.
RevKit's Dashboard Build delivers it in 48 hours for $899:
- Persona interview to scope the dashboards that matter
- 3 production-ready dashboards with 6-8 components each
- Source reports validated and shared correctly
- Scheduled subscriptions to right audience
- Mobile-tested layouts