State the measurement boundary
Define the outcome, entity, eligible touchpoints, lookback window, and identity rules. Decide how anonymous visits, offline conversations, multiple contacts, and missing data are represented. Preserve an unknown category instead of inventing a complete path.Build and compare models
- Check the records you are counting. Deduplicate conversions or opportunities and use a consistent value basis. Separate created pipeline, won revenue, and collected cash.
- Decide which interactions count. Decide which interactions count and how repeated events are collapsed. A thousand page events should not automatically earn a thousand times the credit of a meaningful conversation.
- Apply transparent rules first. First-touch assigns eligible credit to the earliest recorded touch; last-touch to the latest; a custom linear model divides it across eligible touches. These are analytical examples, not a claim that every platform currently offers each model.
- Reconcile totals. Within one model and outcome ledger, allocated value plus explicitly unallocated value should equal the included outcome value. Do not add platform totals when several systems claim the same conversion.
- See whether changing the rule changes your conclusion. Change the model or lookback window and inspect which conclusions move. Keep data-driven platform models labeled with their scope and limitations.
- Use other evidence for budget decisions. Combine recorded paths with buyer-reported discovery, qualitative context, and well-designed incrementality experiments where feasible.
Worked example
A hypothetical $12,000 won deal has three eligible recorded touches: a newsletter, a webinar, and a search ad. A simple custom linear allocation assigns $4,000 to each; first-touch assigns $12,000 to the newsletter; last-touch assigns $12,000 to the ad. The three reports describe the same deal. Adding them would falsely create $36,000. If an untracked peer recommendation drove the buyer’s interest, none of those click-based allocations reveals its contribution. Record the buyer’s answer separately rather than rewriting observed history to manufacture agreement.Model specification
Read the disagreement
Large differences between models can be useful evidence about the recorded journey and its gaps. Investigate them before choosing the model that flatters a preferred channel. Keep an explicit distinction between attributed, influenced, and experimentally estimated incremental outcomes.Try it with your own work
Take one won deal and compare its recorded touchpoints with the buyer’s account of how they found you. Note the gaps before deciding what the channel report means for your budget.Sources and scope
- Google Analytics: attribution defines model-based credit allocation and current platform options; the three-touch arithmetic is a custom illustrative example.
What to read next
Measurement model · Experimentation · Pipeline model Chapter guide · All playbooksCopyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms. Canonical source: github.com/weilun88313/B2B-Playbook