Placeholder values in required fields look like real data
Sentinels pass validation, then break blocking and blend into amounts.
SymptomA dedup or matching job slows sharply on one object, and its biggest block shares a placeholder name like "[not provided]".
Required fields get filled whether or not anyone knows the answer. An import that needs a last name writes "[not provided]", and an integration that needs an amount writes a template value.
Sentinel names wreck blocking. Dedup groups records by name before comparing pairs, so every record with the placeholder lands in one block, and pairs grow with its square.
Keeping sentinels out of the blocking keys makes the giant block go away, and intermediate rows fall by orders of magnitude.
Amounts are harder. A templated round number sits inside the real range, so no single value looks wrong. Only a cluster of identical amounts gives it away.
In a synthetic test set of 10,000 contacts, 1,000 of them carrying a placeholder name, blocking on name made 513,133 candidate pairs; excluding the placeholder left 13,633. The set shows the mechanism, not how common it is.
List the 20 most frequent values in each required name field and each amount field. Any placeholder string is a sentinel your matching and math will read as real. A round amount far more common than its neighbours is also a sentinel.
Passes ifThe 20 most frequent values in each required name or amount field hold no placeholder and no outlying round amount. Otherwise, your matching excludes those values.
Access needed:crm-read
- 01Keep a per-field list of known placeholders, such as "[not provided]". Read listed placeholders as null.
- 02Exclude placeholder values, like nulls, from dedup blocking keys.
- 03Review any value in a field's 20 most frequent that has no plausible reason to repeat.
- 04Flag round amounts that repeat far more often than nearby values. Keep flagged amounts out of averages until reviewed.