Library · Traffic · How to run this
Rockerbox ingested spend hole is not Northbeam spend coverage
Stack (platform − tracked) over platform spend for one Rockerbox window. That quotient is spend-hole %.
Pair: Spend coverage gap on Traffic. Northbeam twin: spend coverage. Channel twin: channel-coverage.
What you type
Tracked spend $ — Ad spend dollars Rockerbox ingested in the named window.
Platform spend $ — Ad spend dollars the platform booked in that same window.
Spend-hole % = (platform − tracked) ÷ platform × 100. Fat spend-hole % usually means a connector or pixel miss — chase that path; never invent a spend-hole chip.
What not to do
Skip inventing spend-hole %. Skip dumping a Northbeam spend file into Rockerbox fields. Skip folding channel-count gaps into dollar spend. Skip merging windows when one skill owns the hole.
Related: Traffic, spend coverage, channel-coverage, unattributed-spend.
Procedure
- Type tracked spend $ and platform spend $.
- Read coverage gap %.
- Fix connectors when gap % is material.
Failure modes
- Inventing coverage gap %.
- Dumping a Northbeam spend file into Rockerbox fields.
- Folding channel-count gaps into dollar spend.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Spend coverage gap %
- (Platform spend − tracked spend) ÷ platform spend × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Northbeam spend coverage gap?
- Different attribution book. [Spend coverage gap](/manuals/northbeam-spend-coverage-gap) reads Northbeam. Here you only stack Rockerbox (platform − tracked) over platform spend.
- Is this Rockerbox channel-coverage gap?
- Sibling Rockerbox door. [Channel-coverage gap](/manuals/rockerbox-channel-coverage-gap) counts missing model channels. This page is dollar spend ingested vs platform booked.
- What spend-hole % should I invent?
- None. Pull tracked spend $ and platform spend $ from the same Rockerbox window.