TechniquecurrentGTM data

Attribution captured at ingest goes stale when the CRM changes

CRMs re-parent records after you read them, so recheck each account link.

SymptomA call or email is missing from the right account's timeline after someone moved its CRM task or opened a new account for that company.

A typical ingest pipeline assigns each call or email an account when it arrives, and because the CRM keeps moving, that account can change after you read it.

Account attribution is a moving value on a record. Whenever a rep re-parents a task to the right account, or an account is opened weeks after the first calls with that company, the source changes while the copy taken at ingest stays put.

Derived data inherits the stale link. Facts extracted from a misattributed call stay scoped to the old account, so an agent answering about either account works from the wrong evidence.

Correcting the link once does not hold when a thread is processed again, because older messages can carry the old account back onto one that was already corrected.

In a synthetic test set of 500 emails, keeping the account stored at ingest left 218 emails and 444 facts on the wrong account; taking each message's account from its own task at read time left none. The set shows the mechanism, not how common it is.

Check your setup read-only

Take the 10 most recent calls or emails linked to an account more than 1 month ago. Compare each stored account with the account its source record names in the CRM today. Any mismatch means attribution is frozen at ingest.

Passes ifAll 10 sampled calls or emails still carry the account their CRM source record names today.

Access needed:context-readcrm-read

If it fails: changes to make later (not part of the check)
  1. 01Store the source record's id with every call, email and fact, not only the account it resolved to.
  2. 02Re-join every signal to its source's current account at least weekly. Rebuild anything scoped to the account.
  3. 03Move the call or email to the new account when its CRM task is re-parented. Invalidate the facts scoped to the old account.
  4. 04Take a thread's account from its current source records, never from a link stored on an earlier message.
Applies ifYour store keeps account ids on calls or emails, and the CRM's field history shows reps re-parenting contacts, tasks or accounts.

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