glossary Diagnostic path Revenue Scan

Public Signal

A public signal is anything a Revenue Scan can verify by visiting public surfaces of the business — its ads, website, booking flow, tracking pixels, public review profile, search presence, and content cadence. Public signals suggest where leaks are likely; verifying internal impact requires access.

group · Diagnostic path scope · entity layer type · DefinedTerm

Definition

Public signals are intentionally observable: anyone with a browser can capture them. That is what makes the Revenue Scan a low-friction diagnostic — no credentials, no shared accounts, no internal data movement.

Why it matters

It is the foundation of the claim/evidence pattern that the entire OmniLabs Systems offer rests on. The discipline is what distinguishes a Revenue Scan from a sales-led audit.

Explore related entities

  • Revenue Scan The Revenue Leak Scan is the public diagnostic front door into Revenue OS — a diagnostic review of public-visible signals across acquisition, website, conversion path, tracking, CRM expectations, content, reviews, and reactivation surfaces.
  • Claim/Evidence Block A finding shape used across Revenue Scan, audit, and reports: a one-sentence claim, the public-visible evidence rows that support it, and the explicit limit on the claim.
  • Internal Verification Verifying a public-signal finding against the operator's internal data — CRM, ad accounts, analytics, call records, server-side events — before assigning financial impact.
  • Revenue Leak Any point in the acquisition → conversion → follow-up → retention path where addressable revenue silently degrades.
[CLAIM BOUNDARY] A public signal is evidence, not proof of internal failure. Every public-signal claim must travel with its boundary.
View the sample scan Back to Diagnostic path