What an Executive Marketing Dashboard Should Show

What the dashboard is for

An executive dashboard has one job: help leadership make decisions about marketing without needing an analyst in the room. That means it is defined by the decisions, not by the data available.

The decisions are usually few. Is marketing producing enough demand, of the right kind, for the business to hit its targets? Is it doing so at an acceptable cost? Should budget move between channels, programs or seasons? Is anything broken that needs attention?

If a chart on the dashboard does not help answer one of those questions, it belongs somewhere else. That is not a judgment that the metric is useless. Sessions, engagement rate, scroll depth and click-through rate are essential for the people running campaigns and the website. They are simply the wrong altitude for a leadership meeting.

This article is about what goes on the dashboard. If you are weighing which tools can build or automate it, including the newer AI-assisted analytics products, that is a different question covered in AI-powered analytics for small business. A clever tool showing the wrong metrics is still showing the wrong metrics.

The top row: outcomes against target

The first thing a leader sees should be three to five numbers, each with its target and its trend. For most organizations they are some version of:

• Qualified demand. Qualified leads, booked consultations, bookings, applications or online sales, whichever is the real unit of business. Not raw form fills, and certainly not sessions.
• Cost per qualified result for paid channels, so spend is judged by what it produces rather than by clicks.
• Pipeline or revenue from marketing-sourced leads, if the CRM can support it, on a rolling basis that reflects your sales cycle.
• Total marketing spend against budget, so the cost side is always visible next to the outcomes.

Each number should be shown against a target and against the same period last year. Month-over-month comparisons mislead seasonal businesses, and for many organizations in Atlantic Canada (tourism, recreation, hospitality, agriculture, education) seasonality is the dominant pattern in every chart. A ski hill comparing October to September learns nothing; comparing this October to last October tells it something.

These numbers should come straight from your measurement plan. If you do not have one, the dashboard will turn into a negotiation about what to show, and the loudest metric wins.

The second layer: by channel and by program

Below the headline, one view that breaks the outcomes down by where they came from. Organic search, paid search, paid social, email, referral, direct, and any offline sources you can capture. For each: volume of qualified results, cost where there is one, and conversion from inquiry to qualified lead or sale.

This is the view budget decisions come from, so it has to reflect quality, not just volume. A channel that produces many cheap inquiries that rarely qualify should look worse than one that produces fewer, better ones. That requires the CRM to hold source data and sales outcomes, which is the subject of connecting marketing reporting to sales outcomes.

If the organization runs distinct programs (a recruitment campaign, a new location, a product launch, a destination campaign aimed at Ontario), each can have a single row showing its spend and its result against its own goal. Keep it to one row each. Programs that need more belong in their own report.

It is worth adding a simple check of whether channels are reinforcing each other or competing for credit. Our piece on whether your marketing channels work together describes the signals to watch.

What to leave off

A leadership dashboard improves more from what is removed than from what is added. Leave off:

• Sessions, users and page views as headline numbers. They describe activity. Traffic can rise while business falls, and the reverse.
• Impressions and reach without a downstream outcome next to them.
• Engagement rate, bounce rate and time on page. Useful diagnostics, but they invite debate without enabling a decision.
• Platform-reported conversions added together. Google, Meta and LinkedIn each claim credit by their own rules, and their totals overlap. Summed, they will exceed the real number of leads.
• Follower counts, unless audience size is a stated objective.
• Anything nobody has acted on in two quarters. If a chart has never changed a decision, retire it.

Search and AI visibility deserve a mention. Leaders increasingly ask whether the organization shows up in AI answers. That is a fair question, but most of the available measures are directional at best; treat them as a quarterly narrative rather than a precise number, as explained in measuring AI search visibility without false precision.

Put the caveats on the page

Every marketing number has limits, and an executive dashboard should state them where the number appears rather than in a footnote nobody reads. A short line of plain text is enough.

• Consent and blocking. Web analytics in Canada increasingly runs behind a consent banner, and some visitors use browsers or extensions that block tracking. Website-based numbers undercount real activity. Say so.
• Attribution method. Name it (first touch, last touch, data-driven) and note that channel credit would shift under a different method.
• Sales cycle lag. Revenue from marketing this quarter mostly reflects inquiries from earlier quarters.
• Untracked sources. Phone calls, word of mouth, events and walk-ins that tracking cannot see, captured only through self-reported source fields if at all.
• Known breaks. If tracking failed for two weeks after a site update, mark the period. Do not let a measurement gap be read as a performance drop.

A dashboard that admits its blind spots earns more trust from a board than one that appears to see everything.

Cadence, commentary and format

A dashboard without commentary is a set of charts that each reader interprets differently. Pair each monthly edition with a short written note from whoever owns marketing: what moved, why we think it moved, what we are doing about it, and what decision (if any) leadership needs to make.

A practical rhythm:

• Monthly: the dashboard plus a short commentary, read before the leadership meeting rather than presented in it.
• Quarterly: the same dashboard with a channel and budget discussion, where reallocation actually happens.
• Annually: a review of whether the KPIs and targets themselves are still right.

Format matters less than people think. Looker Studio connected to GA4, the ad platforms and the CRM is a common choice because it is free and refreshes automatically. A CRM’s own dashboard can work if most of the data is already there. A well-kept spreadsheet is better than a beautiful dashboard nobody trusts. Pick whatever your team will maintain.

Questions to ask whoever builds it

• Which decision does each number on the first screen support?
• Where does each number come from, and which source wins when two disagree?
• How will we know if the underlying tracking breaks?
• Who writes the monthly commentary, and who owns each KPI?
• Can we see this period against the same period last year without asking?

If the answers are vague, the dashboard will be too, however polished it looks.

A worked example

An illustrative case. Say a regional physiotherapy group with four clinics wants a monthly view for its owners. The dashboard might show, on one screen:

1. New patient bookings from marketing this month, against target and against the same month last year.
2. Cost per new patient booking from paid search and paid social, against target.
3. Bookings by source (organic search, Google Business Profiles, paid, referral from physicians, direct), by clinic.
4. Total marketing spend against budget, year to date.
5. Three lines of caveats: consent effects, phone bookings captured only via front-desk notes, and any tracking gaps that month.

Behind it, the marketing team keeps working reports with landing-page performance, campaign detail and search queries. The owners never need to open those unless the dashboard raises a question.

That separation, one decision view for leadership and working views for the team, is how we build reporting in our analytics and measurement work. The leadership view stays small on purpose.