Measure marketing results without false certainty

Distinguish reach, interest and enquiries. A practical measurement plan with clear definitions, small numbers and honest limitations.

Lines of coloured code appear on a computer screen viewed at an angle.
Illustrative photograph. Markus Spiske markusspiske · CC0 1.0
In this article

Marketing figures help decisions when you understand what they represent. A dashboard can look precise while missing visits, counting automated clicks or allowing several channels to claim the same enquiry. Start with your question and measurement definition before looking at percentages.

You do not have to measure everything to make a useful decision. A small business can start with a regular review, a count of relevant enquiries and a few carefully chosen signs. The aim is to understand what you can improve while respecting visitors' and readers' privacy.

Start with the decision you want to make

A concrete question gives a measurement plan direction. Do you want to know whether a service page answers practical questions? Whether a newsletter takes readers to a detailed guide? Whether a campaign brings suitable enquiries? These are three different questions with different signs.

Record in advance which outcome could lead to a decision. If many interested people ask for the same missing information, add that explanation. If a form fails technically, fix it before assessing a campaign. A general visitor count does not reveal which problem applies.

Connect the question to your marketing plan. That prevents whichever figures happen to be easiest to obtain from determining your objective.

Agree what you count

Distinguish reach, an intermediate step and a result. An advertisement impression means a system recorded a display. A website visit is not yet a reader who understood the explanation. A contact-button click is not a received enquiry, and an enquiry is not a job.

For each important measure, establish the event, where it is recorded and exclusions. “Enquiry” might mean a received message about a service you actually offer. Spam, job applications and general supplier emails can remain separate without being arbitrarily excluded when a figure disappoints.

Record the period and denominator too. A conversion rate might be enquiries divided by visits, while another report uses people or clicks. Compare percentages only once you know whether definitions match.

Use a small, consistent scorecard

The scorecard below is a fictional example for a business that clarified its service page. It does not recommend always collecting all these data. Choose only what the decision needs and what you may lawfully process.

  • Is the explanation found? Visits to the relevant page over an agreed period can provide a sign. They do not prove every visitor reads it.
  • Does the next step work? Technically check the link, form and receipt. A successful test does not prove a real enquiry will follow.
  • Do suitable questions arrive? Count received enquiries under a fixed definition. A difference does not prove the text is the only cause.
  • Is important information still missing? Record recurring conversation questions. They do not reveal how every visitor views the page.

A simple list with date, count and brief context note may suffice. Do not preserve full customer messages in a measurement file if a category or count is enough. Limit access and agree when data is deleted.

If the list becomes unwieldy, first decide which decision an overview should support. Choosing a marketing dashboard helps define terms, sources and responsibilities before adding charts.

Read small percentages alongside their counts

Suppose, in an entirely fictional example, you count two enquiries and then three. That is one additional enquiry and a fifty per cent increase. The percentage sounds large, but the underlying numbers remain small. It says little yet about next month.

Always show counts beside percentages. State the period and whether the data is complete. A quiet holiday week is not automatically comparable with a busy promotional week.

Distinguish “we observed a difference” from “the change caused the difference”. The second statement needs more evidence. Longer observation or a carefully designed experiment may help, but few observations remain a limitation. A quick test with little traffic does not automatically produce a reliable winner.

Be careful with email opens and clicks

An open can be recorded when an email application fetches an image. Some privacy features do this in ways revealing little about actual reading. Other readers block images, so someone genuinely reading may produce no recorded open.

Clicks can also come from automated security checks. Treat open and click rates as technical signs with limitations, rather than exact counts of people who read or understood your message.

Replies and voluntary feedback can add context. They too are not a cross-section of all subscribers. When comparing, record whether subject, recipient group and measurement settings remained unchanged. See starting a newsletter with clear consent for the list's foundations.

Do not expect complete attribution to one channel

A customer might first hear about you in a conversation, later visit your website and then click a newsletter. A system observing only the last click may attribute the enquiry entirely to email. An advertising platform may also claim credit under its own rules.

Do not simply add these platform results. They may describe the same event using different periods or models. You can ask enquirers how they found you, but allow incomplete answers. People do not remember every touchpoint.

Campaign codes such as UTM parameters can make links recognisable in reports. They do not fully solve attribution. Do not put names, email addresses or other personal data in them, and establish consistent spelling before distributing links.

Use the practical guide to creating and checking UTM tags. It helps make a recognisable campaign code and test the destination without treating the code as proof of a unique visitor or complete customer journey.

Let privacy help determine what you measure

Collecting more data does not automatically improve measurement. Choose the least intrusive information that can answer the question. A technical function test, for example, does not need a complete visitor history.

Before starting, check what your service collects, which cookies or other techniques it uses, who processes data and whether consent is required. A product label such as “privacy-friendly” or “cookieless” does not answer every data protection question. Describe your own setup clearly and do not reverse a refusal through another technique.

Expect incomplete figures because of visitor choices, blockers or technical errors. State that limitation at the review. Filling missing observations with invented numbers makes a report less useful.

Finish with a next step you can verify

At an agreed time, review the question, figures and context notes together. First check measurement worked. A missing event can be a measurement error. Then test the actual visitor path, as described in checking your service page after publication.

Write the decision plainly: what did you see, what remains unknown and what will you adjust? “We will clarify the delivery area because that question keeps recurring” is useful. “This copy guarantees more revenue” does not follow from a traffic chart. Keep definitions and the starting point so the next review can use the same basis.