An inquiry is not the same as a qualified lead, and a qualified lead is not the same as a booked job or received payment. If you count every comment, click or event as a lead, your numbers will become meaningless. Define each state before you track anything, then apply those definitions consistently so you can compare one week to the next.
Why definitions matter before you count
A single contact episode can move through multiple states: someone asks a question, you confirm they're in your service area, they request a quote, you send the quote, they book a date, you complete the work, and they pay. Each state answers a different business question. If you label all of them "leads," you cannot tell whether posting in local groups brings more unqualified curiosity or more actual bookings.
The same person may send three follow-up messages about the same request. Those three messages belong to one inquiry episode under a single inquiry ID. A separate person who asks an unrelated question the same day is a different episode. Counting every message as a new lead inflates your total and hides the real conversion pattern.
Inquiry: A person initiates contact, asks about your service, requests information or responds to your post with a question. An inquiry does not yet tell you whether the request matches what you offer, whether they are in your delivery area, or whether they have budget and intent to move forward. A florist receives an Instagram direct message asking about Valentine's Day arrangements. That message is an inquiry. A contractor sees a Facebook group post requesting deck repair estimates and replies with availability. That reply opens an inquiry episode.
Qualified lead: The inquiry meets criteria you define in advance—service area, project type, realistic timeline, or budget range. Qualification does not mean the person will book; it means the request is worth your time to quote or schedule. The florist confirms the requested delivery ZIP code is inside the existing route. The contractor verifies the deck repair matches the crew's license and the homeowner wants to start within 90 days. Both inquiries are now qualified leads under those businesses' stated rules.
Booked job or confirmed order: The customer commits to a specific date, accepts a quote, places an order, or provides a deposit. Commitment is explicit, not assumed. A vague "sounds good, I'll get back to you" is not a booking. A signed proposal, calendar hold with deposit, or submitted purchase order is a booking.
Received payment: You have collected full or agreed partial payment, net of any refunds processed in the same reporting period. An unpaid invoice or a pending Venmo transfer is not received payment.
Some businesses add intermediate states—quoted, deposit received, work completed—to match their cash flow and fulfillment process. Choose states that answer the questions you actually need to track.
A photographer's inquiry-to-paid-session log follows each inquiry through its own stages, such as requested date available, consult held, contract signed, retainer paid and gallery delivered, so you can see where inquiries stall.
Inquiry episodes versus repeated messages
A single inquiry episode may generate multiple messages. A building-material supplier receives a Monday morning text asking for plywood pricing, a Tuesday follow-up asking about delivery slots, and a Wednesday confirmation of the order. All three messages belong to one inquiry episode if they concern the same project request. Assign one inquiry ID when the first message arrives, then log subsequent messages under that same ID with updated status notes.
A returning customer who places a new order six months later is a new inquiry episode, even though the person is not new. If your tracking rule counts new inquiry episodes, count the second order. If your rule counts new unique contacts only, do not count the second episode toward new-lead totals but do count it toward total inquiry volume and conversion.
The distinction matters when you calculate inquiry-to-booking rates. If you count three messages as three separate inquiries, your rate will look worse than it is. If you count a repeat customer's new project as zero inquiries, you will undercount actual demand.
| State | Example criteria | What it tells you |
|---|---|---|
| Inquiry | Any inbound message or comment requesting information | Volume of initial interest |
| Qualified lead | In service area, matches offered service, realistic timeline | Proportion of useful requests |
| Booked job / order | Signed agreement, deposit received, or calendar hold confirmed | Commitment rate from qualified pool |
| Received payment | Cash, check, card or transfer settled, net of refunds | Revenue collected in the period |
Platform event counts are not automatic lead counts
Google Analytics can log events when someone submits a form, clicks a phone number, or reaches a thank-you page. The generate_lead event is a recommended name for form submissions or information requests; qualify_lead reflects meeting separate qualification criteria.Recommended events Both require implementation and do not fire automatically. An event count is not, by itself, a count of unique qualified people.
A single visitor may submit the same form twice in one session because the page reloaded or they corrected an error. If the event fires on every submit action without deduplication, Analytics will count two events. Whether that represents one inquiry or two depends on your inquiry-episode rule and whether you can match both events to a single contact record in your actual business system.
A generate_lead event does not prove the inquiry is qualified. A form submission from outside your service area or requesting a service you do not offer may fire the same event. If you report event totals as qualified leads without checking the underlying records, you will overstate your pipeline.
Configure events to pass useful parameters—form name, source channel, or request type—so you can filter the event report by criteria that matter. Then cross-check a sample of event records against your inquiry log to confirm the event count matches real inquiry episodes under your stated rule.
Self-reported source is not the same as attributed source
When you ask "How did you hear about us?" at intake, the customer's answer is self-reported source. It reflects what they remember or what they believe was most important. When Analytics attributes an inquiry to a referral channel using session data or UTM parameters, that is attributed source under a defined model and lookback window.Attribution settings The two answers can differ.
A customer may answer "Instagram" because they follow your profile, even though they arrived at your contact form by typing your business name into Google after seeing a neighbor's recommendation in a Facebook group. Analytics might attribute the session to organic search, branded. Neither answer is automatically wrong; they describe different moments in the decision process.
Keep both the raw self-reported answer and a separate coded field in your tracking system. Allow "multiple," "other," and "don't remember" as valid responses rather than forcing every inquiry into a single channel. When self-reported and attributed sources disagree, investigate whether your tracking is incomplete or whether customers genuinely use multiple touchpoints before contacting you.
Unknown source is not the same as zero or proof of failure
If an inquiry arrives with no UTM parameters, no referrer header, and the customer does not remember how they found you, the source is unknown. Unknown is a real category; it is not zero inquiries, and it does not mean your social posts or other marketing failed.
Direct traffic in Analytics includes typed URLs, bookmarks, and untracked referrals from apps or documents. A Facebook Messenger inquiry that moved to a phone call, then to a form submission days later, may appear as direct in Analytics if the original referrer was not preserved. That does not mean Facebook contributed nothing.
Report unknown source as its own row in your monthly summary rather than assuming it belongs to organic social, word of mouth, or any other channel. If unknown source grows month over month, check whether contact paths are failing to pass source information—broken UTM links, missing phone-call tracking, or intake forms that do not ask the source question.
Lead-definition checklist
Use this checklist to define inquiry, qualification, booking and payment states before you build any report or dashboard:
- [ ] Write down what qualifies an inquiry as worth quoting or scheduling (service area, project type, timeline, budget).
- [ ] Decide whether repeat messages about the same request count as one inquiry episode or separate inquiries.
- [ ] Decide whether a returning customer's new project counts as a new inquiry episode.
- [ ] Confirm that event labels (
generate_lead, form-submit) describe implementation, not automatic qualified unique people. - [ ] Separate self-reported source (customer answer) from attributed source (analytics model) and keep both fields.
- [ ] Include "unknown," "multiple," "other" and "don't remember" as valid source options instead of forcing a single channel.
- [ ] Define received payment as settled funds net of refunds, not unpaid invoices or pending transfers.
- [ ] Document these rules in your inquiry log template so anyone entering data applies the same criteria.
Frequently asked questions
Is a website form click the same as a qualified lead?
No. A click on a contact form button or a phone number is an interaction event, not a lead. The person may close the form without submitting, dial the wrong number, or submit a request outside your service area. Count form submissions or answered calls as inquiries, then apply your qualification criteria to separate qualified leads from unqualified inquiries.
Should I count Instagram story replies as leads?
Count them as inquiries if the reply requests information, asks about your service, or responds to a call-to-action. Apply the same qualification rule you use for direct messages or comments. A reply that says only "Nice!" or an emoji is engagement, not an inquiry. If the reply starts a conversation that leads to a service request, log it as one inquiry episode under a single ID even if the thread includes multiple messages.
How do I turn Analytics event counts into actual lead numbers?
Ask your authorized implementer to reconcile aggregate event counts with your business inquiry log, checking for test submissions, duplicates, or spam where stable permitted evidence is available. Changes to collection require authorized review and must honor privacy choices. Leave unmatched cases as unknown, and document any adjustment in your monthly report so stakeholders understand the difference between raw event count and verified inquiry count.
Next step
Define inquiry, qualification, booking and payment using the criteria that matter for your service or product, then apply those definitions to every contact channel—social messages, phone calls, form submissions and walk-ins. Once the rules are written down, anyone entering data will apply the same standard, and you can calculate meaningful ROI from documented costs and actual received payments.
A free preliminary SEO, GEO and SMM strategy can outline examples of potential customers and help you plan your marketing approach.
Free SEO, GEO and SMM strategy, explained with examples of potential customers.