# First-touch vs last-touch attribution

> Compare first-touch, last-touch, and session-touch attribution models for SaaS revenue reporting.

Canonical page: [https://attribiq.com/guides/first-touch-vs-last-touch-attribution](https://attribiq.com/guides/first-touch-vs-last-touch-attribution)

Category: Revenue Attribution

Last updated: 2026-05-20

Topics: first touch, last touch, attribution models, saas analytics

## Summary

First-touch shows what introduced paid accounts. Last-touch shows what happened closest to conversion. Session-touch shows the context of the payment session. Use all three at first because each answers a different business question.

## What this guide covers

- Know what each simple attribution model means
- Choose the right model for acquisition, conversion, and checkout questions
- Avoid treating one model as universal truth
- Explain revenue attribution reports to non-analytics teammates

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.

| Model | Credit |
| --- | --- |
| First-touch | Search and the original blog landing page |
| Last-touch | Direct or the latest known non-direct source, depending on your rule |
| Session-touch | Friday's checkout session |

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](https://attribiq.com/guides/direct-traffic-revenue-attribution) to understand why direct often appears in last-touch reports. Then connect payments with [Stripe revenue attribution](https://attribiq.com/guides/stripe-revenue-attribution).

## Frequently asked questions

### Which model is most accurate?

No single model is universally most accurate. Each model is a rule for assigning credit. The useful choice depends on the question you are asking.

### Should direct traffic get last-touch credit?

Sometimes, but direct should not always erase a known campaign. Many teams keep direct as session-touch context while preserving known campaign credit for first-touch reports.

### When should I use multi-touch attribution?

Use simple models first. Consider multi-touch only when you have enough volume, multiple paid channels, and a real decision that simple models cannot support.

### Can these models handle renewals?

Yes. A renewal can inherit original first-touch and last-touch acquisition context, while also showing the current renewal event separately.