Marketing Dashboards Answer Different Decisions
A marketing manager opens the weekly report and sees three plausible stories. Website sessions rose, organic search clicks fell, and the sales team accepted fewer leads. A single dashboard packed with all three numbers will show the disagreement but will not tell the manager which action to take. The useful question is narrower: did the change happen in traffic acquisition, on a particular page or campaign, or after someone became a lead?
Good marketing dashboard examples answer different versions of that question. An acquisition view helps decide where visitors are coming from. A search view shows which queries and pages earn visibility and clicks. An engagement view shows what visitors do with emails, forms, and landing pages. A pipeline view follows the handoff into sales. An executive view gives leaders enough context to decide where a closer look is warranted. Salesforce describes a dashboard as a curated set of charts, metrics, and tables, with filters and links into more detailed views; the value lies in that selection, not in putting every available metric on one screen. Salesforce’s B2B Marketing Analytics guide shows why these views serve different readers.
Pick the dashboard by the decision it must support
Before copying a layout, name the meeting in which it will be used. A channel manager deciding whether to change a campaign needs source and session detail. A content lead deciding which page to improve needs query, page, and search result data. A demand generation director deciding where to put the next campaign budget needs lead and opportunity definitions that marketing and sales both recognize. If those people share one crowded screen, each will spend the meeting explaining a different denominator.
The simplest useful design has a summary, a comparison, and a route to the underlying rows. Show the chosen period and the previous comparable period. State whether the unit is users, sessions, people, interactions, opportunities, or dollars. Then provide a channel, page, campaign, or opportunity breakdown that can explain a change. The details matter because a large total can conceal one weak landing page, and a striking percentage can come from a very small base. A dashboard should make the next question easy to ask, even when the answer requires investigation outside the dashboard.
These are six practical examples. Each can be built as a separate view or as a tab in a larger reporting system. The suggested additions are design choices, not claims that every cited product supplies them by default.
An acquisition dashboard shows where visits begin
Use an acquisition dashboard when the immediate decision concerns channel mix: whether to inspect paid traffic, change distribution of a newsletter, or look more closely at organic visits. Google Analytics offers an acquisition overview that summarizes how new and returning users found a website or app. Its overview reports use summary cards, and their date range and comparison settings can be changed. That makes the overview a sensible entry point before opening a more detailed channel report. Google’s overview report guide describes those controls.
A workable version places a channel trend beside a table of source or campaign, sessions, engaged sessions, and the outcome the team actually cares about. If the organization has defined a lead submission or purchase as an outcome, put that outcome next to traffic rather than treating traffic growth as success by itself. Keep the same date window and outcome definition across the comparison. A jump in sessions deserves attention, but it does not establish that the extra visits came from the intended audience or led to more business.
Choose the traffic scope before showing a channel total. Google distinguishes its User acquisition report, which focuses on how new users first arrived, from its Traffic acquisition report, which focuses on where sessions came from. The former uses dimensions such as “First user source”; the latter uses “Session source.” Google warns that the same named metric can differ across those reports because the dimensions have different scopes. Google’s comparison of the two acquisition reports is the relevant reference. A dashboard about finding new people should use the first view. A dashboard about which channels brought visits this week should use the second. Label the choice in the dashboard, because otherwise two legitimate channel figures can look like a broken report.
The cost of this focused view is that it stops at the site or app boundary. It is useful for changing the next channel question, but it cannot alone tell a B2B team whether those visits later became sales opportunities. Put a link to the pipeline view nearby rather than adding opportunity dollars to an acquisition chart with a different population and timing.
An organic search dashboard connects queries to pages
An SEO dashboard is most useful when the content team needs to choose which page to revise. Its first row can show Google Search clicks, impressions, click-through rate, and average position, with a trend for the selected period. Search Console defines click-through rate as clicks divided by impressions; position is a relative ranking of a result, with 1 at the top. Google’s metric definitions also make clear that an impression and a click describe search result activity, not what happened after a visitor reached the site.
The second level should let a reader move between a query and the pages that appeared for it, or start with a page and see the queries associated with it. Search Console supports filters for queries and URLs, including text matches and regular expressions. Google’s filtering guide also cautions that query or URL filters can change totals because some data is truncated or anonymized. The practical design is a page table with clicks and impressions, a query table for the selected page, and visible filter labels. For a content lead, “which page lost clicks for a relevant query?” is a better follow-up than “why is SEO down?”
Keep property totals and page totals distinct. Google counts results differently when Search Console data is aggregated by property versus by page. If multiple pages from one property appear for the same query, property-level impressions may count the property once while page-level rows count each URL separately. The newest performance data can also be preliminary. Google’s explanation of aggregation and freshness is a reason to label the grouping and latest complete date before comparing two charts. An apparent mismatch between a total and page rows is therefore a prompt to check how the view was grouped, not an immediate sign that tracking failed.
This dashboard can guide a decision to inspect a page’s title, search appearance, and content match to a query. It cannot tell you that a drop was caused by a specific edit, or that more impressions will turn into more customers. Pair it with a site engagement view when the decision depends on what visitors do after the click.
An engagement dashboard shows which assets earn a response
When a campaign has already reached people, the next question is whether its email, form, or landing page drew the intended response. Salesforce’s standard B2B Marketing Analytics Engagement dashboard gives a concrete example: it covers list emails, forms, and landing pages, with filters for year, quarter, campaign, and tag. Its email view includes sends, opens, unique clicks, bounces, opt outs, and undelivered messages; its form and landing page views include views and submission measures. Salesforce’s dashboard description documents those fields.
Arrange the view so a campaign owner can follow one asset at a time: exposure, interaction, submission, then the next recorded stage. Put the count beside each rate. A landing page with a high submission rate and very few views may need more qualified traffic; one with many views and few submissions calls for a closer look at the page, offer, and form. Neither pattern proves the cause. The dashboard identifies where to inspect the experience, and the underlying asset tells the rest of the story.
Do not flatten all engagement into a single score. An email click, a form submission, and a landing page view are different actions with different denominators. Comparing them as if they were interchangeable makes a campaign look stronger merely because it generated more easy-to-record events. This is the view for improving a specific asset or campaign journey, not for declaring which campaign produced revenue.
A pipeline dashboard follows leads into sales
For a B2B team, a lead count becomes useful only after everyone agrees what happened to those leads. Salesforce’s standard Pipeline dashboard illustrates the broader view: visitors, prospects, marketing qualified leads, sales qualified leads, and closed-won opportunities, with pipeline dollars, conversion rates, and stage velocity. It also allows campaign and source breakdowns. Salesforce’s Pipeline dashboard guide shows the stages in the context of its connected datasets.
Use that sequence as a model for the question, not as a universal funnel to copy. One organization may count a marketing qualified lead when a person reaches a score threshold; another may require a particular request or a sales review. The dashboard must print its own stage definitions near the chart or link to them. Otherwise, a falling conversion from MQL to SQL could mean weaker leads, a changed qualification rule, or a delayed sales handoff. The same chart would support very different actions under those conditions.
A useful pipeline screen shows both volume and movement: how many records entered each stage in the selected cohort, how many advanced, and how long movement took. Keep the date logic visible. A chart of leads created this month beside deals closed this month does not describe one cohort’s conversion; the deals may have begun earlier. If the system cannot reliably connect lead and opportunity records, show the gap as an unknown instead of filling it with a confident-looking rate. The cost of a truthful pipeline view is extra work on definitions and record links, but those are exactly the details a budget decision depends on.
A campaign contribution dashboard needs a stated credit rule
GitLab’s documented Demand Generation Dashboard offers a more specific example for a team that already connects campaigns to pipeline. Its summary shows touchpoints, marketing qualified leads under a linear attribution method, a count of sales accepted opportunities included in marketing generated pipeline, and the pipeline dollar amount. Users can move from geographic region or marketing channel into campaigns and then into individual opportunities. GitLab’s dashboard handbook describes that path from summary to records.
The useful lesson is the explicit credit rule. GitLab defines a touchpoint as a measurable marketing interaction and distributes MQL credit across touchpoints before the person became an MQL. In its documented three-touchpoint example, each touchpoint gets about one third of the MQL credit. Filtering to one campaign shows its credited share rather than counting the whole MQL again for every campaign. The displayed amount is a result of that rule; it is not proof that one campaign alone created the lead. GitLab’s explanation of linear MQLs makes the distinction clear.
Time selection changes the story too. GitLab offers a touchpoint cohort organized by when an interaction occurred, an MQL cohort organized by when a person became qualified, and a marketing generated pipeline cohort organized by when pipeline was created. In the pipeline cohort, associated touchpoints may precede pipeline creation by up to one year. GitLab’s cohort definitions show why “this quarter’s campaign activity” and “pipeline created this quarter” cannot be treated as the same population. Put the chosen cohort next to the date range on any similar dashboard.
This example is worth adapting if campaign records, lead dates, and opportunities are connected well enough to support the credit rule. If they are not, begin with campaign engagement and pipeline stage views separately. A precise attribution chart built on incomplete links will encourage a false budget move. Even with good links, the result is a description of recorded contribution under one model, so it should start a discussion about channel investment rather than end it.
An executive dashboard should point to the next conversation
Leadership usually needs a shorter view than a campaign owner. Salesforce’s standard Marketing Manager dashboard combines pipeline, campaigns, and engagement, with year and quarter filters and links into its Pipeline and Engagement dashboards. It includes opportunity, cost, revenue, lead volume, conversion, and campaign return figures. Salesforce’s description of the Marketing Manager dashboard is a useful example of a summary that leads to detail.
The executive version should show the few measures that change a resource decision, their period comparison, and the strongest driver or exception worth discussing. If pipeline is down, leaders need to know whether the change sits in lead volume, sales acceptance, opportunity creation, or deal timing before shifting spend. A link from each summary measure to its detailed view is more useful than a wall of miniature charts. An annotation explaining a campaign launch or a changed stage definition can prevent a reasonable reader from attributing every movement to campaign performance.
Keep the executive dashboard honest about timing. Revenue, opportunity creation, campaign activity, and traffic do not arrive on the same schedule. Present them together to show the business picture, but label their periods and populations so a leader does not read adjacent numbers as a single conversion path. The price of clarity is leaving some attractive metrics off the front page; they belong one click down where their definitions and breakdowns are available.
Build the first version around one recurring question
Choose the example closest to the decision that repeats in your team’s meetings. If the question is “where did traffic change?”, start with acquisition. If it is “which page should we improve?”, start with Search Console’s page and query view. If it is “why are leads failing to reach sales?”, start with a pipeline view and settle the stage definitions before drawing the funnel. Reserve campaign contribution for teams that can trace recorded interactions through to opportunities.
Then make a modest first version: one clear period, a prior-period comparison, the essential count beside each rate, and a path into the records behind a change. Give the dashboard a named owner who can keep definitions and filters current. Review it against a real decision: can a reader identify what changed, where to look next, and what information is still missing? If the screen only prompts someone to ask for another spreadsheet, the next improvement is probably a better breakdown or definition, not another chart.