Costs & measurement

How do you track website enquiries?

Start by checking that an enquiry reaches your business. Analytics is a separate record of activity, and it can be incomplete. A reliable setup lets you compare what the website accepted with what your reports counted.

THE SHORT ANSWER

Record successful enquiries privately, then measure an agreed success event. Keep phone clicks, received enquiries and actual customers as separate outcomes.

Decide what success means for each action.

A form button click proves that someone clicked a button. Validation might still fail, the connection might drop, or the message might be rejected. For a lead event, use confirmed success after the application accepts the submission.

A thank-you page can be useful, but a reload or direct visit must not create another lead. Give each accepted submission a unique internal reference and design the measurement so retries are not counted as new enquiries.

Scroll sideways to read the full table.

Separate activity from a received enquiry
ActionWhat it tells you
Form started Someone began the form, not necessarily completed it.
Form accepted The application received the submission.
Phone link clicked Someone tapped the number; a call is not confirmed.
Enquiry became a customer A business outcome recorded after follow-up.

Keep a private source of truth.

Store the details needed to respond in an access-controlled lead system. A record should have a reference, received time, enquiry details and outcome. An email notification can help you notice it, but a notification arriving is a different question from the form saving successfully.

Do not put names, email addresses, phone numbers or enquiry messages into analytics events, page URLs or campaign labels. Google Analytics prohibits sending personally identifiable information. Keep personal details in your private system and use non-personal labels for reporting.

Connect measurement to the accepted action.

Google Analytics recommends generate_lead for a lead submission and provides separate events for later lead stages. Choose the event that matches the action you can actually confirm. Mark the appropriate event as a key event in your measurement setup.

Test in the tool’s debugging or realtime view, then compare with the saved submission. Avoid firing one event from the submit button and another from the success page for the same outcome. If multiple systems record conversions, document which one is used in each report.

Browser settings, blockers, consent choices and connection failures can prevent measurement. Your private lead count and analytics count will not always agree. Investigate the difference without assuming either number represents every step perfectly.

Use source labels with clear limits.

For links you control, campaign parameters can identify a source, medium and campaign. Use a consistent naming convention, such as newsletter / email / autumn-guide. Never place personal information in these parameters.

The page where a person enquires is useful context, but it does not necessarily reveal where they first discovered you. Someone might read a guide, return later through a bookmark and then call. Be explicit about whether you are reporting a landing page, a recent visit or an advertising platform’s attribution.

Run a small end-to-end test.

Use clearly synthetic details in a controlled test and label the resulting record. Do not send a real customer’s personal information into a debugging tool. Check privacy and consent requirements for your actual tools before enabling collection.

  • Submit one valid test and confirm one private record.
  • Try an invalid form and confirm no success event.
  • Reload the success page and check for duplicate counting.
  • Check phone clicks are labelled separately.
  • Test on a phone as well as desktop.
  • Recheck after changing the form, tags or consent controls.

Put it into practice.

A good tracking setup lets you explain the path from accepted enquiry to report. Document what is counted, what can be missed and how you check it.

Sources & further reading.

Official documentation checked when this guide was reviewed. The worked examples and practical checklists are explanatory, not platform promises.