Separate interest from an accepted request
A visitor opening Flor chat is exploring. A person clicking a phone link is taking a contact action. A valid request accepted by the lead system is a received inquiry. Those events should not all carry the same label.
Google Analytics recommends generate_lead for information requests or form submissions. Choose the trigger that matches your defined completed stage and verify it with the actual submission flow. An attempted click followed by an error should not create a false lead event.
Build a simple sequence your team can maintain
Use stages that have clear definitions and an owner. A smaller process that staff keep current is more useful than a detailed funnel filled with guesses.
- Discovery: relevant pages receive search visibility.
- Visit: the prospect reaches the intended page.
- Interest: the visitor starts an appropriate contact action.
- Accepted inquiry: the request is recorded for follow-up.
- Qualified opportunity: the team confirms that it fits.
- Customer outcome: the request is won, lost or still open.
Keep useful context with the inquiry
Record the selected service, project location and originating page when available. Appropriate campaign context can also help. Keep personal contact details and message contents in the protected lead system rather than analytics event fields or page URLs.
For a Central Ohio company serving several markets, the requested location may be more useful than assuming the visitor’s location identifies the job. Someone researching from Columbus may be arranging work at a different address.
Compare numbers with matching definitions
For a basic cost-per-qualified-inquiry calculation, divide the relevant marketing cost by the number of qualified inquiries within a comparable scope. State which costs and period are included. Longer sales cycles may require following a group of inquiries over time rather than comparing two unrelated monthly totals.
Analytics, Search Console and the lead system answer different questions. Consent choices, blocked tracking, repeat visits, duplicate requests and missing source information can affect their totals. Investigate meaningful differences without pretending that all systems observe the same journey.
Use the pattern to decide what to improve
If the right pages receive little relevant discovery, review the search purpose and technical access. If visitors arrive but do not begin an inquiry, examine the offer and next step. If requests fail, fix the submission path. If accepted requests are unsuitable, improve qualification and targeting.
Ask the receiving team for a short, consistent outcome reason. “Outside coverage,” “wrong service” and “useful project discussion” are more actionable than a single undifferentiated lead total. The next page or campaign change can then address a specific problem.
Sources & further reading
Official references behind the local context and platform guidance. Recommendations are ColumbusSEO’s interpretation for business websites.