Your website says you generated 50 leads last month. Your inbox and CRM tell a different story.
Before you change your marketing budget, ask a basic question: what is your website actually counting?
A visitor clicking “Submit,” a form successfully accepting their information, and your sales team receiving a useful inquiry are different moments. Your reporting should make those differences clear.
Here are five checks I recommend before using lead numbers to make business decisions.
1. Define what counts as a lead
Start with a sentence everyone on your team can understand:
“A website lead is a successfully submitted request for information.”
Your definition might be a consultation request, a demo booking, or a quote inquiry. Whatever you choose, write it down.
A contact button click can help you understand interest. A form start can help you understand engagement. Neither, by itself, confirms that someone completed an inquiry.
Measure those steps separately so you can see where people move forward and where they stop.
2. Check what causes the event to fire
Submit a test inquiry and follow the entire process.
Does your tracking fire when you click the button? When the form accepts the submission? When a confirmation message appears?
Then try submitting with a required field missing. If your lead event still fires, your report may be counting an unsuccessful attempt.
In GA, Google recommends the generate_lead event for lead acquisition actions such as form submissions and requests for information. Choosing that name is one part of the setup. You still need to verify that your implementation fires at the intended moment.
3. Look for duplicate counting
One successful submission should be easy to trace through your measurement setup.
Check whether the same action is being recorded by a form integration, a GTM tag, and a confirmation page event. Multiple signals can be useful, but your lead total needs a clear counting rule.
Also test what happens when someone refreshes the confirmation page or clicks the submit button twice.
These checks help answer a practical question: did you receive two inquiries, or record the same inquiry twice?
4. Compare analytics with your lead records
Use the same date range to compare your analytics events, stored form submissions, and CRM records.
Do not expect every total to match perfectly. Consent choices, reporting definitions, spam filtering, and the way each system processes records can affect the comparison.
Look for patterns instead. Does one form consistently show more analytics events than stored submissions? Did the difference start after a website update?
Investigate the gap before deciding which number to trust.
5. Measure what happens after the inquiry
An inquiry is the start of a business conversation.
If you only report submission volume, you cannot tell whether those inquiries became qualified opportunities or customers.
Work with your sales team to understand which leads were relevant, which moved forward, and which produced revenue. A campaign that generates fewer inquiries may still bring in more valuable business.
Make the number explainable
Before trusting a lead report, your team should be able to explain what gets counted, when it gets counted, and how it connects to the inquiries you receive.
That gives you a stronger basis for deciding where to spend, what to improve, and which questions to investigate next.
At JAKs Data, I help businesses review their measurement setup, test important customer actions, and turn confusing reports into information they can use.
Need help checking your lead tracking? Visit our Contact page and tell me what you need your data to answer.