Digital marketing

How to measure qualified leads from a website

Connect website events to sales outcomes so you can distinguish activity from qualified demand.

Illustration for How to measure qualified leads from a website

Start with what sales actually uses

Interest

A click on an enquiry or phone button indicates interest. A form start says someone began typing. Track these actions separately so you can diagnose difficult steps and determine where interested visitors stop.

Accepted enquiry

Record the successful form only after the application has saved it. Give the request a reference and record when it arrived. A failed validation, a blocked CAPTCHA or a refresh of the confirmation page should not count again.

Qualified lead

Have sales confirm fit using practical criteria such as service, location and purchasing intent. Identify spam, duplicate requests and out-of-scope work consistently. Keep a pending status for records the team has yet to review.

A worked example with two campaigns

Assume the sales team classifies both campaigns using the same criteria and reporting window. The business sells services, and a sales-qualified enquiry is a valid request its team can serve.

Illustrative B2B enquiry report. Figures are for demonstration.
StageSearch campaignSocial campaign
Campaign spend₹12,000₹9,000
Form starts7088
Accepted forms4045
Unique valid enquiries3130
Qualified leads126
Cost per qualified lead₹1,000₹1,500
Quotes issued74

Read both the volume and the cost

Social produced more accepted forms and a lower cost per form at ₹200. Search cost ₹300 per form, but produced twice as many qualified leads. Cost per qualified lead is campaign spend divided by qualified leads. Here that changes the order when the campaigns are ranked by cost.

Check the cohort before changing spend

Review enquiries created in the same date range and allow sales time to classify them. Inspect duplicate and invalid reasons before attributing the whole gap to ad quality. Unknown sources should remain visible in the analysis. Keep subsequent quote and sale outcomes linked to the original enquiry cohort.

How to set up GA4 and CRM reporting

Capture the campaign context

Use consistent source, medium and campaign tags on eligible links. Record how first and later known sources are assigned. Test a new visit, a return visit and a request where attribution is unavailable. Keep an explicit unknown value so missing information is visible.

Trigger the event on confirmed success

Use an analytics event such as generate_lead when the application confirms a successful save. Repeat the form journey after a slow response, double tap and refresh, then check that these cases leave one accepted enquiry. Optional analytics may be unavailable due to consent or browser conditions.

Make sales qualification explicit

Set up clear stages for pending, duplicate, invalid, qualified and quoted. Agree who may change them and when a repeat request opens a new opportunity. Use a consent-aware plan for connecting approved identifiers across reports and keep email, names and phone numbers out of GA4 parameters.

Reconcile a sample before publishing

Compare the successful form reference and timestamp to the stored record. Check channel, landing page and sales status, including a case where analytics was unavailable. A separate operational count gives the sales team a reference for accepted forms.

Account for calls and assisted enquiries

Record what a call button click represents and who can confirm whether a conversation occurred. Use agreed manual entry fields for leads created by phone or a sales representative. Give these records the same qualification criteria.

Use outcomes to fix the right stage

If form starts increase while accepted requests fall, inspect page errors and validation. If accepted requests rise while quality drops, review offer fit and campaign targeting. If qualified leads wait too long, review routing and follow-up responsibilities.

Test the measurement plan before spending more

Use a staging form and a campaign URL with known tags. Submit one complete enquiry and run the follow-up review it should reach in the CRM. Then repeat a test with incomplete inputs, blocked optional tracking and an out-of-coverage request. Assign an owner for discrepancies before the report is used for budget decisions.

Request a measurement review

Need help putting this into practice?

Share what you are working on and where you need input.

Discuss this project