Website Leads: Measure the Inquiry, Not Just the Visit

Website traffic can increase while the business receives few useful inquiries.

A conversion event can increase while sales remain unchanged.

A form submission can be recorded even when the request is spam, outside the service area or unrelated to the business.

For this reason, lead measurement needs more than a traffic report.

The business should distinguish the stages between a visit and a customer.

Begin with the business definition of a lead

The word “lead” is often used too early.

A person who views a page is not a lead.

A person who clicks a contact button is not necessarily a lead.

Even a submitted form may not be a useful lead.

A practical business vocabulary can separate the stages.

Recorded website action

The website recorded an action such as:

• form submission;
• phone-link click;
• email-link click;
• booking request;
• quote request.

This is a measurement event.

It does not yet establish business quality.

Accepted inquiry

A real inquiry reached the business successfully.

The message may come through a form, phone call, email, booking system or another approved route.

The business has evidence that the inquiry exists.

Qualified lead

The inquiry fits the business’s criteria.

Depending on the company, this may involve:

• correct service;
• correct geography;
• appropriate budget or project scope;
• appropriate timing;
• real contact information;
• willingness to proceed to the next step.

Customer or won project

The opportunity produced an actual business outcome.

This is a later stage and should not be inferred from the website event alone.

Google Analytics supports several lead stages

Google Analytics includes recommended lead-generation events.

Its current documentation includes:

• generate_lead for a submitted form or request for information;
• qualify_lead when the lead is marked as qualified;
• disqualify_lead when it is rejected;
• working_lead when the business is actively working the lead;
• close_convert_lead when the lead becomes a customer. [1]

Google also provides a Lead acquisition report that can use these events to show new, qualified and converted leads. [2]

This vocabulary is useful because it reflects an important business principle:

lead generation is a process, not one event.

A business does not need to adopt every Analytics event name.

It does need an equivalent internal distinction.

The form event is not the final source of truth

Analytics can record that a form event occurred.

The business should also have evidence that the inquiry actually reached the intended destination.

Depending on the system, that evidence may exist in:

• a server-side submission record;
• an email delivery record;
• a CRM;
• a booking platform;
• a support or sales system.

This matters because several failures can occur between a visible button click and a usable inquiry.

For example:

• the browser event may fire but the form may fail;
• the form may succeed but notification delivery may fail;
• spam may be counted as a submission;
• a duplicate submission may create several events;
• consent or blocking may prevent Analytics from recording an otherwise valid inquiry.

The business record and the analytics event answer different questions.

Lead quality should use business criteria

A qualified lead is not simply a form with enough fields completed.

The criteria should reflect the business.

For a local service business, qualification may depend on:

• service type;
• location;
• appliance, property or job type;
• availability.

For a professional service business, qualification may depend on:

• project scope;
• budget;
• decision-maker access;
• timeline;
• fit with the service.

For ecommerce, the primary outcome may be a completed purchase rather than a lead.

The reporting system should match the actual business model.

Source attribution and lead quality should remain separate

A business may want to know where an inquiry came from.

Useful source information can include:

• Google organic search;
• advertising;
• referral websites;
• social media;
• email;
• AI assistants;
• direct visits;
• tagged campaigns.

Google Analytics provides traffic-source dimensions for users and sessions. [3]

A website or server may also preserve referral or campaign information with the inquiry where available.

However, the source label does not determine lead quality.

A qualified lead from a small source can be more valuable than ten unqualified submissions from a large source.

The report should preserve both dimensions:

SOURCE
Where the recorded visit/inquiry appears to have come from.

QUALITY
Whether the inquiry fits the business.

Some inquiries will remain unattributed

Attribution is not perfect.

A person may:

• discover the company in one place;
• return through another source;
• call later;
• type the brand name into Google;
• use a different device;
• block analytics;
• arrive without referral information.

A business should not force every inquiry into a precise source category when the evidence is missing.

Unknown can be a more accurate answer than a fabricated attribution.

This is especially important when evaluating emerging discovery channels such as AI search.

Our Insight on AI Search and Customer Inquiries explains why discovery, referral and inquiry evidence should remain separate.

A useful lead report follows the funnel

A business-facing report can use a simple sequence.

VISITS
How many relevant visits were recorded?

INQUIRY ACTIONS
How many form/call/booking actions were recorded?

ACCEPTED INQUIRIES
How many real inquiries reached the business?

QUALIFIED LEADS
How many fit the business?

CUSTOMERS / WON PROJECTS
How many produced the final business outcome?

The report does not need every number if the business cannot measure every stage yet.

It does need clear labels so that one stage is not silently presented as another.

Conversion rate depends on the denominator and the event

A “conversion rate” can mean several different things.

For example:

form submissions / sessions
qualified leads / accepted inquiries
customers / qualified leads
customers / sessions

These are all valid calculations, but they answer different questions.

A report should state the numerator and denominator instead of using “conversion rate” as if it had one universal definition.

This is especially important when comparing periods or channels.

A higher form-submission rate can coexist with a lower qualified-lead rate.

Reporting should preserve the path from source to outcome

For each important channel, the business may eventually want a table such as:

SOURCE
RECORDED VISITS
ACCEPTED INQUIRIES
QUALIFIED LEADS
CUSTOMERS

This can reveal useful differences.

One source may produce many visits but few inquiries.

Another may produce fewer visits but stronger lead quality.

A third may be difficult to attribute but appear frequently in customer self-reports.

The purpose of the report is not to make every column large.

It is to identify where the business is gaining useful opportunities and where the funnel is failing.

Measurement should improve the next decision

A lead report is useful when it changes what the business does next.

Examples:

Traffic is low, but lead quality is strong

The business may need more qualified visibility rather than a new conversion design.

Traffic is strong, but accepted inquiries are weak

The landing pages, offer, audience or contact path may need review.

Submissions are strong, but qualified leads are weak

The website may be attracting the wrong audience or failing to state service limits clearly.

Qualified leads are strong, but few become customers

The problem may be later in the sales process rather than on the website.

Source data is usually missing

Measurement quality may need improvement before channel ROI can be judged confidently.

This is why a visit and a lead should never be treated as synonyms.

The website should be measured in business terms

Traffic matters because customers must reach the website before many online inquiries can occur.

Traffic is not the final objective.

A business needs enough measurement to connect visibility and visits with the inquiries and customers that justify the investment.

Our Analytics & Conversion service uses this distinction so that website reporting can answer a business question rather than stopping at a page-view total.

Sources

1. Google Analytics Help - Recommended events
   https://support.google.com/analytics/answer/9267735
2. Google Analytics Help - Lead acquisition report
   https://support.google.com/analytics/answer/16376749
3. Google Analytics Help - About traffic-source dimensions
   https://support.google.com/analytics/answer/15612152

Analytics & Conversion Library