Video Marketing

Dashboard Tour Video Examples: 16 Data Views Buyers Can Read

Introduction

A dashboard on video has to be read, not just seen

Pause any dashboard tour at a random frame. Count the charts. Then try to read one number.

Most frames fail. Twelve widgets, tiny labels, and the cursor already moving on. Your buyer sees a busy screen and leaves with one word: complex.

Inside your product, a dashboard gets studied. On video, it gets a few seconds at playback speed, often on a phone. So the job changes. You're not showing data. You're teaching one reading.

The short answer: the dashboard tour videos that work answer one buyer question per scene. Source Merge answers “where does this data come from?” Metric Label answers “what does this number mean?” Alert Path answers “what happens when it moves?” Report Builder answers “will it show my team's numbers?” The 16 examples below are grouped by the question they answer.

Planning a dashboard tour?

Talk to the Advids team about style, budget and timeline before you record a single screen. Start with the one number your buyer should be able to read.

Let’s talk

16 examples

Dashboard Tour Video examples

Move 1 · Source Merge

If your buyer doesn't trust the numbers, show where they come from.

A bank statement you can't trace to a transaction gets disputed. Your buyer treats a chart with no visible source the same way. They nod, then they don't trust it.

I call it the Source Merge: show the scattered inputs first, then watch them land in one view. Five examples.

HR Acuity case management overview video

HR Acuity sells employee relations case management software. The overview turns scattered workplace issues into one tracked case system.

What works here:

  • Tangled lines stand for separate employee issues. They get pulled into the platform, so the mess becomes a record before any chart appears.
  • Then the data view: central case tracking, investigations and trend analysis, drawn as infographics.
  • A 3-step method and a path from issue intake to aftercare put a process behind the numbers.

The move: Show your buyer's messy inputs before the first chart. If a viewer can't say where the numbers came from, the scene is missing.

Bookingkit platform interface video

Bookingkit sells booking software for tours, activities and attractions. The video follows a booking from the “Book Now” button to a ticket redeemed on a phone.

What works here:

  • 2D characters and a “rocket science” joke lower the stakes before any interface shows up.
  • The sources get a number: over 50 distribution channels, with availability and pricing synced in real time.
  • Only then the dashboard: customer messages, cancellations and sales performance in one place.

The move: Count your data sources and put the number on screen. “50 channels in one dashboard” is a claim a buyer can check.

GoAigua water utility platform video

Idrica's GoAigua sells data software to water utilities. A city full of disconnected signals becomes one data model on a control room screen.

What works here:

  • The city is the map. Data signals blink from separate points, so the problem is visible before it's named.
  • Each source gets its real name, from AMI and AMR meters to SCADA. Engineers recognize their own stack.
  • The dashboard lands on results a utility manager reports: less non-revenue water, leaks found, lower OPEX.

The move: Name your buyer's existing data sources the way they say them, acronyms included. If an engineer would spot their own system, keep it.

SolarWinds Observability dashboard video

SolarWinds sells observability for hybrid IT. The video opens on critical data “scattered across multiple systems that don't talk to one another.”

What works here:

  • The risk gets a phrase IT teams know: issues “hide in plain sight.” That's the reason for one view.
  • Sources are listed, not implied: physical and virtual servers, AWS, Azure and Kubernetes.
  • Two named views do the work: traffic flow analysis and path monitoring, to catch issues before they hit operations.

The move: List the systems your dashboard pulls from in the voiceover. If your buyer runs one of them, they'll lean in.

Adobe Real-Time CDP overview video

Adobe Real-Time CDP brings together data “from any channel into unified profiles.” The video shows the profile first, then the audiences built from it.

What works here:

  • One profile is the merge point. Data is collected, organized and governed, then becomes segments.
  • Each data view has a job. Propensity scoring “shows you which customers will convert or churn.”
  • Speed gets a unit: segmentation “in an instant” and personalization “within milliseconds.”

The move: Show one unified record before any chart built on it. If the viewer never sees the record, the chart is just a picture.

Move 2 · Metric Label

If your buyer can't tell what a number means, name the metric before you chart it.

A source settles trust. Then the next question arrives: what am I looking at?

A thermometer reading means little until someone says what normal is. Your dashboard metric is the same. I call it the Metric Label: name the metric, say what it's compared to, then show the chart. Three examples.

DAT Rates data walkthrough video

DAT sells freight rate data to trucking carriers. The whole video explains how to read one figure on one screen.

What works here:

  • It opens on the viewer's own question: “Ever wonder why the rate you see on DAT doesn't always match the offer you're getting from a broker?”
  • The source is a number: over a trillion dollars in verified transactions from brokers, shippers and carriers.
  • Then a limit and a reading. “Rate View is a benchmark, not a fixed price.” The example reads a 7-day average of $4.60 per mile.

The move: Read one value off your dashboard out loud, with its time window. If the viewer couldn't repeat the number, it was never read.

GitKraken Insights dashboard video

GitKraken Insights sells engineering analytics. It opens on the question every team that bought AI coding tools gets asked: “can you quantify their real-world impact?”

What works here:

  • The metrics are named before they appear: code quality before and after AI adoption, and defect rates.
  • DORA metrics come “with context,” and developer experience is correlated with performance.
  • The close names the buyer's real job: “stop defending engineering productivity and start proving engineering value.”

The move: Write the question your buyer's boss asks, then name the 2 metrics that answer it. Show only those charts.

Flowcode Analytics interactive dashboard video

Flowcode turns QR code scans into first-party data. The video answers the question in its own title: what can you measure?

What works here:

  • The list is concrete: IP address, device type, location and opt-in details collected through Flowpages.
  • Interactive maps, line graphs and pie charts then cover traffic, engagement and device mix.
  • It ends outside the dashboard, with CRM integration and scheduled reports sent to email.

The move: List what your product measures before you show a single chart. If two charts answer the same question, cut one.

Move 3 · Alert Path

If your buyer asks what happens when a number moves, follow one alert to one action.

Knowing what a number means raises the next doubt. Who notices when it changes?

A smoke alarm earns its place by sending you to one room. Your dashboard earns its renewal the same way, when a chart sends someone to fix one thing. I call it the Alert Path: one change, one flag, one action. Four examples.

ST Engineering AGIL Care operations dashboard video

ST Engineering's AGIL Care runs a hospital operations center. Made for a pandemic, the video shows a dashboard that spots trouble and calls in a team.

What works here:

  • Live views come first: patient flow, ambulance arrivals and emergency department status, in clean 2D motion graphics.
  • Then the alert. Abnormal patient symptoms get flagged on screen and escalated.
  • The flag triggers the crisis management team, with admission trends and crisis inventory lists in one place.

The move: Script one alert from the flag to the person who acts on it. If your video shows the alert but not the action, add the action.

Veritone Forecaster platform tour video

Veritone Forecaster predicts energy supply, demand and prices with machine learning. In 40 seconds, it shows why a trader should trust the prediction.

What works here:

  • Graphs put predicted values next to actual results. Accuracy is shown, not claimed.
  • The dashboard names its metrics: peak price, demand, solar and wind generation, and forecasted revenue.
  • Potential outliers get flagged. That's the moment a trader acts.

The move: If you sell a prediction, show it next to what really happened. One overlay line beats a paragraph about accuracy.

Knode AI knowledge search video

Knode AI searches a company's knowledge, from Google Workspace and other sources. Published on Google Cloud's channel, the video ends on analytics that flag what to fix.

What works here:

  • Search reads meaning, not just keywords, and pulls up any document or slide deck.
  • Each answer links to its source document, and permissions carry over, so people only see what they're allowed to see.
  • Real-time analytics then point at knowledge gaps and content that needs an update. The dashboard becomes a to-do list.

The move: End your data view on the item someone should fix next. If the chart doesn't point at a task, it's a report, not a tool.

Process Street workflow management video

Process Street sells workflow software. In 31 seconds, it goes from an “Office Cleaning Checklist” to an “Information Security Audit” across departments.

What works here:

  • Tasks get assigned automatically, and alerts route them to people across a global map.
  • Each step ends in a decision, with “Approve” and “Reject” right on screen.
  • Confetti closes the run. The status view ends on done, not on pending.

The move: Show the alert, the person and the button they press. If your 30-second cut has no decision in it, it has no point.

Move 4 · Report Builder

If your buyer asks whether it fits their team, build one report on screen.

The last doubt is personal. Will this show my numbers, the way my team reads them?

A kitchen showroom sells when you can picture your own pans on the counter. Your buyer wants to see their report take shape, not your demo account. I call it the Report Builder: one report, built step by step, for one role. Four examples.

Ceipal BI dashboard tutorial video

Ceipal sells an applicant tracking system to staffing firms. Part 1 of a series, this video shows how its BI dashboards get built from ATS data, much like software tutorial videos do.

What works here:

  • Scattered data elements converge into trends in the opening motion graphics.
  • Then each step is shown: open BI from the ATS quick links, pick a module and topic, and choose a detailed, summarized or graphical report.
  • Graph types are named on screen: line, bar, pie, clustered columns and nested donut.

The move: Show the steps from login to finished chart, in order. If a viewer couldn't rebuild the report from your video, a step is missing.

Sapaad Vantage BI dashboard video

Sapaad Vantage is business intelligence for restaurants. It splits the view by time: past trends, the current pulse and future forecasts.

What works here:

  • Geographic sales maps and pie charts turn sales data into pictures an owner can read.
  • The view moves from a high-level summary down to single metrics, the way an operator would drill in.
  • Drag-and-drop reporting, fed by data synced from every sales channel, makes the report the buyer's own.

The move: Zoom from the summary to one metric in a single move. If the viewer loses track of which number you zoomed into, slow it down.

Smartsheet Portfolios dashboard video

Smartsheet Portfolios sets up projects from templates. Its framing line is simple: “Think of a portfolio as your central project hub.”

What works here:

  • Intake comes first. New form submissions flow straight into one project list.
  • One trigger builds the rest. The moment work is approved, it spins up the project plan, sheets, reports and dashboards.
  • Then the payoff a PMO lead reports up: “see project health, spot risk, and share reliable updates without the manual effort.”

The move: Show the report being created by the workflow, not by hand. If your dashboard needs setup, show the trigger that does it.

monday.com product video

monday.com's 15-second spot opens on a quote, then shows the same platform used for team planning and sales tracking.

What works here:

  • Two teams, two views, one product. A buyer from either team spots their own board.
  • Metrics are drawn in a simple visual style, so each one reads at a glance.
  • 15 seconds forces the choice: one quote, two uses, no settings.

The move: Cut a 15-second version with one view per team you sell to. If a team can't spot its own view, change the data on screen.

Pick your move

Which move does your dashboard tour need?

The short answer: ask one question. What can't your viewer answer about your data yet: the source, the meaning, the alert or the fit? The answer picks the move. One question per scene. If two are loud, make two short videos.

If your buyer asksUseDo thisExample to copy
“Where does this data come from?”Source MergeShow the scattered inputs, then the one viewSolarWinds
“What does this number mean?”Metric LabelName the metric and its comparison, then chart itDAT
“What happens when it moves?”Alert PathOne change, one flag, one actionST Engineering
“Will it show my team's numbers?”Report BuilderBuild one report, step by step, for one roleCeipal

Now go back to that paused frame. Twelve widgets, and not one number a stranger could read. Every move above fixes the same thing: it tells the viewer which number to look at, and why.

The move: pause your current dashboard tour at 5 random frames. Ask a colleague to read one number and say what it means. Cut widgets until they can.

A full dashboard proves you built a lot. One readable number proves they'll use it.

FAQ

Dashboard Tour Video Examples FAQ

What is a dashboard tour video?
A dashboard tour video is a short video that walks a buyer through the data views in a software product: the charts, reports and alerts they'll actually use. The good ones teach the viewer to read one number, not admire a full screen. Veritone Forecaster does it in 40 seconds.
How long should a dashboard tour video be?
Most run 1 to 2 minutes. 12 of the 16 examples on this page fall in that range. The shortest is monday.com at 0:15. The longest is GoAigua at 2:06, because it explains a whole water network. Give each chart enough time to be read, and cut any chart you can't.
Should a dashboard tour use real screens or an animated UI?
Use a real screen recording when the buyer needs proof the product exists. Use a simplified, animated UI when the real screen is too dense to read at video speed. Most SaaS UI videos clean the interface up: fewer widgets, bigger numbers, nothing busy in the corners.
How do you animate charts in a dashboard video?
Animate to show change, not to decorate. A line that draws itself shows a trend. A bar that grows shows a comparison. Use the same motion for the same kind of data, so viewers learn it once. Observable's guide on animation in data visualization covers when motion helps a chart.
What's the difference between a dashboard tour and a product tour?
A product tour video walks the viewer through the whole interface to show it's easy to use. A dashboard tour stays on the data views and teaches the viewer to read them. Analytics and monitoring products often need both, starting with the tour.
What's the difference between a dashboard tour and a SaaS demo?
SaaS demo videos follow the product through a task, from the first click to the result. A dashboard tour starts where the task ends: the numbers it produced. If your buyer pays for insight more than for workflow, lead with the dashboard tour.
How do you show an AI insight on a dashboard?
Show the insight next to the data it came from. Knode links each AI answer to its source document. Forecaster puts predicted values next to actual results. Without the source or the comparison, an AI insight on screen looks like a guess.
Should a dashboard tour video use a voiceover?
Yes, in most cases. The voiceover tells the viewer where to look, so the screen can stay clean. Say the number you want read, the way DAT reads its 7-day average aloud. Add captions too, for viewers watching with the sound off.
How do you show real-time data in a video?
Show the update, not the word “real-time.” A number ticking up, a new row landing, a dot appearing on a map. Bookingkit shows availability and pricing synced across channels. SolarWinds pairs “real time insights” with two named views: traffic flow analysis and path monitoring.
How do you make charts readable for color-blind viewers?
Don't let color carry the meaning alone. Add labels, patterns or direct values next to lines and bars. Red versus green is the classic trap on status dashboards. Highcharts' guidelines for accessible data visualization make a good checklist before you lock the design.
How should a dashboard tour video end?
On the screen or decision your buyer cares about, then one ask. Smartsheet ends on project health and risk. GitKraken ends on “start proving engineering value.” Then ask for one next step: a trial, a demo or a sample report.
How do you measure whether a dashboard tour video works?
Pick one goal first: trial sign-ups, demo requests or feature adoption. Track clicks on the call to action against that goal. Then check where viewers drop off. A drop on a chart scene usually means the chart was too hard to read at that speed.

Patterns from the analysis

Dashboard Tour Video Best Practices

Five of the videos above were broken down from their full transcripts: GitKraken, SolarWinds, Smartsheet, DAT and Adobe. Five patterns showed up. Five is a small sample, so read each count as what these five did, not as market data.

Question Open

Should a dashboard tour open on a question?

Observation
GitKraken opens on “can you quantify their real-world impact?” DAT opens on why its rate doesn't match a broker's offer. SolarWinds opens on data scattered across systems. Smartsheet opens on a promise: “Launch projects faster and keep work aligned.” Adobe opens on the product name.
Data
3 of 5 opened on a question or a problem. 2 of 5 opened on the product or a promise.
The move
Open on the question your dashboard answers. The chart then arrives as the answer, not as decoration.
Source Named

Should a dashboard tour say where the data comes from?

Observation
DAT cites over a trillion dollars in verified transactions from brokers, shippers and carriers. SolarWinds lists servers, AWS, Azure and Kubernetes. Smartsheet shows form submissions flowing into the project list. Adobe says “any channel.” GitKraken says “across your tool chain.”
Data
5 of 5 said where the data comes from. 3 of 5 named a specific source.
The move
Name the source in plain words. “Verified transactions” earns trust. “Any channel” asks for it.
Value Read Aloud

Should the voiceover read a number off the dashboard?

Observation
Only DAT reads a value: a 7-day average of $4.60 per mile. GitKraken names code quality and defect rates without values. Adobe names propensity scoring. Smartsheet names project health and risk. SolarWinds names its views, not its metrics.
Data
4 of 5 named a metric. 1 of 5 read a value aloud.
The move
Read one value off your dashboard in the voiceover, with its unit and its time window.
Speed Unit

How should a dashboard tour talk about speed?

Observation
GitKraken works “in minutes, not months.” Adobe promises segmentation “in an instant” and personalization “within milliseconds.” Smartsheet spins up dashboards “the moment work is approved.” SolarWinds offers “real time insights.” DAT makes no speed claim.
Data
4 of 5 made a speed claim. 2 of 5 gave it a unit of time.
The move
Give speed a unit. “Real time” is a label. “Within milliseconds” is a spec.
Say the Limit

Should a dashboard tour say what a number can't tell you?

Observation
Only DAT does. “Rate View is a benchmark, not a fixed price.” It then names what pushes a load above or below the average: the commodity, shipment urgency and other outside factors. The other four show no limits.
Data
1 of 5 said what its main number doesn't mean.
The move
Say what your main metric can't tell the buyer. It heads off a misread and makes every other claim easier to believe.

How to plan

Where to use your dashboard tour video

Put the dashboard tour where someone has to judge your data. That one rule decides most placements.

  • Product pages for analytics and monitoring tools. The dashboard is the product, so the tour is the main demo.
  • Feature pages. One data view per page, with one number read aloud.
  • Sales follow-ups. The report your champion will forward to their boss, shown on video.
  • Onboarding emails and help docs. How to build the first report, the way Ceipal does in Part 1 of its series.

How to make a dashboard readable on video

A screen built for daily use is too dense for video. Five fixes, in order.

  • Zoom. Push in until the chart you want read fills most of the frame. Then pull back once to show where it sits.
  • Cut ink. Remove gridlines, borders and extra labels. Holistics' guide to the data-ink ratio explains why every mark should carry data.
  • Title the finding. A chart title that states what changed reads faster than one that names the axis. AnyChart's tips on writing chart captions show how.
  • Highlight one thing. Dim everything except the number the voiceover is reading.
  • Hold. Leave each chart up long enough to read its title and one value.

The same zoom and highlight moves run through most user interface demo videos. Before you record, check the screen itself against Geckoboard's dashboard design guide.

What data to put on screen before you record

Empty dashboards look broken. Fake-looking data looks fake. The numbers on screen are part of the script.

  • Uneven values. Perfectly round numbers read as placeholders. Use the kind of values a real account would show.
  • One story in the data. Give the chart something to show: a spike, a drop or a forecast. Forecaster's predicted-versus-actual lines are the model.
  • Your buyer's labels. Name metrics the way your buyer says them, like ST Engineering's ambulance arrivals and emergency department status.
  • No customer data. Use a sandbox account, or rebuild the screen in animation.
  • Clean corners. Notifications, test accounts and extra browser tabs pull the eye. Record any product screencast in a clean browser profile.

Dashboard tour video production process

Every dashboard tour runs through the same three stages. Knowing them keeps a project from drifting.

  • Pre-production. Pick the buyer question, the one number and the story in the data. Then script and storyboard one frame per chart.
  • Production. Record clean screens with demo data, or rebuild the UI in motion graphics. Use technical animation for systems a screen can't show, like GoAigua's city network.
  • Post-production. Add zooms, highlights, chart captions and the voiceover. Get feedback in one round, then cut a version for each platform.

About the author

About Jai Ghosh

Jai Ghosh
Video Producer at Advids · LinkedIn

Jai Ghosh is a Video Producer at Advids, where he has planned and produced videos for B2B software and technology companies for 7 years. He works on product demos, explainer videos and brand videos, from the first script to the final cut, for clients from startups to enterprises.

Before Advids, Jai spent over 11 years in freelance media consulting, after starting out in digital journalism. He writes the Advids blog's breakdowns of product and demo videos, sorting real examples by the question each one answers for a buyer.

  • Focus: SaaS product demos, explainer videos and brand videos
  • Experience: 7 years at Advids, over 11 years in media consulting
  • Background: digital journalism

Connect with Jai Ghosh on LinkedIn