FindingcurrentGTM data

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.

Check your setup read-only

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

If it fails: changes to make later (not part of the check)
  1. 01Keep a per-field list of known placeholders, such as "[not provided]". Read listed placeholders as null.
  2. 02Exclude placeholder values, like nulls, from dedup blocking keys.
  3. 03Review any value in a field's 20 most frequent that has no plausible reason to repeat.
  4. 04Flag round amounts that repeat far more often than nearby values. Keep flagged amounts out of averages until reviewed.
Applies ifYour dedupe or enrichment matches people or accounts by name, or your digests average CRM amounts, and imports or integrations fill required fields.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.