Measurement

Build a small business marketing dashboard that supports decisions

Choose a few trustworthy measures, explain their limitations and agree the next action.

By Graphic Core   /   Published
Monthly guide series: November 2023

A blank dashboard sketch with boxes and circles, surrounded by wooden shapes.

Begin with an action

A marketing dashboard should help a business decide what to do, not merely display every number a platform offers. Begin by writing down two or three decisions: whether to improve a service page, continue a campaign or change the way enquiries are handled. Choose a measure only when you can explain how its movement would affect one of those decisions.

A small local team may find a simple monthly table more useful than a complex live report. Record the owner, period and source for each measure. If the underlying data is incomplete, show that clearly rather than filling empty cells with invented values or treating an unavailable measure as zero.

Choose complementary measures

A useful set can include an activity, an early signal and a business outcome. For example, the activity could be improving a page; an early signal could be relevant search impressions; the outcome might be suitable enquiries for the service. Each has limits: a page can be seen without being visited, and a visit does not prove the visitor became a customer.

Include a quality check such as whether enquiries match the service and area offered. Use broad categories rather than customer names in a shared report. Avoid collecting a new identifier just to create a chart. If you compare periods, account for changes in opening hours, capacity, website configuration and the actual time covered.

Give every measure a definition

Write down the exact question each number answers. Is an enquiry counted when a form button is clicked, when a message is delivered or when staff confirm it is suitable? Does the period describe enquiries received that month or all open requests? The answer affects interpretation, especially when a quote follows weeks after the original request.

Record how duplicates, tests, spam and incomplete entries are handled. Use the same definition across reviews or clearly mark a change. If two sources count different things, label them separately rather than adding them together. A reliable manual count can be appropriate when the volume is manageable.

Show context and uncertainty

Use a headline count, the period, a short explanation and a suggested next question. A percentage should include its underlying count, particularly when there are few enquiries. One extra booking can make a percentage look dramatic in a small dataset; it may not indicate a lasting trend.

Search Console and website analytics measure different parts of the journey, and consent choices, browser settings and configuration may limit recorded activity. A report should say what is missing and who checked it. It should not imply that every customer interaction or offline recommendation is visible.

An illustrative dashboard

Imagine a team records 20 initial enquiries in one period, identifies 12 as suitable and sends six quotes to that same group. The dashboard can show those counts alongside a note that some conversations remain open. It can also record that the service page was updated, without claiming that update caused any of the enquiries.

These figures are an illustrative example, not measured results or an industry benchmark. Before acting, the team checks its definitions and asks why the other suitable requests did not yet receive a quote. The answer may be timing, missing project details or available capacity rather than a marketing issue.

ILLUSTRATIVE CHART

Example dashboard: enquiry stages

  • Enquiries20 requests
  • Suitable12 requests
  • Quotes sent6 requests
Illustrative example, not measured results. The counts describe the same hypothetical group.

Decide and assign

For each review, record one observation, one limitation and one next step. If many visitors ask a question already answered on the website, make the answer easier to find and test it with a colleague. If responses are slow because the team is busy, address the enquiry workflow before buying more traffic.

Name the person responsible and a realistic review date. Keep a short change log so the team knows what was altered and when. A dashboard is not a substitute for a conversation with staff and customers; use it to focus that conversation on evidence rather than to avoid it.

An example review meeting

Set aside a short review with the person responsible for the work and the person who handles enquiries. Start by checking the date range, definitions and any tracking or availability changes. Then show counts alongside percentages: the hypothetical pipeline of 20 enquiries, 12 suitable requests and six quotes describes a defined group and should not be mixed with an unrelated month's quotes.

Ask what the team observed that the figures do not show. Perhaps some requests are still awaiting information, or a service page creates confusion about coverage. Note the uncertainty in the report. Do not copy names, contact details or message contents into a broadly shared dashboard when a general category is sufficient.

Choose one action with an owner and a date, such as clarifying the service-area description and testing it with a colleague. At the next review, confirm the change was made and ask whether the same issue remains visible. If a metric never leads to a decision, remove it; a dashboard earns its place by helping people act.

For each dashboard item, add a short data dictionary entry: source, owner, definition, reporting period and known omissions. Ask the person who will use the report to explain what change they would make if that item rose or fell. If the answer is unclear, the measure may need a better definition or may not belong on the first page of the report.

Protect and maintain the report

Share reports with the people who need them and remove unnecessary personal details. Check whether any external dashboard provider receives information and whether the business's privacy arrangements match the actual tools in use. Review access when roles change and retain exports only as long as justified.

At each review, confirm the source, dates and definitions, then look for missing or duplicated data. Remove a metric if no one uses it to make a decision. A smaller dashboard that the team understands and maintains can be more useful than a large collection of attractive but ambiguous charts.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION