Library · Chargebacks · How to run this
Midigator duplicate alert is not Kount duplicate alert
MG dup % asks how often Midigator stacks the same case in one rail window. Stacked alerts go on top. Total Midigator alerts sit under.
Pair: Duplicate-alert share on Chargebacks. Sibling desks: Kount, Forter.
What you type
Duplicate alerts — Midigator rows marked as a second (or later) ping on an order already in the window.
Alerts — Every Midigator alert that landed in that same rail window.
MG dup % = stacked ÷ total × 100. When MG dup % climbs, fix match keys and suppress rules before you add headcount. Never invent an MG dup chip.
What not to do
Skip inventing MG dup %. Skip loading a Kount or Forter export into Midigator boxes. Skip counting uncovered MIDs as duplicates. Skip blending Ethoca and CDRN when Midigator alone owns the stack.
Related: Chargebacks, Kount duplicate-alert, Forter duplicate-alert, alert-coverage.
Procedure
- Type duplicate alerts and alerts.
- Read MG dup %.
- Dedupe intake when MG dup % is material.
Failure modes
- Inventing MG dup %.
- Dumping a Kount or Forter duplicate-alert file into Midigator fields.
- Folding Midigator 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
- MG dup %
- Duplicate alerts ÷ Alerts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Kount duplicate-alert share?
- Other vendor intake. [Kount duplicate-alert](/manuals/kount-duplicate-alert-share) stays on Kount rows. Here the numerator and denominator are Midigator only.
- Is this Midigator alert-coverage gap?
- Enrollment seats vs live seats. [Alert-coverage gap](/manuals/midigator-alert-coverage-gap) answers cover. This page answers how often the rail stacks the same case.
- What MG dup % should I invent?
- None. Export stacked alerts and total alerts from one Midigator rail window.