Library · Chargebacks · How to run this
Kount duplicate alert is not Forter duplicate alert
On one Kount fraud-desk cut, put repeat alerts over all alerts. That is KT dup %.
Pair: Duplicate-alert share on Chargebacks. Forter twin: duplicate-alert. Disputifier twin: duplicate-alert.
What you type
Duplicate alerts — Kount alert rows the fraud desk tags as a repeat in the cut.
Alerts — All Kount alert rows in that same fraud-desk cut.
KT dup % = duplicate alerts ÷ alerts × 100. Fat KT dup % means dedupe first. Never invent a KT dup chip.
What not to do
Do not invent KT dup %. Do not paste a Forter or Disputifier duplicate file into Kount fields. Do not treat cover gaps as duplicates. Do not mix networks when one seat owns the repeats.
Related: Chargebacks, Forter duplicate-alert, Disputifier duplicate-alert, alert-coverage.
Procedure
- Type duplicate alerts and alerts.
- Read KT dup %.
- Dedupe intake when KT dup % is material.
Failure modes
- Inventing KT dup %.
- Dumping a Forter or Disputifier duplicate-alert file into Kount fields.
- Folding Kount alert-coverage into duplicate-alert counts.
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
- KT dup %
- Duplicate alerts ÷ Alerts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Forter or Disputifier duplicate-alert share?
- Sibling desks. [Forter duplicate-alert share](/manuals/forter-duplicate-alert-share) and [Disputifier duplicate-alert share](/manuals/disputifier-duplicate-alert-share) score those intakes. Here you only divide Kount duplicate alerts by Kount alerts.
- Is this Kount alert-coverage gap?
- Seat cover, not repeats. [Alert-coverage gap](/manuals/kount-alert-coverage-gap) is uncovered seats vs enrolled. This page is duplicate alerts ÷ alerts.
- What KT dup % should I invent?
- None. Pull duplicate alerts and alerts from the same Kount fraud-desk cut.