A monthly marketing report says traffic is up. The sales team says the enquiries are no better. Both observations can be true, because they describe different stages of the customer journey.

The answer is not necessarily a more complicated dashboard. Start by agreeing on what each number means and how it connects to the next step.

Separate Interest From a Completed Action

A visitor reading an article, clicking a contact button and successfully sending an enquiry has done three different things. Count them separately where the website and consent setup allow reliable measurement.

Google Analytics supports marking important actions as key events. Its official tutorial uses a confirmation-page visit to create a generate_lead event and explains how to verify it in reporting. [1]

That is a measurement example, not proof that every confirmation-page visit represents a suitable customer. The business still needs a clear definition of an enquiry and a separate way to assess its quality.

Write a Small Measurement Dictionary

Before building the report, agree on a few definitions:

  • Contact click: someone selects a contact route; completion is not confirmed.
  • Submitted enquiry: the form accepts a submission successfully.
  • Qualified enquiry: the sales team confirms it fits the agreed requirements.
  • Customer: the business records the outcome using its normal sales process.

These are suggested working definitions. Adapt them to the business and record any exceptions. A telephone enquiry, for example, may need a different process from a website form.

Avoid sending names, email addresses or enquiry-message contents into general analytics reports. Keep the information needed to handle a lead in the appropriate business system, with access limited to the people responsible.

Test the Journey, Including the Awkward Cases

Submit a test form and check that the intended event appears. Then try the situations that can distort a report: a validation error, a double click, a refreshed confirmation page or someone returning to a saved confirmation URL.

A button click should not be reported as a successful submission if the form subsequently fails. Document how repeated actions are handled, and ask the person configuring analytics to explain any limits.

This is also a useful moment to check mobile usability. If a form is difficult to complete on a phone, accurate reporting will describe the problem but will not solve it.

Compare Quality Alongside Quantity

Consider this hypothetical example. Campaign A produces 100 enquiries and 10 meet the business's qualification criteria. Campaign B produces 40 enquiries and 16 qualify. Campaign A has more submissions; Campaign B has more qualified opportunities.

That does not automatically make B the better investment. Costs, sale value and follow-up outcomes still matter. It does show why the enquiry count alone is an incomplete basis for allocating a budget.

Use a small report with traffic, successful submissions, qualified enquiries and the time period covered. Add a short note about campaign changes or tracking problems so readers can interpret unusual movements.

Use the Report to Choose One Next Action

If visitors arrive but few submit, review the offer and form experience. If submissions are plentiful but unsuitable, review the page's promise and targeting. If suitable enquiries receive slow replies, the next improvement may belong to the follow-up process.

These are diagnostic questions, not automatic conclusions. Check a sample of actual cases before changing a campaign.

A useful marketing report ends with an accountable action: who will investigate, what will change and when the result will be reviewed. That gives the numbers a purpose beyond filling a monthly presentation.