Library · Chargebacks · How to run this
Alert-to-CB lag is not escape rate
CB day − alert day make lag days. Type both plus alerts that became CB.
Pair: Alert-to-CB lag on Chargebacks. Escape: alert-escape rate. CDRN: CDRN alert-to-refund lag.
What you type
Alert day — day index when Chargebacks911 fired the alert.
CB day — day index when that alert posted as a bank CB.
Alerts that became CB — alerts in that lag window that later posted as CB.
Lag days = CB day − alert day. Pull refund / fight earlier when lag days are fat. Do not invent a lag chip.
What not to do
Do not invent lag days. Do not fold escape % into day indexes. Do not paste Chargeblast refund lag onto a Chargebacks911 CB clock. Do not blend MIDs when one owns the lag.
Related: Chargebacks, alert-escape rate, alert-to-refund lag, CDRN alert-to-refund lag.
Procedure
- Type alert day, CB day, and alerts that became CB.
- Read lag days.
- Tighten refund / fight clocks when lag days are material.
Failure modes
- Inventing lag days.
- Mixing escape counts into day indexes.
- Treating alert-to-refund lag as alert-to-CB lag.
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
- Alert-to-CB lag days
- CB day − alert day.
Work with us — We run this job on your accounts. Services
FAQ
- Is this alert-escape rate?
- Count share. [Alert-escape rate](/manuals/chargebacks911-alert-escape-rate) is alerts that still CB ÷ alerts. This page is CB day − alert day.
- Is this alert-to-refund lag?
- Refund clock. [Alert-to-refund lag](/manuals/chargeblast-alert-to-refund-lag) is alert hour to refund hour. This page is Chargebacks911 alert-to-CB lag.
- What lag days should I invent?
- None. Type alert day, CB day, and alerts that became CB from the same Chargebacks911 export.