Measure Website Enquiries, Not Just Visits: An Analytics Plan for SMEs

c
ceofounder
11 min read 38 views
Measure Website Enquiries, Not Just Visits: An Analytics Plan for SMEs
Website Analytics

Measure Website Enquiries, Not Just Visits: An Analytics Plan for SMEs

A monthly report that celebrates more visits can still hide a website that generates no useful enquiries. The useful question isn't just “How many people came?”

A small specialist firm may receive fewer visitors but win valuable projects from the right audience. The real question is: “Did the site help the right people take the next step — and what can we learn from that?”

Pick the actions that matter

Start with two or three actions the website should support:

  • Completed enquiry forms
  • Clicks to a phone number
  • Booking requests
  • High-value document downloads
  • Pricing page → contact action
Keep the definitions clear. A click on a WhatsApp button is evidence of interest, but it is not proof that a conversation became a qualified lead or sale.

Separate activity from outcomes

Visits, page views and engagement help diagnose how people use the site. Enquiries, qualified opportunities and attributable revenue are closer to business outcomes. Record both types — but never present them as interchangeable.

Diagnostic

Activity

Visits, page views, engagement. Useful for understanding how people use the site.

Business outcome

Outcomes

Enquiries, qualified opportunities, attributable revenue. Closer to what the organisation actually cares about.

If a form receives many submissions but few relevant enquiries, review the offer, form questions, targeting and follow-up process — rather than celebrating volume alone.

Create a baseline before redesigning

Record the current performance over a sensible period and note changes in advertising, seasonality, service availability or tracking. This does not prove causation, but it gives you context. After a change, compare similar periods and check whether measurement was configured consistently.

Avoid claiming that a redesign caused an increase when several other factors changed at the same time.

Protect privacy and respect consent

Analytics tools can collect information about how people use a site. Review what is collected, who can access it and what notices or consent mechanisms are appropriate to the organisation and applicable law.

Do not collect sensitive details in analytics event names or send private form content to analytics services. See the Office of the Data Protection Commissioner for Kenyan data-protection resources, and obtain qualified advice for questions about compliance.

Turn the report into a decision

A useful monthly review should answer four questions:

  • Which pages attract relevant visitors?
  • Where do important journeys stop?
  • Which channels produce useful leads?
  • What one change will we test next?

End with a decision and an owner — instead of a screenshot full of charts.

Distinguish source, influence and attribution

A visitor may discover a business through a referral, read a website article later and finally contact the company after a conversation. Analytics systems cannot automatically explain every influence on the decision.

Record how the lead says they heard about the business where appropriate, use campaign tags consistently and treat attribution as an estimate rather than absolute truth. This helps prevent the team from overvaluing the last click or undervaluing offline relationships.

Use consistent campaign naming

When using links in email, social posts or paid campaigns, agree a simple naming convention for source, medium and campaign. Different spellings for the same campaign fragment reporting and make comparisons unreliable. Keep the convention documented and test the tagged link before publication.

Do not include names, phone numbers or other private details in tracking parameters.

Connect lead data carefully

If the organisation also uses a customer-management system, decide which fields will be shared and how leads will be matched. The goal is to understand whether website enquiries progress — not to copy every analytics detail into a customer record. Limit access to the combined information and avoid sending sensitive form text to analytics services.

Avoid dashboard theatre

Do not add a metric just because the tool can display it. Every chart in a review should help answer a question or support a decision. If a number changes, ask whether the change is meaningful, whether tracking changed and what else happened during the period. End the review with an action, an owner and a date to check whether the action helped.

Build a useful monthly measurement review

1

Agree what counts as a meaningful website enquiry and what makes that enquiry qualified. Select a small set of actions to track, such as completed forms or booking requests, and test them before relying on the data.

2

Record a baseline and note campaigns, service changes or seasonal events that might affect results. Separate visits and clicks from completed enquiries and opportunities. Review privacy settings and avoid placing sensitive content in analytics events.

3

Hold a monthly review that answers one business question, identifies a change to test and assigns an owner. After the test, inspect whether the result improved and whether tracking remained consistent. Keep the report short enough that the owner can make a decision from it.

Illustrative example

Report three measures — separately

600 Service page visits
18 Enquiries submitted
5 Qualified leads

Do not call all 18 “customers,” and do not imply the numbers are a benchmark for other businesses.

Frequently asked questions

Is website traffic still useful?

Yes, as a diagnostic measure, but it should be interpreted alongside enquiries, lead quality and business outcomes.

Can analytics prove a redesign caused more sales?

Usually not by itself. Document other changes and describe attribution limitations honestly.

Action checklist

  • Define what counts as an enquiry and a qualified lead.
  • Track important actions consistently.
  • Compare activity metrics with actual lead outcomes.
  • Check privacy and access settings.
  • Use monthly findings to select a specific improvement.

Final thought

Analytics earns its keep when it improves decisions, not when it produces more charts. Start small, define your metrics and review lead quality alongside traffic. Google's Analytics guidance can help with tool-specific questions.

Want a site with measurement foundations built in?

To discuss a site with measurement foundations appropriate to your business, talk to Stonehenge Digital KE about the website service.

Explore the Portfolio & Organisational Website Service →
Share Written by ceofounder

Interested in Portfolio & Organisational Website?

Let's build this for your business

A professional, mobile-first website that makes your business look credible and gets found on Google.

Leave a Comment

Share Your Thoughts