Library · Traffic · How to run this
Tracker cost is not tracker revenue
Cost $ and revenue $ on the tracker make gap %. Gap % = (revenue − cost) ÷ cost × 100. Type both.
Pair: Cost vs revenue gap on Traffic. Lag: cost vs CRM lag. Bots: bot-filter waste.
What you type
Cost $ — tracker-reported media / traffic cost for the window.
Revenue $ — tracker-reported revenue for that same window.
Gap % = (revenue − cost) ÷ cost × 100. Kill or fix the offer when gap % stays negative — do not invent a gap chip.
What not to do
Do not invent gap %. Do not mix CRM settled into tracker revenue without a rule. Do not fold bot waste into cost twice. Do not average every offer when one owns the hole.
Related: Traffic, cost vs CRM lag, bot-filter waste, offer URL fail.
Procedure
- Type cost $ and revenue $.
- Read gap %.
- Kill or fix the offer when gap % stays negative.
Failure modes
- Inventing gap %.
- Mixing CRM settled into tracker revenue without a rule.
- Folding bot waste into cost twice.
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
- Cost vs revenue gap %
- (Tracker revenue − tracker cost) ÷ tracker cost × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this cost vs CRM lag?
- Sibling gap with lag days. [Cost vs CRM lag](/manuals/redtrack-cost-vs-crm-lag) adds CRM lag. This page is tracker cost $ vs tracker revenue $ only.
- Is this bot-filter waste?
- Related waste. [Bot-filter waste](/manuals/voluum-bot-filter-cost) is billed spend on bot clicks. This page is (revenue − cost) ÷ cost on the tracker book.
- What gap % should I invent?
- None. Type tracker cost $ and revenue $ from the same offer window.