Operational guide · October 6, 2026
Your infrastructure shows traffic.
Your analytics does not.
Find out what is missing.
Start by asking what each system actually counts. Then verify the collection path. A bigger request number is neither proof of more customers nor a reason to discard it.
Start with your own source
Already need to distinguish machine requests from browser visits? Check whether your infrastructure can deliver request evidence before creating a collector or paying.
Four measurements, four different questions
Edge requests: What HTTP traffic reached the measured infrastructure? Assets, crawlers, previews and operational tests can all contribute. Traffic served or blocked outside the application may not appear in application records.
Browser measurement: Which eligible browsers executed the measurement code under the visitor's privacy choice? This is not a substitute for machine-request logs.
Useful operations: Did a scan, protocol call or connected delivery actually return the expected result? A request to a tool route is an attempt. A successful HTTP status is not always a successful task.
Commercial value: Did the billing provider confirm the subscription or payment, did the application grant the correct access, and did the customer obtain value afterward? None of the first three counts can answer that alone.
A real example from our own audit
Our October 6 review found 446 AI-classified request records over a rolling seven-day window. GA4 separately reported 63 sessions for September 29 through October 5. These are deliberately different datasets and windows, not a conversion-rate numerator and denominator. The review did not establish a new independent paying customer.
More importantly, we found that some query failures could look like zeros and that the blog used a separate measurement path. These were defects in our reporting implementation, not evidence that visitors had disappeared. The current self-observation service exposes source availability and the new measurement boundary instead of silently treating missing evidence as success.
The practical investigation
1. Align the window and scope. Record the timezone, hostname, paths and inclusion rules of each source. Keep all-edge, origin-only and browser-only evidence separate.
2. Verify collection before judging demand. Check query failures, latest successful writes, tag ownership and consent state. Missing data should say unavailable, not zero.
3. Split requests by purpose. Separate recognizable previews, internal tests and discovery files from production-use attempts. Unknown client identity remains unknown; it should not prevent protocol requests from being counted.
4. Verify the consequential operation. For a scan, look for a persisted report. For a protocol call, inspect its operation result. For a connected source, distinguish a reserved test delivery from the first real non-test request.
5. Reconcile the outcome. Compare application access with provider billing. Then separately establish whether the customer is independent, obtained a useful result, and returned.
What you receive from AIWebSignals
The free scanner checks public access and discovery signals without an account. Connected monitoring addresses a different question: what arrived at infrastructure you control. Its setup requirements depend on your source; the source-fit guide explains what you need before you create anything.
We do not promise rankings, citations or sales. We provide a way to examine the evidence and choose a defensible next action.
Evidence and methods
Live self-observation JSON · Unified source-status report · Research methodology · Google Analytics collection documentation · Cloudflare analytics documentation
Our audit is operator-owned evidence, not independent validation. Counts above are a dated snapshot. Test traffic and unknown affiliation do not establish customer acquisition.