FindingcurrentGTM data

A rep-entered profile URL beats a vendor's perfect-score match

Enrichment can return a different person even when name and company scores are perfect.

SymptomAn enriched contact shows another person's profile or title even though the CRM already held the right profile URL.

The standard enrichment flow trusts a vendor match whenever its name and company scores are high, treating a perfect score like proof.

A perfect score can still be a different person. Name and company are what the vendor matched on, so two people with one name at one company can both score perfectly.

Profile slugs also change when people rename their public profile URL, so an old URL in the CRM and a new one from the vendor can be the same person.

So let the human-entered URL win, because someone chose it on purpose. The vendor should fill only the gaps, with every disagreement logged and reviewed on a schedule. Adopt a new slug only when the vendor supplies a stable id that ties both URLs to the same person. Otherwise the CRM's URL stays.

In a synthetic test set of contacts with rep-entered profile URLs, letting a perfect-score vendor match win overwrote the correct URL on 5 of 10 namesake contacts; keeping the rep-entered URL overwrote none and logged 5 disagreements for review. The set shows the mechanism, not how common it is.

Check your setup read-only

List contacts that hold a profile URL both in a rep-entered CRM field and from enrichment. Count the contacts where the 2 URLs differ. Any difference where the enriched URL is the one in use is a possible wrong person.

Passes ifWherever the rep-entered and enriched profile URLs differ, the rep-entered one is the URL your jobs and agents read.

Access needed:crm-read

If it fails: changes to make later (not part of the check)
  1. 01Treat a profile URL entered in the CRM as the identity anchor. Let enrichment fill only empty fields.
  2. 02Log every case where the vendor's profile differs from the CRM's, instead of choosing silently. Review logged disagreements on a schedule.
  3. 03Adopt a new profile slug only when a stable id from the vendor ties both URLs to the same person. Otherwise, log the disagreement. Then keep the CRM's URL.
  4. 04Never let a match score override a human-entered identifier, however high the score.
Applies ifA job enriches titles or departures from a vendor, and a rep-entered CRM field holds profile URLs for some contacts.

← 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.