Library · Traffic · How to run this
Unattributed revenue is not spend coverage
No-credit $ ÷ total $ make share %. Type both.
Pair: Unattributed-revenue share on Traffic. Spend: spend coverage gap. Books: platform vs modeled.
What you type
No-credit $ — Sales Northbeam left with no channel credit in the window.
Total $ — All sales in that same Northbeam window.
Share % = no-credit $ ÷ total $ × 100. Fix CAPI and events when share % is fat. Do not invent a share chip.
What not to do
Do not invent share %. Do not mix spend gaps into sales $. Do not treat call share as no-credit $. Do not average every skill when one owns the hole.
Related: Traffic, spend coverage gap, platform vs modeled, call-attribution share.
Procedure
- Type unattributed revenue $ and total revenue $.
- Read unattributed %.
- Fix CAPI / events when unattributed % is material.
Failure modes
- Inventing unattributed %.
- Mixing spend coverage gaps into revenue $.
- Treating call-attribution share as unattributed $.
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
- Unattributed-revenue share %
- Unattributed revenue $ ÷ total revenue $ × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this spend coverage gap?
- Sibling Northbeam book. [Spend coverage gap](/manuals/northbeam-spend-coverage-gap) is tracked vs platform spend. This page is no-credit $ ÷ total $.
- Is this call-attribution share?
- Related grain. [Call-attribution share](/manuals/hyros-call-attribution-share) is call orders ÷ orders. This page is Northbeam no-credit share.
- What share % should I invent?
- None. Type no-credit $ and total $ from the same Northbeam window.