How to Track Website Leads Accurately

Define the event before installing a tag

For a small business, the useful question is usually “Which pages help people contact us about work we actually provide?” Decide what counts before choosing a dashboard. A quote request accepted by your website is an inquiry. A visitor opening the contact page is interest. A person tapping your number may or may not complete a call.

Colby Technologies builds websites, SEO improvements, and practical reporting tools. Connecting those services starts with consistent definitions: the website records a successful request, the owner reviews its fit, and the report distinguishes the two. This guide covers measurement; our lead follow-up guide covers what happens after the inquiry arrives.

• Form start: someone begins entering information.
• Accepted inquiry: the submission succeeds and the system acknowledges receipt.
• Qualified inquiry: a person confirms the request matches the service and business requirements.
• New client: the business records an agreed project separately.

Track success, not the attempt

Google Analytics lists generate_lead as a recommended event for an information request or form submission. Its documentation also explains how an event can be designated a key event. Our implementation recommendation is to send that event after the website confirms acceptance, rather than when the submit button is pressed.

That distinction matters when a required field is missing, a spam check fails, or the request cannot reach the server. A click-based event would still fire in those situations. If your site uses a thank-you page, make sure reloading it or visiting its address directly cannot manufacture additional inquiries. Choose one tracking route for the successful submission; adding both a tag-manager trigger and a separate application event can double-count it.

Keep names, email addresses, message text, and other personal information out of analytics event fields. Use a nonpersonal form identifier such as “project-inquiry” when you need to distinguish multiple forms.

Run a small acceptance test

Ask your developer to demonstrate the expected behavior on the actual form, including mobile. Use clearly labeled test inquiries so nobody mistakes them for customers. The following is a suggested test plan, not a claim about your current implementation.

1. Submit an empty required field. Expect validation and no accepted-inquiry event.
2. Complete a valid submission. Expect one saved or delivered inquiry, one confirmation, and one lead event when analytics collection is permitted.
3. Press submit twice quickly. Confirm the interface and backend prevent accidental duplicates.
4. Reload the confirmation page. Verify that a second lead is not counted.
5. Test a failed request in a controlled environment. Expect an honest error message and a retry path, not a success event.

Consent choices, blockers, network failures, and measurement settings can create differences between analytics and the business inbox. Analytics is a trend tool; your received-request records remain the operational check.

Keep phone intent separate from completed calls

A phone link can record that someone tapped to call. It cannot, by itself, establish that the call connected, lasted long enough to discuss a project, or came from a new prospect. Name the event accordingly and keep it separate from confirmed inquiries. If you need completed-call attribution, scope a call-tracking setup and its ongoing responsibilities before adding it.

For a small first version, an owner can record the source customers mention and whether the call was relevant. Avoid combining that manual count with phone clicks as if they were different leads. The same person may tap, call, and submit a form.

Reconcile the report with real inquiries

Illustrative example: a service page records 12 form starts, four accepted requests, and two relevant conversations. That does not prove which change will help, but it gives you better questions: Were fields confusing? Were visitors outside the service area? Was the offer unclear? Review the actual requests before buying more traffic.

Colby Technologies can scope website reporting alongside website development. Bring the current form, the place inquiries are received, and the business action you want measured. The goal is a report you can reconcile, not a collection of impressive-looking counters.