TrackRev
Blog
10 min read
Attribution models

Last-Touch Attribution Explained: Why It’s the Default

Last-touch attribution is the default for 64% of TrackRev workspaces. Why it wins, a worked $500 example, and the blind spots that quietly misprice channels.

Muzahid Maruf — Founder of TrackRev.io

Muzahid Maruf, Founder

LinkedIn

On this page
  1. 01Why this matters for your revenue
  2. 02What last-touch attribution is
  3. 03A worked example: a $500 sale
  4. 04The strengths and the blind spots
  5. 05Who should use last-touch
  6. 06Last-touch and TrackRev
  7. 07When NOT to use TrackRev

Explore with AI

Opens this article inside the chosen assistant with a ready-made prompt.

Last-touch attribution is the default for 64% of TrackRev workspaces (TrackRev platform data, Q2 2026), and it credits 100% of a sale to the final touch before payment — so in the worked $500 example below, the closing paid-search click takes all $500 and the three touches that built up to it take nothing.

Last-touch attribution is the model that assigns the entire value of a conversion to the last touchpoint the buyer interacted with before paying. It is the most widely used model for good reasons: it is simple, unambiguous, and it needs no assumptions about how earlier touches contributed.

It is also structurally blind to everything that created the demand the final click merely captured.

This guide explains why last-touch became the default, works the maths on a real journey, and is honest about the blind spots that quietly misprice your awareness channels — because the whole point of picking a model is to work out which channel actually funds your growth.

Key Takeaways

  • Last-touch attribution credits the final touch before purchase with 100% of the revenue — in the worked $500 example, the closing paid-search click takes all $500 and the three earlier touches take nothing.
  • It is the default for 64% of TrackRev workspaces because it is simple, needs no modelling assumptions, produces one unarguable number per sale, and is accurate for short, high-intent purchases.
  • Its blind spot is structural: it over-credits demand harvesters like retargeting and branded search and zeroes out the awareness channels that created the demand, which risks cutting channels that actually fill the funnel.
  • Keep last-touch as a default below roughly $10k MRR and for short cycles; once journeys span several channels or cycles pass a month, run it beside first-touch and linear so demand creators show up.
  • TrackRev runs last-touch by default and computes first-touch and linear from the same stored click log, so cross-checking a channel before cutting it is a dropdown, not a re-instrumentation.

The one-line version

Last-touch credits the final channel before purchase with 100% of the revenue. It is the default because it is simple and needs no assumptions — but it systematically over-credits closers like retargeting and branded search and zeroes out the awareness channels that started the journey.

Why this matters for your revenue

Because last-touch is the default almost everywhere, its biases are baked into most teams’ budget decisions without anyone choosing them.

The model credits whatever channel got the last click, which in practice is disproportionately retargeting, branded search, and direct — the channels that harvest demand other channels created.

Optimise on last-touch alone and budget flows toward those harvesters, while the awareness channels that fill the funnel show weak numbers and get cut.

The cost is a predictable misallocation. Consider a podcast sponsorship that “never closes”: listeners rarely click straight from an episode to checkout, so under last-touch the channel shows almost no revenue and looks like a candidate to cut.

What last-touch cannot see is that the podcast was the first touch for a large share of high-value buyers who converted weeks later through search. Kill it and pipeline dries up two quarters on.

This is not a discipline problem or a creative problem — it is a measurement problem, and you cannot reallocate budget toward channels your model cannot see.

Last-touch is a fine default precisely because it is safe and simple, but relying on it alone hides a whole class of channel. For the wider picture, see the SaaS attribution benchmarks.

What last-touch attribution is

Last-touch attribution assigns 100% of a conversion’s credit — and its revenue — to the final touchpoint before the purchase, giving every earlier touch nothing. If a buyer discovered you through organic search, returned via newsletter and an affiliate link, and finally clicked a paid-search ad before paying, last-touch credits the paid-search click with the entire sale and the first three touches with zero.

Its logic is that the last click is the one that “worked” — the touch that converted an interested buyer into a paying one. Sometimes that is exactly right, when the decision and the click are nearly simultaneous.

Often it is wrong, because the last click merely collected a decision that earlier channels had already made. The model’s appeal is that it never has to decide which — it always credits the closer.

A worked example: a $500 sale

The same customer and journey used throughout this series: a $500 annual plan bought after four touches over 28 days. We apportion it under last-touch, then compare with the other models.

The four-touch journey

Organic search brings the buyer in on day 1, a newsletter keeps them engaged on day 9, an affiliate review link pushes them along on day 21, and a paid-search ad brings them back to buy on day 28.

The paid-search click is the last touch inside the window, so it is where last-touch places all the credit.

TouchpointChannelDayRole in the journey
1Organic search (blog post)Day 1Discovery — first contact
2NewsletterDay 9Nurture — stays in touch
3Affiliate referral linkDay 21Consideration — third-party push
4Paid searchDay 28Closing click — returns and buys

Illustrative four-touch journey for a representative $500 annual-plan sale, used consistently across the model examples.

How last-touch credits the $500

Last-touch is the mirror of first-touch: the final touch takes everything. Paid search is credited the full $500; organic search, newsletter, and affiliate are each credited $0.

The organic result that discovered the customer and the affiliate link that pushed them toward the decision both score nothing, despite doing the work paid search finished.

The maths, step by step

As with first-touch there is no split to calculate. Identify the latest touch inside the attribution window — paid search on day 28 — and assign it 100% of the $500; assign every earlier touch 0%.

The whole model is “find the last touch in the window, give it the sale”. Its unambiguity is the reason finance teams like it: there is no apportionment to dispute, only a single crowned channel.

The same sale under all five models

Set last-touch beside the alternatives on the identical $500 journey. Last-touch and first-touch are opposites; the multi-touch models distribute the sale rather than crowning one channel.

TouchpointDayFirst-touchLast-touchLinearTime-decayPosition-based
Organic searchDay 1$500$0$125~$20$200
NewsletterDay 9$0$0$125~$45$50
Affiliate linkDay 21$0$0$125~$145$50
Paid searchDay 28$0$500$125~$290$200
Total$500$500$500$500$500

Illustrative apportionment of one $500 sale under five models. Time-decay figures use a 7-day half-life and are rounded; position-based uses a 40/20/40 split.

Reading the comparison

Last-touch and time-decay agree on the winner — both credit paid search most — but time-decay still hands roughly $210 to the earlier touches, while last-touch hands them zero.

That difference is the whole argument about last-touch: it is not that it picks the wrong closer, it is that it pretends the closer did all the work.

The more multi-touch your journeys, the more revenue last-touch quietly transfers from creators to closers.

The strengths and the blind spots

Last-touch earns its default status and pays for it with a specific, predictable bias.

StrengthsBlind spots
Simple and unambiguous — no apportionment to argueZeroes out every awareness and nurture touch
Needs no assumptions about earlier touchesOver-credits retargeting, branded search, and direct
Accurate for short, single-decision purchasesMisleads on long, multi-touch SaaS journeys
A safe, defensible default finance acceptsHides demand-creation channels, risking bad cuts

The last-touch trade-off: safety and simplicity bought by crediting the closer for the whole journey.

How much last-touch moves between channels

On the worked $500 journey, last-touch hands the closing paid-search click all $500 and gives the discovery, nurture, and consideration touches $0. A recency-weighted model would still award those three earlier touches roughly $210 between them. That ~$210 on a single sale is the credit last-touch silently transfers from demand creators to the closer — multiply it across a quarter of sales to see the budget distortion it hides.

Why last-touch became the default

Last-touch is the default for the same reasons 64% of TrackRev workspaces run it: it requires no modelling assumptions, it produces one number per sale that no one can argue about, and it is correct often enough — for short, high-intent, single-channel purchases the last click really did drive the sale.

It is also the model every ad platform reports by default, so it is the path of least resistance.

For a team that needs a defensible starting point and does not yet run many channels, that safety is a genuine virtue, not a compromise.

Where last-touch misleads

The moment buyers touch more than one channel before paying, last-touch stops describing reality and starts hiding it.

It credits the closer and erases the creators, so podcasts, YouTube, content, and community — the channels that generate demand but rarely get the final click — look worthless.

In long B2B cycles the distortion is severe: the webinar that generated the demo and the email that closed it both mattered, but last-touch credits only the email.

Budget then flows to demand-harvesting channels and away from demand-creating ones, and the funnel slowly starves.

Who should use last-touch

Last-touch is the right default for more teams than any other model — but “default” is not “only”. Match it to your stage and funnel.

A good fit for short cycles and early stage

Keep last-touch when purchases are high-intent and short-cycle — a consumer signing up for a low-priced app after one ad, a high-intent search where the buyer already knew what they wanted — because the final click really did drive the sale.

It is also the right choice very early, below roughly $10k MRR, where you lack the conversion volume for multi-touch models to produce meaningful splits and you need one clear number per channel to find the one or two channels that work.

A poor fit for multi-channel and long cycles

Stop relying on last-touch alone once journeys genuinely span several channels or your sales cycle stretches past a month.

At that point it systematically underprices your awareness channels, and the fix is to run it beside first-touch and linear so the creators show up somewhere.

For long B2B cycles specifically, see attribution for long B2B sales cycles; for the full model comparison, the models compared.

Last-touch and TrackRev

Last-touch is TrackRev’s default model — the one 64% of workspaces run — and it is computed from the same stored click log as first-touch and linear.

How to run last-touch in TrackRev

Last-touch works out of the box: connect billing, add the pixel, and the dashboard attributes revenue to the final touch inside your window.

Because the raw journey is stored, you are never locked into it — switching to first-touch or linear to sanity-check a channel is a dropdown.

See how to set your attribution window, which matters most under last-touch because the window defines what counts as the “last” touch.

Set the window deliberately

Under last-touch the attribution window is doing quiet but important work: it decides how far back a payment looks to find the final qualifying touch.

Across TrackRev workspaces the median window is 27 days and 30-day windows are most common at 41% (TrackRev platform data, Q2 2026).

Set it too short and a slow SaaS evaluation loses its closing touch to “direct”; set it too long and you credit stale clicks.

Cross-check against first-touch

The habit that saves you from last-touch’s blind spot is cheap in TrackRev: periodically flip to first-touch and note which channels leap up. Those are your demand creators, the ones last-touch was zeroing out.

You do not have to abandon last-touch as your default to benefit — you just have to look at the other view before you cut a channel.

When NOT to use TrackRev

If your billing is not on Stripe, Paddle, Polar, or Lemon Squeezy, the revenue join does not apply.

If you want algorithmic or data-driven attribution with a large training set, TrackRev deliberately ships the three auditable models — first-touch, last-touch, and linear — because they are explainable and hold up at SaaS data volumes, and it does not pretend to offer a black-box model it cannot audit.

If you sell physical goods or run a CRM-led enterprise motion, a specialist tool fits better. TrackRev is for SaaS teams that want revenue tied to channels across models they can defend.

The stack maths is the consolidation case: Bitly Growth (~$35/mo) plus Rewardful Starter (~$49/mo) is $84+/month for two tools with two definitions of a sale, while TrackRev is $39/mo for all three products on one.

Found this useful? Share it.

PostLinkedIn

Frequently asked questions

Muzahid Maruf — Founder of TrackRev.io

Written by

Muzahid Maruf, Founder, TrackRev.io & Contant.io

Muzahid Maruf is the founder of TrackRev.io and Contant.io. He writes about marketing attribution, link tracking, and revenue analytics for SaaS teams.

Writes about Marketing attribution · Link tracking · Revenue analytics · SaaS growth

Keep reading

Related articles from the TrackRev blog.

Stop guessing where your revenue comes from.

Set up TrackRev in 5 minutes. Free tier covers 1,000 events / month — no card needed.

Last-Touch Attribution Explained: Why It’s the Default · TrackRev