Call (631) 559-5336Partner programClient sign in

Count the step that actually happened.

Opening a form, saving an inquiry and qualifying a prospect are separate events. Define each one so the report shows where people arrive, where they stop and what the team can improve.

DiscoverClear topics, useful pages, crawlable links
UnderstandEvidence, context and readable structure
MeasureMeaningful inquiries and working handoffs
An illustrated workflow. Each implementation has its own scope.

Agree what each stage means

Agree on a few definitions the team can apply consistently. Interest might mean opening a product inquiry. Received means the request was saved. Qualified means someone reviewed it against the service's fit criteria. Keep proposals and customer outcomes as later stages.

Do not let a software default define the business process accidentally. A button labeled conversion can include several behaviors. Write down the trigger and the evidence behind each number before using it in a performance discussion.

Count receipt when receipt is confirmed

A website inquiry event should correspond to the system confirming receipt, not only to a click on Send. Failed validation and repeated clicks should not look like separate successful inquiries. Test the implementation with a recognizable internal example.

Google Analytics offers a recommended generate_lead event for submitted information. That standard name can help organize reporting, but it does not validate your form or establish that an inquiry is qualified. Keep customer names, email addresses and message content in the business record, outside analytics event parameters.

An event-definition worksheet

Complete one definition for each stage you intend to report. The person maintaining the form and the person receiving inquiries should be able to use it to check the same example.

  • Stage and question: What business stage does this measure, and what decision will its count support? State the unit being counted: an interaction, a saved request or a reviewed opportunity.
  • Trigger and evidence: What exact action starts the count? Where can the responsible person verify that the intended work completed?
  • Exclusions and duplicates: How will failed validation, repeated attempts and internal tests be handled? Define how the business recognizes another attempt at the same request.
  • Report definition: Which system and event label carry the measure? For GA4, who checked whether it is a key event and which counting method applies, and when?
  • Context and qualification: Which source or service details are available? Who reviews fit, using which criteria, and where is that decision recorded?
  • Baseline and next review: When was the full measurement path verified? Record the reliable start date, or “not yet verified,” together with the owner and next check.

An example: one inquiry through several stages

Consider a fictional service business with a project inquiry form. It has agreed to count a saved request as received. This example illustrates the intended logic.

  1. A visitor opens the project form. That records interest if the business measures that action.
  2. A required field is missing, so validation prevents submission. No request has been received.
  3. The visitor corrects the field. The receiving system saves fictional record DEMO-201 and confirms receipt. The received-inquiry count increases once.
  4. A repeated attempt is recognized as the same request and reconciled to DEMO-201. It adds no second received inquiry.
  5. The assigned staff member checks the request against the agreed service-fit criteria and records it as qualified. That later decision belongs to its own stage.

The review can now ask where progress stopped: before submission, during receipt or during staff review. The saved request and staff decision provide the evidence for the latter stages.

Read the numbers with the inquiries

Read the inquiries alongside their products and sources. What did those people need, and did the website give them enough information? If a campaign attracts requests the business cannot serve, review its message and audience.

Keep qualification in the system where the team manages the relationship. If website reporting and the CRM are not connected, compare the records through a documented review instead of presenting a fabricated automatic funnel. Unknown source values should remain visible.

Where the data has gaps

Not every visit is recorded, and a person may return through a different device or channel. Campaign labels provide context rather than a complete explanation of a sale. Search reports, analytics and inquiry counts can differ because they measure different activity.

Small samples also need care. One additional inquiry can make a percentage look dramatic. Review the actual records and comparable time periods before deciding that a change caused an improvement. Note seasonal demand and simultaneous campaign changes.

Read the reporting columns accurately

A recorded GA4 event can appear without contributing to a key-event count. Check whether the action is marked as a key event. Marking applies from that point onward and does not change historical data. Also check the key-event counting method: once per event and once per session can produce different totals. Neither setting verifies what happened in the receiving system.

Search Console clicks and GA4 sessions describe different activity. A click leads from a Google result; a session is a period of interaction. Compare Google organic sessions with a corresponding Search Console report, matching dates and relevant country/device filters. Consent, measurement implementation, timezones and canonical reporting can still create differences. Investigate substantial discrepancies using the source reports.

Choose a change and review its effect

Choose a specific intervention based on the pattern. If visitors ask the same basic question, clarify the product page. If the form fails on a phone, fix the interaction. If good inquiries wait unassigned, improve ownership before buying more traffic.

Record the change and the date for a follow-up review. Separate internal test entries from business conclusions. The review should end with an assigned action and enough evidence to judge its effect.

  • Interest is not receipt.
  • Receipt is not qualification.
  • Qualification is not a completed sale.
  • A recorded event needs an accurate trigger and a practical use.