How to tell whether your website is bringing you inquiries.

Decide what each number actually counts.

A “Call now” click shows that someone tapped a link. It does not establish that the call connected, that the caller was new, or that they needed a service you offer. The same applies to an email link: opening an email app does not mean a message was sent.

For a local service business, a useful report keeps the steps separate. This gives the person answering the phone and the person looking at the website the same vocabulary. Agree on the definitions before comparing performance or deciding what to spend.

Start with a small inquiry record.

A spreadsheet or the system you already use to manage customers can be enough to begin. For each request, record the received date, contact channel, requested service, general service location, known source, and outcome. Keep customer contact details in the business system where you handle the inquiry.

Decide how to handle duplicates. Someone who fills out a form and then calls about the same estimate is usually one opportunity with two contact actions. Record spam, wrong numbers, existing-customer calls, and out-of-area requests separately so they do not inflate the count of new qualified inquiries.

For a contractor working around Lake Geneva, qualification might mean a request is for a service the business provides and a property inside its actual service area. Your criteria should reflect your business. Apply them consistently, and leave uncertain requests unclassified until someone checks them.

Connect website events to real actions.

In Google Analytics, an event records an interaction. Google recommends the generate_lead event for a submitted form or request for information. For your site, have the implementation trigger that event after a successful request, and test that failed attempts and repeat clicks do not produce duplicate leads. See Google’s recommended events.

• Track phone and email clicks under their own descriptive event names.
• Count a successful form submission separately from a click on its submit button.
• Check delivery in the receiving system; an analytics event alone does not confirm an email arrived.
• If using a booking provider, verify whether you can measure a completed booking or only a visit to its site.
• Use call records or an appropriately configured call-tracking service when you need to distinguish connected calls from website clicks.

Use Analytics Realtime and DebugView to verify events and their parameters. Then mark the events that matter to your business as key events. Keep the definitions in your reporting notes so a label such as “lead” does not silently change meaning later. Google explains events and their verification tools here.

Do not send customer names, email addresses, phone numbers, or free-text inquiry messages into ordinary Analytics event parameters or URLs. Google’s guidance prohibits sending personally identifiable information to Analytics. Your measurement setup should record the action without copying the inquiry itself. Read Google’s guidance on avoiding personal information in Analytics.

Be clear about what you know about the source.

Someone might first find you on Google, return through a saved link, and call after a neighbor recommends you. The source shown in a website report and the source a customer remembers can both be useful, but they answer different questions. Keep them separate when they disagree.

Add consistent campaign labels to links you control, such as an email campaign or an advertisement, and verify that the destination receives them. Ask “How did you hear about us?” when appropriate. Keep “unknown” as a valid answer instead of assigning every untracked inquiry to the website.

Our All4Seasons case study presents reported business call totals with the timeframe and source context. Business-wide calls are useful evidence of activity, but they do not establish that each call originated on the website or that one marketing channel caused the change. Apply the same distinction in your own report.

Compare periods that tell a fair story.

Choose a weekly or monthly reporting rhythm and keep the date range visible. A complete month and a month-to-date figure are different lengths of time. Changes in opening hours, weather, season, staffing, campaign spending, or service coverage can also affect the number of requests you receive.

For a business with a busy season, keep notes about those conditions next to the numbers. Compare the same metrics under the same definitions, and use the same period from the previous year when that history is available. A short run of data can reveal a problem worth investigating without establishing a lasting trend.

• Show the exact reporting dates and whether the period is complete.
• Report contact clicks, received inquiries, qualified inquiries, and booked jobs separately.
• Break out known paid-campaign inquiries and include the relevant spend when evaluating those campaigns.
• Note tracking changes, outages, promotions, and changes in how quickly you answered.
• Keep unresolved attribution and missing records visible instead of filling gaps with assumptions.

Use the gaps to choose the next improvement.

If people visit a service page but rarely attempt contact, review whether it answers their questions and makes the next step clear. If contact clicks are healthy but few requests reach the business, test the links, form delivery, booking handoff, and call-answering process before buying more traffic.

If requests arrive but many are a poor fit, review the service-area wording and the offer customers saw. That might mean clarifying a website service page, improving local search information, or tightening an advertising campaign. The report helps identify the question; conversations with actual customers help explain the answer.

For your first month, define the counts, test the contact path, record every received inquiry, and review the record once a week. At the end of the month, choose one problem to address and note the change. That gives the next report a useful decision to inform.