Make sure enquiries are actually being measured
Define what counts as an enquiry: a successfully submitted form, a call, an order or a quotation request. A button click does not prove that the message arrived. Compare analytics with the actual enquiries in the working channel and check the selected goal. Consent conditions and tracking configuration can also affect the available statistics.
For a controlled check, agree a test enquiry and follow it through to receipt. Do not create a paid order or repeatedly submit forms just to test them. If the interface says success but the message is lost later, investigate enquiry handling. If the contact arrived but the goal was not recorded, repair measurement before concluding that the traffic is ineffective.
Use one clearly defined rate
Session conversion rate is the share of visits containing a selected target action. For enquiries, divide visits with an enquiry by all visits and multiply by one hundred percent. A visit is a session. An analytics service identifies visitors using its own rules: the same person may be counted separately across devices or browsers. Visits, recorded visitors and a confirmed count of people are therefore different measures.
One person can submit a form twice within one visit, so total submissions differ from converting visits. In an illustrative example, one thousand visits and twenty visits with an enquiry give two percent. This is arithmetic, not a universal good or bad benchmark. Meaningful evaluation also needs enquiry quality, the visitor’s task and comparable conditions.
20 / 1 000
20 visits with an enquiry out of 1,000 visits.
Understand why the visitor came
An overall report combines different intentions. Someone reading a tutorial may be learning, while someone on a specific service page may be choosing a supplier. Separate visits at least by channel, landing page, device and region. Compare groups offered a similar next step. An explanatory article and an order form should not automatically have the same enquiry rate.
Imagine that traffic increased after an accessible explanation of a term was published, but enquiries did not change. That alone does not identify a form problem. Check whether the topic reaches your audience and whether you offer a relevant service and give the reader a clear route to it. For purchase-oriented searches landing on a general company story, the offer may instead need to become more specific.
Follow the route as a new customer
Open the landing page on a phone without relying on internal knowledge of the company. Is the problem you solve clear? Can a visitor understand the scope and how to begin? Are limitations, the estimating process and contact choices visible? Provide essential decision information before asking for contact details, rather than making people search several sections for it.
Then check the action itself: the button is visible, fields are labelled, errors are understandable and corrections preserve entered data. On a small screen, the keyboard should not hide an important step. Pressing a button needs clear feedback, especially during a wait. Record specific obstacles; a request to modernise the design does not by itself define a testable improvement.
Choose one supported improvement
List observations and distinguish a fault from a hypothesis. Broken submission is a defect to repair. The idea that explaining the service more fully will help visitors choose is a content hypothesis to implement and observe. Avoid changing the traffic source, offer, form and counting rules simultaneously: the cause of a later difference would be hard to separate.
Record the reason for each action and the outcome that can be checked. For example, visitors cannot find the scope, so add a clear explanation and a discussion route. Consider sample size, seasonality, traffic quality and other business changes when comparing periods. A small sample can produce sharp fluctuations without a meaningful change to the site.
Connect the report to real enquiries
A website may produce more contacts without producing more suitable customers. Check whether enquiries reached the responsible person, were handled promptly and matched your services and working regions. Do not include phone numbers, correspondence or customer details in public reports. An initial review can use anonymised observations and aggregated figures instead.
When the cause is unclear, review the sources, page content, technical enquiry route and available data together. We discuss General iT Metrika and measurement methods around your task: which actions matter, how to relate them to enquiries and what data is already available. An SEO plan becomes more useful when connected to this customer journey, rather than to the traffic count alone.
Common questions
What conversion rate is normal?
There is no universal value for every website. The service, source, buying stage, measurement method and enquiry quality matter. Establish comparable data and a clear business purpose first.
Will changing the button immediately increase enquiries?
A button can be an obstacle if it is hard to notice or understand. It cannot fix the wrong audience, an unclear offer or broken submission. Choose the action that addresses the observed cause.
Do I need to share customer information for a review?
An initial review needs page URLs, a description of the journey and aggregated figures. Real contacts and correspondence do not belong in open materials or educational examples.
Sources and documentation
From understanding to action
Connect the decisions in one plan.
A focused check helps identify a cause. When changes involve structure, development, content and analytics, agree them together with priorities, ownership and verification.
Tell us about your website, priorities and the issue you have observed. We will discuss whether you need a focused stage or coordinated promotion and what the initial scope should include.
Discuss coordinated promotion