Measure enquiries using a consistent definition, a small private record and honest source categories, including unknown. Distinguish contact attempts, relevant enquiries and agreed work. Compare periods with their context, but do not claim that a profile change caused the difference without a suitable evaluation design and supporting evidence.
Define the unit before counting it
An enquiry count is meaningful only when everyone knows what qualifies. Decide whether you count a new request for service, every message or a completed form. A single person sending three follow-ups should not automatically become three independent opportunities. Separate spam, delivery failures, support requests and existing-project messages so changes in those categories do not masquerade as new professional interest.
Create a minimal private record with a date, enquiry identifier, broad service interest, stage and source information when known. Avoid copying full private messages into an analytics sheet. Keep operational contact details in the appropriate system and retain only the data necessary for the review. The measurement record should support a decision without becoming a second, poorly controlled client database.
Preserve uncertainty in source information
A person may discover you through a conference, revisit through a social account and contact you after a recommendation. Ask an optional, neutral source question if it is useful, and preserve the answer’s level of detail. Do not force every enquiry into a single digital channel simply because your dashboard provides a source field. “Referral, details not recorded” is more accurate than a confident guess.
Website analytics and self-reported sources describe different evidence. A tracked session can show a recorded visit path under the tool’s rules, while the person’s account may describe earlier influences. Google Analytics explains attribution as assignment of credit under a model. That allocation is not equivalent to proving what caused an individual’s decision, and missing tracking should remain a limitation rather than be silently filled.
Compare periods with their surrounding events
Keep the same enquiry definition across the comparison and record period dates. Note changes in service availability, pricing, outreach, events, referrals and form reliability. A profile edit made during a conference campaign cannot be cleanly credited with every subsequent contact. Small numbers can also vary substantially without a stable trend. Report the actual counts before presenting percentages that may exaggerate a modest difference.
Distinguish enquiry quantity from suitability. More messages may include requests outside your scope, while fewer conversations may be more relevant. Use a small set of clearly defined stages such as new request, needs clarification, suitable for discussion and closed. Do not label an enquiry a client, sale or completed engagement before the corresponding agreement or work actually exists.
Write conclusions at the level the evidence supports
A careful report might say that more recorded enquiries arrived after a contact-page revision, while outreach and event activity also changed. It can identify a plausible explanation and a useful next check without asserting causation. If a stronger causal claim matters, plan an appropriate evaluation before making changes and consider whether available traffic and controls can support the question.
Use the record to improve practical decisions: clarify a frequently misunderstood service, repair a failed contact route or adjust the information requested before a call. Do not optimize toward a larger number that hides unsuitable or duplicate contacts. The useful outcome is a more accurate understanding of observed enquiries, with explicit limits around source coverage, stage definitions and the reasons people choose to contact you.
Fictional example: a new page during an event week
A fictional workshop facilitator revises her contact page in the same week she speaks at a community event. Her private enquiry log records more new requests during that period, including several people who mention the event and several whose source is unknown. She separates follow-ups from new requests and marks two enquiries as outside her current scope.
Her review states the observed difference and the overlapping event activity. She does not attribute every request to the page revision or convert them into claimed clients. The next action is to clarify one scope question that appears repeatedly. The example contains no real measurement result; it illustrates definitions, source uncertainty and a conclusion that stays within the available evidence.
A checklist for your next step
- Define a new enquiry consistently.
- Separate duplicates and existing work.
- Retain an unknown source category.
- Record concurrent activity.
- Distinguish observations from causes.
Common questions
Can I say a redesign increased enquiries?
A before-and-after difference alone is insufficient for that causal claim. Report the observed change, relevant context and evaluation limitations.
Should I exclude enquiries with unknown sources?
Keep them visible in the overall count and label the source unknown. Excluding them can make channel comparisons look more complete than they are.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.