How do I Know if marketing is using the Salesforce Dashboard I built them?

You spent two sprints integrating campaign data, mapping it into the CRM, and building Marketing a dashboard they asked for by name. Three months later, nobody on that team has mentioned it once. That silence poses the question: is it working, or did it quietly join the pile of things you built that nobody’s using?

The cost isn't just the build time, though that's real. If Marketing isn't using what you gave them, they're probably still pulling exports into their own spreadsheets. A shadow version of the same numbers, drifting further from what the rest of the org sees every quarter. That's not a minor inconvenience, it's two versions of "how's the funnel doing" existing at once, and only one of them lives where Sales and RevOps can see it.

Login activity tells you they showed up, not what they saw

Login history is the easiest signal to pull, and it tells you almost nothing about the dashboard specifically. Someone logging in to check their calendar counts the same as someone logging in to dig through campaign performance. You can see that Marketing is present in the org. You can't see whether they ever navigated anywhere near the thing you built for them.

Dashboard refresh and run history tells you it loaded, not who was looking

This one feels closer, since at least it's tied to the actual dashboard. A refresh timestamp confirms the component rendered for somebody. What it can't tell you is who: a refresh triggered by an admin checking the dashboard can make an entire team's dashboard look "active" when only one person has ever seen it.

Asking Marketing directly tells you what they think you want to hear

You can always just ask in the next sync. Most of the time you'll get a version of "yeah, it's great, we check it." That's not dishonesty, it's the natural response when someone doesn't want to be the reason a project gets flagged as a failure, or when they genuinely don't remember the last time they opened it versus the last time someone on their team mentioned a number from it secondhand. Self-reported usage is a real signal, but it's the least reliable one you have, and it's the one most teams lean on hardest because it's the easiest to collect.

Stack all three together and you still land in the same place: you know Marketing exists in Salesforce, you know the dashboard rendered for someone at some point, and you know what they'll say if you ask them face to face. None of that tells you whether the VP of Demand Gen has opened it since the kickoff call, or whether the person who actually needs it — the campaign manager three levels down — has ever seen it at all.

Seeing who actually looked, and what they did next

This is the gap RecordWatch closes. Instead of inferring usage from logins or refresh timestamps, you can see the dashboard view itself — who opened it, when, and how often, down to the individual user rather than a team-level guess. You stop asking "did Marketing use the dashboard?" and start being able to answer it with a name and a date.

The more useful part is what happens after the view. Because the tracking lives natively in Salesforce, you can see the click path a dashboard view leads to — whether someone who opened it then drilled into a specific Campaign record, or clicked through to Opportunities tied to a channel that's underperforming. That's the difference between a dashboard people glance at and one that's actually driving them deeper into the platform instead of back out to their own spreadsheet. We wrote more about what this looks like across a broader set of out-of-the-box adoption signals if you want the fuller picture before layering this on.

What this actually changes

Once you can see real usage at the individual level, the fix stops being a guess. If the campaign manager who requested the dashboard has never opened it, that's a conversation about the report itself — wrong fields, wrong cadence, buried where nobody would find it. If it's genuinely being used but only by one person on a five-person team, that's an adoption problem you can now name and go solve, instead of one you find out about accidentally in a meeting six months later.

Either way, you're no longer maintaining a dashboard on faith. You know if it's working, you know who it's working for, and you know exactly what to fix if it isn't — before Marketing quietly rebuilds the same numbers somewhere you can't see them.

FAQ

How can I tell if someone actually viewed a Salesforce dashboard, not just that it loaded? Standard Salesforce reporting shows refresh and run history at the dashboard level, which doesn't distinguish between individual viewers. RecordWatch tracks views at the user level, so you can see specifically who opened it and when.

Is login activity a reliable way to measure dashboard adoption? Not on its own. Login history confirms someone accessed Salesforce generally, not that they viewed a specific dashboard or report. It's a useful baseline signal, but not proof of engagement with any one asset.

What's the risk of not knowing whether Marketing is using their dashboard? The main risks are wasted build and maintenance time, and Marketing falling back on their own exports or spreadsheets to get the numbers they need — creating a second, unofficial version of the data that drifts from what's in Salesforce.

Can I see what someone does after viewing a dashboard, not just that they viewed it? Yes — RecordWatch can surface the click path from a dashboard view into related records, so you can see whether a view leads to someone drilling into Campaigns, Opportunities, or other objects rather than leaving the platform.

Does this only apply to Marketing dashboards? No. The same gap — knowing a report exists versus knowing whether anyone's actually using it — shows up for any stakeholder group with its own systems and priorities outside core Sales workflows, not just Marketing.