Library · Subscriptions · How to run this
Rebill lag is not soft-decline share
Billed day − due day make lag days. Type both plus due count.
Pair: Campaign rebill lag on Subscriptions. Soft: rebill soft-decline share. Drop: rebill-day drop.
What you type
Due day — day index when the campaign rebill was due.
Billed day — day index when it actually billed.
Due count — due attempts in that same lag window.
Lag days = billed day − due day. Fix dunning cadence when lag days are fat — do not invent a lag chip.
What not to do
Do not invent lag days. Do not mix soft-decline buckets into day indexes. Do not treat MIT/CIT mix as due count. Do not average every campaign when one owns the lag.
Related: Subscriptions, rebill soft-decline share, rebill-day drop, MIT vs CIT mix.
Procedure
- Type due day, billed day, and due count.
- Read lag days.
- Fix dunning cadence when lag days are material.
Failure modes
- Inventing lag days.
- Mixing soft-decline buckets into day indexes.
- Treating MIT/CIT mix as due count.
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
- Campaign rebill lag days
- Billed day − due day for the typed due cohort.
Work with us — We run this job on your accounts. Services
FAQ
- Is this rebill soft-decline share?
- Sibling rebill grain. [Rebill soft-decline share](/manuals/sticky-rebill-soft-decline-share) is soft declines on rebill. This page is billed day − due day.
- Is this rebill-day drop?
- Related day-N clock. [Rebill-day drop](/manuals/buygoods-rebill-day-drop) is due vs billed count drop. This page is campaign rebill lag days.
- What lag days should I invent?
- None. Type due day, billed day, and due count from the same Sticky window.