Library · Chargebacks · How to run this
Ethoca fight share is not Chargeblast fight share
ET fight % asks how often Ethoca routes an alert into a fight path in one intake window. Fought alerts go on top. Total Ethoca alerts sit under.
Pair: Alert-to-fight share on Chargebacks. Chargeblast twin: alert-to-fight. Lag twin: alert-to-fight lag.
What you type
Alerts fought — Ethoca alerts sent to a fight / represent path in the window.
Alerts — Every Ethoca alert in that same intake window.
ET fight % = fought ÷ alerts × 100. When ET fight % climbs, tighten refund-default rules before you add fight labor. Never invent an ET fight chip.
What not to do
Skip inventing ET fight %. Skip loading a Chargeblast fight or Disputifier lag export into Ethoca boxes. Skip counting escapes or duplicates as fights. Skip blending networks when Ethoca alone owns the fight pile.
Related: Chargebacks, Chargeblast alert-to-fight, alert-to-fight lag, alert-escape.
Procedure
- Type alerts fought and alerts.
- Read ET fight %.
- Tighten the refund fork when ET fight % is material.
Failure modes
- Inventing ET fight %.
- Dumping a Chargeblast fight-share or Disputifier fight-lag file into Ethoca fields.
- Counting alert escapes or 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
- ET fight %
- Alerts fought ÷ Alerts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Chargeblast alert-to-fight share?
- Other intake. [Chargeblast alert-to-fight](/manuals/chargeblast-alert-to-fight-share) stays on Chargeblast rows. Here both counts are Ethoca only.
- Is this Disputifier alert-to-fight lag?
- Lag hours ≠ fight share. [Alert-to-fight lag](/manuals/disputifier-alert-to-fight-lag) prices hours × cases. This page is Ethoca fights ÷ alerts.
- What ET fight % should I invent?
- None. Export fought alerts and total alerts from one Ethoca intake window.