A campaign report can show progress while a sales team sees no useful work arriving. The first question should be simple: what did the report count?

A button press, a submitted form, a conversation and a sale describe different moments. A small business needs a shared definition of those moments before deciding whether advertising deserves more budget. That definition can fit on one page.

Start with the decision

Write the business decision at the top of the page. For example: “We want to know whether this service attracts enquiries from customers we can actually serve.” This is more useful than “increase conversions,” because it gives the marketing and sales teams something concrete to examine.

Then choose a reporting period and a person responsible for reviewing the enquiries. A report without an owner can accumulate numbers for weeks without changing any decision.

Describe an enquiry in ordinary language

An example definition might be: “A person requests a quote for the service we advertise and gives us a usable way to reply.” Treat this as an example to adapt, not a universal standard.

List the reasons an enquiry may be unsuitable: an unsupported location, a request for a different service, a duplicate message or obvious spam. Keep “not suitable” separate from “no reply yet.” Otherwise, an operational delay can be mistaken for poor advertising.

Ask the person handling enquiries to review these definitions. Marketing cannot reliably infer every aspect of lead quality from a browser event.

Make a small event map

For each important step, write three items: the action, the evidence and the person who can check it. Opening a form is evidence of interest. A successful submission means the website accepted information. A qualified enquiry requires a business judgement.

Give those events distinct names. If the same label covers all three, a change to the form can look like a change in commercial performance even when nothing valuable has improved.

Separate the technical test from the business assessment. A working tracking event does not prove that the message reached the right inbox or that the request was useful.

Test failure as well as success

Schedule a brief test with whoever maintains the website and whoever receives enquiries. Mark test messages clearly so they do not become sales work.

Try one normal submission, one invalid submission and one repeated action. Record what the visitor saw, whether a message arrived and what appeared in analytics. If a failed attempt is counted as a completed enquiry, resolve that mismatch before using the number to judge campaigns.

For readers implementing this in Yandex Metrica, the ZHADOV guide walks through goals, successful submission events and checks against actual enquiries:
https://zhadov.ru/instrukciya-yandex-metrika/

Keep a decision journal

At each review, note the observation, the proposed explanation and the next check. “Mobile enquiries fell” is an observation. “The new form is difficult to use” is a hypothesis. Testing the form on a phone is an action. Keeping these separate prevents an attractive explanation from turning into an unsupported conclusion.

Also record changes to the offer, website and handling of enquiries. A campaign can remain unchanged while a slower response process reduces the number of customers who continue the conversation.

Finish with a handover

The finished page should identify the main event, the evidence behind it, the exclusions, the reviewer and the next review date. It should also say where unresolved discrepancies are recorded.

This is a modest deliverable. Its value is that everyone can point to the same definition when the advertising dashboard and the business tell different stories.