A visitor opens your contact page, selects the phone number, and leaves. Was that a lead? Maybe. You know they selected a link. You do not yet know whether the call connected, whether they needed your service, or whether anyone booked the work.
That distinction matters when you are deciding where to spend your marketing budget. Start by separating interest, inquiries, qualified opportunities, and customers. Your reporting should explain the difference instead of putting everything into one impressive number.
Give each stage a plain definition
Write down what your business means by each stage before configuring any software:
Stage | A practical definition |
|---|---|
Interest | Someone interacts with a service page, contact link, or booking button. |
Inquiry | A usable request reaches the business through a form, call, or booking. |
Qualified lead | The request fits your service, area, and other agreed criteria. |
Customer | The person reaches your defined sales milestone, such as an accepted contract. |
These definitions are an example, not a universal sales process. A restaurant reservation and a construction estimate should not share every rule. Agree how repeat requests, spam, existing customers, and cancelled bookings will be handled.
Google Analytics provides recommended events for lead stages, including generate_lead, qualify_lead, and close_convert_lead. They require implementation and context; they are not automatically created by installing Analytics. GA4 recommended events
Count a successful request, not a hopeful click
For a quote form, the lead event should follow a confirmed successful submission, not merely a press of the submit button. Otherwise, a validation error or failed send can look like an inquiry.
Check embedded booking tools separately. Opening the calendar is different from completing a booking. Similarly, keep a phone-link click separate from a confirmed call unless a connected call-tracking system provides that evidence.
Ask the person implementing tracking to document each event's trigger and source. If both your website integration and tag manager send the same event, the report may count the action twice. One clear owner for each trigger makes this easier to maintain.
Keep the source with the inquiry
Use consistent campaign tags on appropriate external marketing links so traffic from an email, social campaign, or referral placement can be identified. Google's URL-builder guidance explains the utm_source, utm_medium, and utm_campaign fields. Campaign URL guidance
For example, an email about seasonal maintenance could use a source of newsletter, a medium of email, and a campaign of fall_maintenance. Choose a naming pattern the team can repeat.
Where your tools support it, carry the relevant source and landing-page context into the inquiry record. Keep “unknown” available. Guessing a source to fill an empty field makes the report look complete without making it accurate.
Connect the website to what happens next
A monthly lead total cannot explain whether requests were relevant or followed up. In your CRM, record the owner, status, next action, and outcome. Decide who updates those fields; an empty pipeline will not repair itself.
For Google Ads, enhanced conversions for leads can help connect later offline outcomes to advertising interactions using a supported matching process. It needs proper setup, appropriate data handling, and actual outcome records, not just another tracking tag. Enhanced conversions for leads
Review which actions your campaigns use for optimization. Google distinguishes primary actions used with eligible bidding goals from secondary actions used for observation, with an exception for custom goals. Do not assume every imported event belongs in your main performance total. Primary and secondary conversion actions
Keep personal information out of ordinary analytics events
Do not put a customer's name, email address, phone number, or free-text inquiry into normal Analytics event parameters or tracking URLs. Google prohibits personally identifiable information in Analytics. Purpose-built advertising matching features have their own requirements; they are not permission to send personal details anywhere you want. Google Analytics privacy guidance
Review your privacy notice, consent setup, and data permissions with the people responsible for them. Installing a CRM does not establish compliance on its own.
Test the complete path
With permission from whoever receives the inquiries, send one clearly marked test. Check the confirmation, the receiving inbox or CRM, the assigned owner, and the event. Test an invalid submission too: it should not create a successful lead. Refresh the confirmation page and check for accidental repeat counts.
Use Analytics DebugView to inspect events during testing, then verify the business record separately. Seeing an event is not proof that the team received the request. DebugView documentation
Start with a report your team can explain: inquiries, qualified inquiries, customers, and unresolved follow-up. Review the records behind those totals before judging a campaign. Better measurement does not guarantee more business, but it helps you see what needs attention.
If the gap is after the inquiry, explore YALID Flow. If you need the website and campaigns considered together, see the Growth System. The next step is to find the missing connection, not to collect more numbers.
