// METRICS · ATTRIBUTION OPS

Attribution Agents Need Source Locks Before They Rewrite Pipeline Credit

The dangerous growth agent is not the one that sends a bad email. It is the one that quietly changes which motion gets credit, then optimizes the company around a fake truth.

01 · FreezeLock original source before machines touch the deal.
02 · CompareSeparate agent-influenced from agent-created pipeline.
03 · ReceiptEvery credit move needs evidence, owner, timestamp.
04 · KillNo source lock, no attribution change.
// OPERATOR THESIS

Attribution is a control surface, not a dashboard.

Heads of Growth are about to let agents route leads, enrich accounts, revive pipeline, personalize pages, and recommend offers. That means machines will touch the evidence trail behind revenue.

If the same system can create activity and award itself credit, your growth model becomes self-congratulating machinery.

The source-lock rule

Original source is immutable unless a named operator approves a correction with evidence.

Agents may append influence. They may not overwrite origin.

// BEFORE / AFTER GRID

What breaks when attribution is writable.

Before source locks

  • Agent updates campaign source after touching the account.
  • Retargeting steals credit from founder-led demand.
  • Pipeline reports show lift without causal proof.
  • Budget moves toward the machine that edits the ledger.

After source locks

  • Origin stays fixed at first qualified capture.
  • Machine touches become influence events, not source rewrites.
  • Every attribution correction has a receipt.
  • Budget follows verified creation, not noisy activity.
WARNING: If your AI can edit attribution and optimize spend, it can manufacture its own performance review.
// SOURCE LOCK DECISION MATRIX

Use this matrix before agents touch pipeline credit.

Field
Agent can append
Agent can overwrite
Human gate
Original source
Never
No
Correction only
Influence event
Yes
Yes, own row
Sample audit
Campaign member
Yes
No, append state
Exception review
Pipeline credit
Recommendation
No
Named owner
// CONTROL-PLANE FLOW

The attribution control plane is simple.

STEP 01Capture origin
STEP 02Lock source
STEP 03Append influence
STEP 04Audit credit
STEP 05Move budget

This keeps machine labor useful without letting it become the judge of its own revenue impact.

Influence is not origin. Activity is not creation. Credit is not a model output.
// OPERATOR RECEIPT

What every credit change must carry.

A source lock does not slow growth. It makes the growth system legible enough to trust at speed.

Put the receipt in the same place operators review pipeline. If the evidence lives in a separate tool, it will not govern anything.

Minimum receipt

  • Old value and proposed value.
  • Evidence URL or event ID.
  • Agent name and tool scope.
  • Human approver for origin corrections.
  • Rollback path before reporting closes.
// FINAL DECISION RULE

No lock, no credit move.

Give agents room to find influence. Do not give them authority to rewrite origin. A Head of Growth who cannot defend source truth cannot defend budget, headcount, or strategy.

01 Lock original source at first qualified capture.
02 Store agent touches as influence rows.
03 Require receipts for every correction.
04 Review source-lock exceptions weekly.
05 Move budget only after locked-source lift is proven.
06 Kill any workflow that lets agents grade themselves.