Library · Chargebacks · How to run this
Kount proxy hit is not device-fingerprint miss
Open one Kount decision cut. Put proxy hits over auth attempts. That is the proxy %.
Pair: Proxy-hit share on Chargebacks. Fingerprint twin: device-fingerprint miss rate. Sift twin: device-mismatch share.
What you type
Proxy hits — Auths where Kount flagged proxy / VPN / anonymizer in the cut.
Auth attempts — Auth attempts in that same Kount cut.
Proxy % = proxy hits ÷ auth attempts × 100. Fat proxy % means retune proxy rules — do not invent a proxy chip.
What not to do
Do not invent proxy %. Do not paste fingerprint misses into the proxy field. Do not treat Sift device mismatches as Kount proxy hits. Do not blend MIDs when one MID owns the skew.
Related: Chargebacks, device-fingerprint miss rate, velocity-override share, device-mismatch share.
Procedure
- Type proxy hits and auth attempts.
- Read proxy %.
- Retune proxy rules when proxy % is material.
Failure modes
- Inventing proxy %.
- Dumping fingerprint misses into the proxy field.
- Treating Sift device mismatches as Kount proxy hits.
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
- Proxy-hit share %
- Proxy hits ÷ auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this device-fingerprint miss rate?
- Sibling Kount grain. [Device-fingerprint miss rate](/manuals/kount-device-fingerprint-miss-rate) is fingerprint misses. Here you type proxy / anonymizer hits over auth attempts.
- Is this Sift device-mismatch share?
- Different vendor door. [Device-mismatch share](/manuals/sift-device-mismatch-share) is Sift device/account mismatch. This page is Kount proxy-hit share.
- What proxy % should I invent?
- None. Pull proxy hits and auth attempts from the same Kount cut.