Keep website visits, recorded contact actions, received inquiries and sales qualification in separate evidence layers. Compare dated website and sales records, state what each source can establish, and mark any link between them as verified, a candidate or unmatched. A contact click can show an attempted next step while receipt and buyer quality remain unknown.
Build a layered event and sales-feedback table, with a specific owner for each gap. All W-01 and R-01 records, times and review conditions below are fictional teaching inputs, not GRC results or customer data.
What does each measurement layer actually show?
Describe the action that was observed before giving it a business label. A page view records page activity under the collection setup. A contact control may record a click. A receiving record can establish that an inquiry arrived, while a sales review decides whether it meets agreed qualification criteria.
Google's recommended events guidance distinguishes a generated lead from a lead marked as meeting qualification criteria. Recommended events require additional context and are not sent automatically. Treat those definitions as a reason to inspect your own triggers and business records, not as evidence that your store already collects them.
Use this comparison table to assign evidence to its layer. These are review responsibilities, not instructions to install event names. Scroll sideways on a phone to read all columns.
| Evidence layer | Website-side evidence | Receiving or sales evidence | What remains unproved | Next field or check |
|---|---|---|---|---|
| Visit or page activity | Named report, date window, timezone, page, metric and filters. | Usually no corresponding sales record. | Contact intent, actual receipt and qualification. | Record whether the unit is views, sessions, users or another defined metric. |
| Contact action | Documented trigger, time, page and route, when actually measured. | A possible later inquiry, still requiring independent evidence. | Whether a message was sent, received or qualified. | Verify trigger coverage and duplicate observations. |
| Received inquiry | A website reference only if legitimately available and reviewed. | Dated receiving record and inquiry-episode reference. | Exact website source, qualification or eventual sale. | Preserve receipt evidence and mark the website link separately. |
| Qualified inquiry | Analytics may reflect a business outcome if separately implemented and verified. | Sales criteria, reviewer, decision date, reason and next step. | Marketing cause or a particular browser visit without supporting linkage. | Keep pending, qualified and disqualified decisions distinct. |
A lead can be received and qualified even when its website source is unmatched. Conversely, a recorded contact action can remain unlinked to any receiving record in the material available. Preserve both observations without inventing the missing connection.
What should the website and sales records contain?
Give each side a clear reporting boundary. For website activity, retain the source report or export, site or property, observation window, reporting timezone, extraction date, metric unit, relevant pages and included channels. For a contact event, document what actually triggers it and which control it covers.
Google's enhanced measurement documentation describes page-change views and outbound-link clicks with their own triggers. A generic click event does not establish coverage of every contact control. Verify an email link or QR-image action in the actual implementation before assigning it a measurement role.
For the receiving side, keep the received time and timezone, channel, controlled inquiry reference, receipt evidence and follow-up owner. Add a source statement only when it was actually supplied, and label whether it is buyer-reported or supported by a reviewed technical link. Sales can then add a dated qualification decision and its reason.
Reviewers need enough detail to verify the observation without copying private correspondence into a general report. Google's Analytics terms set restrictions on sending personally identifiable information. Keep customer identities and message text in the appropriate controlled business records, and check URLs and other proposed fields before sending data. Any proposed identifier or data transfer needs its own privacy and implementation review.
When can a click and an inquiry be linked?
Link them only to the extent the evidence supports. The same day, contact channel and approximate time can suggest a candidate match; those details do not identify a unique occurrence. Keep the receiving record valid even when the matching website action cannot be established.
In the fictional example, W-01 records an email-link click at 10:14, America/Chicago. R-01 records an email received at 11:02 in the same timezone. The sender says they read a website article, but the records share no reviewed occurrence reference. R-01 supports receipt; the statement supplies buyer-reported source context. It does not prove that W-01 produced this email.
Inspect the gap between the two records in the diagram. The question mark is a review status, not a missing arrow the reviewer should fill by guessing.
Now change one teaching condition: suppose a separately approved mechanism preserves a shared occurrence reference on both sides, and the reviewer verifies its meaning and deduplication. That can support a link between those records. It still does not prove which marketing activity caused the inquiry or that a page change improved results. This is a conditional design example, not a claim that GRC has deployed such a mechanism.
How should sales confirm inquiry quality?
Ask sales to apply a documented business definition and record the reason for the decision. Receipt alone does not establish that the sender has a relevant project or that the business can help. A qualification record should identify the reviewer, decision date, criteria used and next action.
For a service inquiry, proposed review questions might cover the project need, fit with the offered work and whether enough context exists for a useful follow-up. Agree those criteria with the business before applying them. Do not turn an absent budget, an unfamiliar domain or a short first message into an automatic rejection rule.
Keep a pending state when the information needed for a decision is missing. In the fictional R-01 record, receipt is confirmed and quality is initially pending. If sales later confirms qualification under agreed criteria, record that dated decision; the website link can remain unverified. A follow-up message can add evidence to the same inquiry episode without creating another new lead.
Why can the two sides disagree?
They can count different units, cover different periods or observe different parts of the contact process. Website events may include repeated actions or overlapping observations. A sales record may group several messages into one inquiry episode and apply a later qualification decision.
In GRC's current contact route, visitors can use WeChat or email. Opening an email link does not prove the message was sent. Opening the QR image does not prove a WeChat message arrived, and someone can scan a displayed QR with another device without clicking that image link. These paths explain why a browser action and a business receipt need separate evidence.
Check the units in the diagram before combining records. The examples illustrate deduplication decisions, not observed counts from this website.
Align periods and timezones, distinguish event counts from people or inquiry episodes, and retain extraction and qualification dates. Avoid presenting unmatched totals as a verified visit-to-qualified-inquiry conversion rate. Our guide to reviewing an operations recommendation covers comparison and denominator checks in more detail.
Which fields should you add to the next review?
Add the field that would resolve a named uncertainty. If the contact trigger is unclear, the measurement owner needs the actual trigger definition and a verification result. If receipt is uncertain, the receiving owner needs a dated receipt record. If quality is pending, sales needs the missing business context and an agreed decision rule.
For an uncertain website-to-inquiry association, record the linkage status and supporting basis explicitly: verified occurrence, buyer-reported context, candidate match or unmatched. Record a reason and owner beside the gap. A buyer's source statement can be useful without identifying an exact session or click.
Sales feedback can also reveal a content question after this review. Preserve the permitted question summary and its answer gap separately from the lead-quality decision. The sales-question content backlog guide explains that next editorial step; it does not replace receiving or qualification evidence.
What changes when trustworthy event data is unavailable?
Leave website activity and its linkage unavailable, and review only the business evidence you actually have. A missing export, an unverified trigger or an unconfigured mapping does not establish zero activity or zero inquiries. State which part of the comparison cannot yet be made.
For this GRC article, no live analytics or private inquiry records were accessed. The project has no verified event mapping available for this review. The contact route can be described from its public page, but actual activity, receipt, qualification and attribution cannot be reported from that page. The W-01 and R-01 exercise supplies a method, not missing measurements.
When real permitted inputs become available, begin with their definitions and coverage. Keep a missing link visible while assigning a check to the responsible owner. Do not diagnose a failed page from a gap in the evidence.
What should you bring to an inquiry review?
Bring the website and contact route, documented event triggers where available, a dated activity export, and the minimum permitted receiving and sales summaries needed for review. Include reporting timezones, qualification criteria and the layer comparison table. Mark unavailable inputs before discussing conclusions.
GRC's managed website operations services include prepared-data and inquiry review. To discuss the evidence you have and the gaps that remain, bring this first table to Discuss your project. Access, permitted data and the work to agree can be clarified in that conversation.
