First-touch vs last-touch attribution

Attribution models are rules for assigning revenue credit.

For most SaaS builders, the first useful set is first-touch, last-touch, and session-touch. They are easy to explain, quick to implement, and good enough to reveal whether acquisition and conversion work are pointing in the right direction.

First-touch attribution

First-touch gives credit to the earliest known source or landing page for a visitor.

Use it to answer:

• Which channels introduce customers who eventually pay?
• Which blog posts or landing pages start good journeys?
• Which campaigns create long-term customer value?

First-touch is useful for content, SEO, referrals, partnerships, and community traffic where the first visit may happen well before checkout.

Last-touch attribution

Last-touch gives credit to the latest known source before conversion.

Use it to answer:

• What pushed the customer over the line?
• Which campaigns or pages close the sale?
• Which retargeting, launch, or pricing paths create paid conversion?

Last-touch can over-credit direct traffic, branded search, or checkout-adjacent pages if you read it without context.

Session-touch attribution

Session-touch gives credit to the active session where the revenue event happened.

Use it to answer:

• What was happening when the customer paid?
• Did the payment happen after a direct return, a campaign click, or an API reference visit?
• Which pages appeared in the checkout session?

Session-touch is practical for debugging the payment journey. It is not always the best acquisition model.

A simple example

A visitor finds your blog from search on Monday. On Wednesday they read a comparison page from a newsletter link. On Friday they type your domain, visit pricing, and subscribe.

All three can be true. The mistake is asking one report to answer every question.

How to use the models

Start every revenue review with the question:

• Acquisition question: use first-touch.
• Conversion question: use last-touch.
• Checkout debugging question: use session-touch.
• Retention quality question: compare renewal, refund, and churn by original source.

This keeps the conversation clear. It also prevents teams from changing attribution rules every time a favored channel looks weaker than expected.

Next steps

Read direct traffic revenue attribution to understand why direct often appears in last-touch reports. Then connect payments with Stripe revenue attribution.