BlogInquiry measurement
Measuring website inquiries: useful contacts, appointments and verified sales
A WhatsApp click does not establish an inquiry or sale. Connect each stage to a record and retain what is still unknown.
Test worksheet: Website inquiries: useful contacts and verified sales
A WhatsApp click does not establish an inquiry or sale. Connect each stage to a record and retain what is still unknown. Record inputs, expected outcome, evidence, owner and observed result.
Define the outcome your business needs
A factory may consider an inquiry useful when product, quantity and date are provided; a carrier needs route and requirements; a service company checks whether work fits its scope. Write a verifiable qualification criterion. Do not change it to flatter a campaign or discard legitimate inquiries solely because one detail is still missing.
Google Analytics describes recommended events such as generate_lead for forms or information requests. The Matomo measurement plan starts from objectives and observable actions. Use those tools for defined stages, but verify receipt and qualification in operations: an event does not confirm a sale by itself.
Fictional example: 300 sessions to one verified sale
A rehearsal website records 300 sessions and 30 contact-button clicks. The destination receives 12 submissions; three are retries of existing cases, leaving nine unique inquiries. Sales qualifies four, confirms two appointments and later verifies one sale in that cohort. These synthetic figures explain denominators and are not Nightly or customer traffic results.
Nine unique inquiries from 300 sessions equal 3%. Four qualified inquiries out of nine received equal approximately 44.4%. Do not compare the 3% with 30 clicks as though they measure one stage. Link the sale to a cohort inquiry and follow-up period: a sale from an earlier conversation does not automatically belong to these contacts.
| Stage | Fictional count | Required evidence |
|---|---|---|
| Contact click | 30 | Defined event and period |
| Received submission | 12 | Destination record |
| Unique inquiry | 9 | Identification and retry rule |
| Qualified contact | 4 | Sales criterion and decision |
| Confirmed appointment | 2 | Calendar confirmation |
| Verified sale | 1 | Linked commercial record |
Check measurement through a complete inquiry
Create an identified fictional inquiry and follow it through receipt, classification and a test appointment. Check that button, form and sales tools do not count the same event several times. If a response is lost and the customer retries, preserve the original reference; deduplication by name can combine different people.
| Case | Expected result | Evidence |
|---|---|---|
| Customer only clicks WhatsApp | Click without claiming received inquiry | Event and absent receipt |
| Form received correctly | Identifiable inquiry at destination | Reference and time |
| Three retries of one case | One unique inquiry with attempts retained | Key and history |
| Sales qualifies an inquiry | Recorded criterion and owner | State and decision |
| Calendar does not confirm appointment | Still pending, not counted confirmed | Calendar result |
| Source unavailable | Unknown origin without invented attribution | Record and limitation |
Allow differences between tools
Analytics, forms and CRM may use different windows, time zones and filters. Some visitors also do not generate every measurement event. Keep each source's counts and explain scope; do not force agreement by deleting inquiries the business actually received. Fewer events may indicate instrumentation failure rather than reduced interest.
Google Analytics policy on personal information prohibits sending data Google can recognize as personally identifiable, including email addresses or personal phone numbers. Use appropriate technical references and review fields, URLs and parameters before tracking. Data needed to respond can stay in its authorized system without being copied in full into analytics.
Use the failing stage to choose a correction
Many clicks with few verified inquiries suggest reviewing receipt and friction. Received inquiries without replies need follow-up; out-of-scope contacts call for reviewing messaging and classification. An observation does not establish causality: change something specific and compare sensible periods and cohorts. Adding an event does not promise sales.
Use forms and spam, easier buying and website performance for the relevant stage. The worksheet has ten cases without measured outcomes. Bring definitions, an anonymized inquiry and count sources to a free consultation on websites to review what can be demonstrated and what remains unknown.
Frequently asked questions
It is observed intent to open a channel, not evidence that someone wrote. Record the click separately and confirm an inquiry in its destination when authorized access exists. Do not report it as a customer or sale.
A business-agreed consistently applicable criterion, such as in-scope service and sufficient information to review a quote. Record owner and reason. A label without a definition cannot fairly compare campaigns.
Use a reference or evidence linking inquiry and commercial record within the follow-up window. If the source cannot be confirmed, leave it unknown. Matching dates or a salesperson's question may not resolve attribution.
Report each channel and identify the same case where a valid rule exists. Retain origins and avoid deduplicating solely by shared phone or name. Explain whether the total counts submissions, conversations or unique cases.
Sources
- GA4 recommended eventsGoogle
- Matomo Analytics Measurement PlanMatomo
- Avoid sending personally identifiable informationGoogle
Last updated:
