glossary Tracking + follow-up Tracking & Attribution System · Revenue OS

Tracking Gap

A tracking gap is any place a real revenue event in the business fails to register, or registers incorrectly, in the systems used to make spend or reporting decisions — missing pixels, broken server-side events, attribution mismatches, identity-resolution failure. Gaps make ad platforms optimise toward the wrong audience and make internal reports lie.

group · Tracking + follow-up scope · entity layer type · DefinedTerm

Definition

Tracking gaps usually live between systems: the website handing off to the tag manager, the tag manager handing off to the ad platform, the ad platform handing off to the CRM. Each handoff is a candidate gap.

Why it matters

A tracking gap is one of the cheapest, highest-leverage things to fix. The same campaign with clean tracking spends to a different audience than the same campaign with broken tracking — usually a much better one.

Explore related entities

  • Source-to-Revenue Visibility The ability to trace a real revenue event back to the source — campaign, content, channel, referral — that produced it, using internally verified data.
  • Revenue Leak Any point in the acquisition → conversion → follow-up → retention path where addressable revenue silently degrades.
  • Conversion Path The subset of the revenue path that runs from first landing to a captured conversion event — landing page, form, booking flow, checkout, confirmation.
  • 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.
[CLAIM BOUNDARY] Public-signal diagnostics can confirm missing pixels and broken server-side handoffs on the public path. Full attribution review requires access to the ad account, GTM, and back-end events.
See what the scan checks Back to Tracking + follow-up