Attribution models for lifecycle: which one to defend in which room

Last-touch: credit to the most recent touchpoint before conversion. Simple. Easy to report. Almost always wrong for lifecycle. An email clicked two minutes before purchase gets everything. The onboarding sequence from three months ago gets nothing.

First-touch: credit to the first interaction. Useful for acquisition attribution — which channel brought this user in — and largely beside the point for lifecycle.

Multi-touch: credit is distributed across touchpoints. Linear gives equal weight. Time-decay weights recent touches more. Position-based weights first and last. More accurate than last-touch and still built on arbitrary weighting choices nobody will defend when pressed.

Incrementality: compare the revenue of users who received messages to a matched group who didn't. Holdouts. Answers the causal question — would this conversion have happened anyway? — which is the only question leadership actually cares about even when they don't know to ask it that way. The holdout guide covers the design.

Different questions, different tools. The instinct to pick one model and apply it everywhere is the source of most bad attribution conversations — it forces one method to answer questions it wasn't built for, and then people argue about the method when they should be arguing about the question.

Every attribution conversation runs on two layers. The epistemological one: which model is most accurate? The political one: whose team gets credit? Lifecycle marketing usually loses the political layer under last-touch because most conversions have an intervening paid or organic touchpoint that steals the last click. Multi-touch gives lifecycle some credit. Incrementality gives it the credit it actually deserves. Which is why incrementality conversations are the slowest to get organisational buy-in.

The operator move: publish in whichever model fairly represents the program's contribution, and have a second number ready for when leadership challenges the first. Last-touch for operational reports. Incrementality for budget conversations. The Attribution Audit skill covers how to structure the dual-model reporting without it looking like attribution-shopping — because the second it looks like that, you've lost the room.

Multi-touch sounds like the adult answer — spread the credit, acknowledge the journey, move on. It introduces its own problem: arbitrary weighting. Linear gives equal credit to all touches, but is the sixteenth email really as valuable as the first? Time-decay privileges recent touches, which means channels that touch near the conversion (often paid, not lifecycle) get more credit purely for timing.

The cleanest multi-touch approach is to weight based on holdout-measured incrementality per touch type. If a holdout tells you email produces 40% of tested revenue, ads 35%, content 25%, then the weighting is evidence-based rather than chosen by vibes. Most programs don't do this because it requires running holdouts across multiple channels at once. Which is why most multi-touch numbers, however official they look, are guesses in a spreadsheet.

Run attribution in the operational dashboards — daily, weekly, monthly. It tells you where conversions happened and which touchpoints were in the path. Useful for spotting broken programs, evaluating creative, and making tactical decisions. Is last-touch wrong? For lifecycle ROI specifically, yes — it systematically under-credits lifecycle touches. For operational reporting, it's fine. Don't use it for budget conversations and you'll avoid most of the trouble.

Run incrementality for budget and strategic questions — quarterly at minimum, annually for smaller programs. It tells you whether the program is worth running and how much revenue it actually produces. Useful for allocation, kill calls, and defending lifecycle marketing to finance. A holdout for budget season and a second for mid-year review is the cadence that keeps the financial case current.

The mistake is using attribution for budget conversations. Attribution-based lifecycle revenue numbers are almost always optimistic — they count conversions that would have happened anyway. When leadership eventually notices the gap between attribution-claimed revenue and bottom-line revenue, the credibility hit damages the whole program. Better to under-promise with incrementality numbers and deliver consistently than the other way around.

Can you use both? Yes, and most mature programs do. Attribution in weekly dashboards, incrementality in the quarterly review. The two answer different questions and complement each other. The risk is attribution numbers leaking into budget conversations; keep the separation deliberate and name it out loud. The retention economics guide covers how to frame incrementality numbers in CFO conversations specifically.