Is Leadership Actually Looking at the Salesforce Dashboards We Built Them?

You built the CRO a pipeline dashboard back in Q1. It's got the stage-by-stage breakdown, the weighted forecast, the little callout for deals slipping past close date. It looked great in the demo you gave leadership when you shipped it.

Does she still open it?

You don't actually know. And that's the uncomfortable part, because these aren't just any dashboards — they're the ones actual business decisions get made from. Headcount, territory changes, which deals get exec attention this week. If the CRO isn't looking, that's not a minor reporting gap. That's leadership steering the org on stale instinct instead of the thing your team spent two sprints building.

Most ops teams have a version of this problem, and it's bigger than one dashboard. Based on Oniic's customer surveys, most orgs are sitting on thousands of dashboards and reports, and as much as 88% of them go unused. Somewhere in that pile is the pipeline dashboard, the MQL dashboard for the CMO, the renewals view you built CS leadership after that one QBR where someone asked "can we see this by segment." Built with good intentions. Possibly abandoned within a month.

Building a dashboard nobody uses is a waste of everyone's time — yours to build it, and leadership's to have asked for it in the first place. So how do you actually know?

Why LastRunDate doesn't tell you what you think it does

If you've tried to answer this question before, you've probably pulled up LastRunDate or LastReferencedDate on the dashboard record and called it a day. It feels like an answer. It isn't one.

LastRunDate tells you the last time the dashboard was refreshed. That's it. It doesn't tell you who refreshed it. Maybe the CRO opened her pipeline dashboard Monday morning like she does every week — or maybe a rep pulled it up to double-check their own number and the timestamp updated for reasons that have nothing to do with leadership actually using the thing.

It's also just a single point in time. Say you check LastRunDate on a Friday and it shows Friday. Was it opened once on Friday and never before that? Or opened twelve times between Monday and Thursday? You can't tell. The field collapses a week of behavior — or the absence of it — into one date, and then throws away everything else.

Admins have been suspicious of LastRunDate for a while now, and for good reason. It's the metric we've had to work with, not the metric that actually answers the question.

The question you're actually trying to answer

What you actually want to know isn't "when was this dashboard last refreshed." It's: did the CRO look at her pipeline dashboard this week? Has the CMO opened the MQL dashboard even once since launch? Is the renewals view CS leadership asked for actually part of anyone's Monday routine, or did it quietly stop mattering the week after you shipped it?

That's a who-and-how-often question, not a when-was-it-last-touched question. Salesforce, out of the box, doesn't really give you a way to get there.

This is where RecordWatch comes in. It's the first Salesforce-native solution on the AppExchange that tells you who's actually looking at a specific dashboard, when, and how often — down to the individual view. Instead of guessing from a single stale timestamp, you can see every time the CRO opened the pipeline dashboard this quarter, or confirm the CMO genuinely checks the MQL dashboard every Monday before the pipeline call. You can pull that by person, by role, by week — the same kind of grouping you'd apply to any other adoption report, just aimed at the dashboards themselves instead of records.

And the flip side matters just as much as the confirmation. If the CRO hasn't opened that pipeline dashboard in six weeks, now you know. You can retire it, rebuild it, or go ask her directly what she actually needs instead of maintaining a dashboard that's really just decoration.

Building success metrics in before you build the dashboard

Once you can actually see usage, the smartest move is to stop treating "we'll build it" and "we'll know if it works" as two separate conversations. Define the success metric before the project kicks off, not after someone asks why nobody's using the thing you shipped three months ago.

That might look like: leadership commits to reviewing the dashboard weekly, and you check back in a month to confirm that's actually happening. Or: this dashboard replaces a recurring email report, so usage should show up as regular opens on the days that report used to go out. Either way, you've got a target to check the data against instead of just hoping engagement holds.

This also changes the conversation with the people requesting dashboards in the first place. "Yes, we'll build this" stops being the end of the ask. It becomes "yes, we'll build this, and we'll know who's looking at it and how often" — which tends to make requesters think harder about whether they actually need a new dashboard or just want to feel like they asked for one.

What abandoned dashboards actually tell you

A dashboard leadership stopped opening isn't just dead weight to clean up. It's a diagnostic. Maybe the metrics on it stopped being the ones that matter — the org shifted focus from new logo to expansion revenue and nobody rebuilt the dashboard to match. Maybe it duplicates something leadership already gets in a Monday email and never needed a separate destination in Salesforce at all. Maybe it was genuinely useful for exactly one QBR and never again.

Knowing which dashboards leadership has quietly walked away from is what lets you ask the right question before you build the next one — not "what do you want to see" but "what will you actually come back and check." That's a harder question to answer honestly, but it's the one that keeps you from spending another sprint on something that ends up as one more unused report in that 88%.

The next time someone on the leadership team asks for a new dashboard, you're not just building it and hoping. You're building it, watching whether it gets used, and using what you learn to make sure the next one actually earns a place on someone's Monday. 

If you want to see what dashboard-level visibility actually looks like in your org, RecordWatch is built to answer exactly this.

FAQ

How do I know if leadership is actually using a Salesforce dashboard? Out of the box, Salesforce only gives you LastRunDate or LastReferencedDate on the dashboard record, which shows the last time it was refreshed by anyone — not who looked at it or how often. RecordWatch tracks individual views on dashboards, so you can see exactly who opened a given dashboard and when, rather than relying on a single stale timestamp.

Why is LastRunDate unreliable for measuring dashboard usage? LastRunDate only captures a single point in time and overwrites every other instance. A rep checking their own numbers can update the same timestamp as the CRO reviewing the whole pipeline. It also can't tell you whether a dashboard was viewed once or a dozen times since you last checked.

What percentage of Salesforce dashboards and reports actually go unused? Based on Oniic's customer surveys, most organizations have thousands of dashboards and reports, and up to 88% of them go unused.

What is RecordWatch? RecordWatch is a Salesforce-native application, available on the AppExchange, that reports on record and dashboard views — showing you who looked at what, when, and how often, down to the individual user.

When should we define success metrics for a new dashboard? Before you build it. Agreeing on what "in use" looks like — a weekly review cadence, replacing an existing report, a specific stakeholder checking in regularly — gives you something concrete to measure against once RecordWatch data starts coming in, instead of guessing after the fact whether the dashboard is working.