Agree on a qualified lead before configuring reports
Ask the people answering inquiries and the people reviewing marketing to define the same term. For a local service business, qualification might require an offered service, an address within genuine coverage, and a project the business can reasonably take on. The criteria should reflect actual operations rather than a desire to make the report look successful.
Write down the rule and its owner. If the business changes its coverage or stops offering a service, date the change so future comparisons remain interpretable. A larger qualified-lead count caused by a broader definition should not be presented as proof that marketing improved.
Keep suitability separate from the sales outcome. A suitable prospect can choose another provider. An inquiry can also remain unresolved because nobody has reached the person yet. Treating both cases as unsuitable hides information the business needs.
Use a small, clear set of statuses
A manageable starting process has a few stages, each with an observable meaning:
- Received: a real request has reached the business through a form, call, or other supported route.
- Awaiting assessment: the team does not yet know enough to judge fit.
- Qualified: the request meets the agreed criteria.
- Not qualified: the team has a reason such as an unoffered service or location outside coverage.
- Outcome: qualified work was won, lost, or remains open.
Handle spam, staff tests, and duplicates separately. Two submissions about the same job should not automatically become two opportunities. Decide how repeat requests are recognized inside the business’s approved record system, without exporting unnecessary identifying information to a marketing dashboard.
Statuses should support the team’s work. Do not create ten mandatory fields if staff can reliably maintain only three. Begin with the information needed for the next decision and expand only when a specific question requires it.
Create a measurement specification before adding events
For each website action, document what it means, what triggers it, and what should not trigger it. A successful inquiry submission is different from clicking the submit button when the form contains errors. A phone-link click shows an attempt to initiate contact, not a completed conversation.
Google Analytics recommends lead-related events, including generate_lead and qualification lifecycle events. Recommended events require implementation; naming an event in a plan does not make it collect automatically. Have your analytics specialist map events to real business stages and confirm the prescribed parameters.
Your specification can stay practical:
- Action or stage being measured.
- Authoritative system recording it.
- Exact success condition and exclusion rules.
- How repeated actions are handled.
- Who tests it and where the result is documented.
Not every business needs to send later qualification stages into analytics. An access-controlled operational record and an aggregate monthly comparison can be a useful first version. If integration is proposed, ask what decision it enables, what data it transmits, and who will maintain it.
Record source evidence without pretending it is complete
Keep observed analytics source, landing page where available, and the customer’s voluntary answer about discovery distinct. “Found you on Google” does not establish whether the person used an advertisement, a local result, or an ordinary website result. Someone may have discovered the business through several channels before returning directly.
Use an unknown category when the evidence is missing. Do not assign every untracked inquiry to SEO or force a salesperson to guess. If reports use different attribution definitions, explain the difference before comparing totals.
For SEO review, group the records that the agreed method identifies as organic-search leads. Keep the method consistent across periods and show the unassigned portion alongside it. This gives the owner a useful view without promising a complete account of every customer’s journey.
Keep personal information out of analytics
Google’s Analytics privacy guidance prohibits sending information Google can recognize as personally identifiable, including email addresses and personal phone numbers. Such data can leak through page URLs, titles, form values, and custom parameters as well as deliberate uploads.
Ask the implementer to inspect actual event payloads and confirmation URLs. Do not pass free-text inquiry details into analytics. Store necessary customer details in an appropriate approved business system with suitable access controls, and use aggregate reporting where possible. Do not assume hashing a personal identifier automatically makes an integration acceptable.
Review consent, platform requirements, and applicable privacy obligations before introducing new tracking. A measurement improvement should not create an unnecessary data-sharing risk.
Test the full route with clearly labeled test inquiries
Use non-sensitive test data and coordinate with the staff receiving it. Confirm the form works on representative devices, the request arrives at the correct destination, and the relevant event represents a successful action. Try validation errors and repeated button clicks as well as the happy path.
Then check the operational stage: can the assigned person mark qualification and record an outcome? A technically correct event is of limited value if the team never updates the lead record. Exclude tests from production results and retain a short test log with dates, issues, fixes, and acceptance checks.
Read the monthly numbers with the denominator visible
Consider a hypothetical month with 30 genuine organic-search inquiries under your agreed source method. Twenty-four have been assessed, of which 15 qualified; six remain pending. The qualification rate among assessed inquiries is 15 divided by 24, or 62.5%. Calling it 50% by dividing by all 30 answers a different question and obscures the pending work.
Show the counts and the rule beside any percentage. Keep open sales outcomes visible and allow enough time for jobs to mature. Comparing newly received leads with older leads that have had months to close can distort conclusions about the current campaign.
Turn the report into the next SEO decision
Use the results to choose specific work: clarify an often-misunderstood service, improve the landing page for a valuable offering, or correct coverage information that attracts unsuitable inquiries. A follow-up problem belongs with the operational owner rather than automatically becoming a content assignment.
When comparing ongoing SEO services, ask who maintains definitions, verifies tracking after changes, and connects reports to completed improvements. Our proposal evaluation checklist helps make those responsibilities explicit.
Contact Guardian Solutions to discuss a practical measurement plan for the services and customers your business wants to reach.