Library · Chargebacks · How to run this
Chargeblast fight share is not alert-to-refund lag
Divide alerts fought by alerts in one Chargeblast cut. That ratio is fight %.
Pair: Alert-to-fight share on Chargebacks. Refund twin: alert-to-refund lag. Lag twin: alert-to-fight lag.
What you type
Alerts fought — Chargeblast alerts routed to a fight / represent path in the cut.
Alerts — Chargeblast alerts in that same cut.
Fight % = alerts fought ÷ alerts × 100. Fat fight % usually means refund-default rules are loose — tighten the refund fork; never invent a fight chip.
What not to do
Skip inventing fight %. Skip dumping Disputifier lag hours into Chargeblast fields. Skip treating alert duplicates as fights. Skip blending MIDs when one seat owns the fight pile.
Related: Chargebacks, alert-to-refund lag, alert-to-fight lag, alert duplicate rate.
Procedure
- Type alerts fought and alerts.
- Read fight %.
- Tighten refund fork when fight % is material.
Failure modes
- Inventing fight %.
- Dumping Disputifier lag hours into Chargeblast fields.
- Treating alert duplicates as fights.
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-fight share %
- Alerts fought ÷ Alerts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this alert-to-refund lag?
- Sibling Chargeblast clock. [Alert-to-refund lag](/manuals/chargeblast-alert-to-refund-lag) is hours from alert to refund. This page is alerts fought ÷ alerts.
- Is this Disputifier alert-to-fight lag?
- Different tool grain. [Alert-to-fight lag](/manuals/disputifier-alert-to-fight-lag) prices lag hours × cases × AOV. Here you only divide Chargeblast alerts fought by alerts.
- What fight % should I invent?
- None. Pull alerts fought and alerts from the same Chargeblast cut.