Fraud signal counts: what practitioners should actually compare

TL;DR: Fraud prevention vendors can report wildly different signal totals from the same underlying data, according to SEON, because interface fields, raw responses and database-layer metadata are often counted differently. The useful comparison is whether an input changes a real-time decision, not how large the number looks.

Editorial analysis by NHI Mgmt Group, based on content published by SEON: “The Only Signal Count That Matters in Fraud Prevention”.

Key questions

Q: How should fraud teams compare vendor signal counts without being misled?

A: Compare signal counts only after confirming the counting layer, the decision layer, and the action layer.

Q: Why do large fraud signal counts not always mean better detection?

A: Large counts often include exposed metadata, duplicate fields, or model inputs that never change a decision.

Q: What breaks when a fraud platform counts metadata as signals?

A: The comparison breaks because teams start judging platform depth by storage structure rather than control value.

Practitioner guidance

• Define the counting layer before procurement Require vendors to state whether the number reflects interface fields, raw response fields, or model inputs, and reject comparisons that mix layers.
• Map each claimed signal to a live action For every nominated signal, document whether it can approve, challenge, review, or stop a transaction in production decisioning.
• Separate metadata from intelligence Classify derived fields, descriptive attributes, and duplicated observations as supporting data unless they independently change a risk outcome.

Bottom line: Fraud signal totals are not comparable unless teams know which layer of data was counted and whether it affects live decisioning.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →