Library · Traffic · How to run this
Approved-to-paid lag is not payout $ gap
Paid day − approved day make lag days. Type both plus approvals.
Pair: Approved-to-paid lag on Traffic. Dollars: approved vs paid. Hold: payout hold days.
What you type
Approved day — day index when the cohort was approved (window clock).
Paid day — day index when that cohort was paid.
Approvals — approved conversions in that same cohort.
Lag days = paid day − approved day. Fix payout cadence when lag days are fat — do not invent a lag chip.
What not to do
Do not invent lag days. Do not mix dollar gaps into day indexes. Do not treat clawbacks as approvals. Do not average every offer when one owns the lag.
Related: Traffic, approved vs paid, payout hold days, payout revision rate.
Procedure
- Type approved day, paid day, and approvals.
- Read lag days.
- Fix payout cadence when lag days are material.
Failure modes
- Inventing lag days.
- Mixing dollar gaps into day indexes.
- Treating clawbacks as approvals.
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
- Approved-to-paid lag days
- Paid day − approved day for the typed approval cohort.
Work with us — We run this job on your accounts. Services
FAQ
- Is this approved vs paid payout?
- Sibling TUNE grain. [Approved vs paid](/manuals/tune-approved-vs-paid-payout) is approved $ − paid $. This page is paid day − approved day.
- Is this payout hold days?
- Related affiliate clock. [Payout hold days](/manuals/everflow-payout-hold-days) is hold vs CB lag. This page is approved-to-paid lag on TUNE.
- What lag days should I invent?
- None. Type approved day, paid day, and approvals from the same TUNE window.