Library · Traffic · How to run this
Tracker cost lands before CRM revenue
Tracker cost posts before CRM revenue finishes. Gap % = (CRM revenue − tracker cost) ÷ tracker cost × 100. Type cost $, CRM revenue $, and lag days.
Pair: Cost vs CRM lag on Traffic. Units: CPU vs CPS. Three books: tracker vs CRM vs settled.
What you type
Tracker cost $ — media / tracker cost for the cohort window.
CRM revenue $ — CRM revenue for that same cohort (after your lag).
Lag days — days CRM trails the tracker cost day (your clock).
Gap % = (CRM − cost) ÷ cost. Negative means cost still ahead of CRM cash — do not invent a gap chip.
What not to do
Do not invent gap %. Do not mix settled bank cash into CRM without saying so. Do not ignore lag when the gap looks fine on day 0. Do not blend all offers into one cost row.
Related: Traffic, CPU vs CPS, tracker vs CRM vs settled, postback fail rate.
Procedure
- Type tracker cost $, CRM revenue $, and lag days.
- Read gap %.
- Wait the lag or fix postbacks when gap stays negative.
Failure modes
- Inventing gap %.
- Mixing settled bank cash into CRM without saying so.
- Ignoring lag when the gap looks fine on day 0.
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
- Tracker vs CRM gap %
- (CRM revenue − tracker cost) ÷ tracker cost × 100 for a cohort with typed lag days.
Work with us — We run this job on your accounts. Services
FAQ
- Is this CPU vs CPS?
- Sibling unit. [CPU vs CPS](/manuals/redtrack-cpu-vs-cps) is spend per click vs sale. This page is tracker cost $ vs CRM revenue $ with lag days.
- Is this tracker vs CRM vs settled?
- Related books. [Tracker vs CRM vs settled](/manuals/tracker-vs-crm-vs-settled) names three piles. This page is (CRM − cost) ÷ cost with the lag clock typed.
- What gap % should I invent?
- None. Type tracker cost, CRM revenue, and lag days from the same cohort window.