Multi-touch attribution: what it is and how to build it in 5 steps

Multi-touch attribution splits a sale's revenue across every click that led to it. See how 4 rules split credit, what they miss and how to build it in 5 steps.

Muzahid Maruf — Founder of TrackRev.io

Muzahid MarufUpdated

Revenue attribution · 11 min read
On this page
  1. 01How does multi-touch attribution work?
  2. 02Which multi-touch attribution model should you use?
  3. 03What are the benefits of multi-touch attribution?
  4. 04What can multi-touch attribution not tell you?
  5. 05How to set up multi-touch attribution in 5 steps
  6. 06How does multi-touch attribution work without cookies?
  7. 07How do you test the pipeline with a known journey?
  8. 08How does multi-touch attribution work in TrackRev?

Explore with AI

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

Multi-touch attribution is the practice of dividing the revenue from one sale among every recorded touchpoint before it, where single-touch rules give the whole amount to the first or last click.

A SaaS buyer who clicks a podcast link on day 1, a LinkedIn post on day 9, a newsletter on day 16 and an affiliate's review link on day 24, then pays $1,200 for an annual plan on day 28, produces 4 credits that add back up to $1,200.

Setting it up takes 5 steps in a fixed order: capture each click on your own server, give the visitor an ID, link it to a person at signup, store every touch as its own row, and join the payment.

Pick the credit rule last, since any rule can be read from the same stored touches.

Key takeaways

  • Multi-touch attribution divides one sale's revenue across every recorded touch, and the shares add back up to the sale. A $1,200 plan with 4 touches gives each $300 under linear and $480, $120, $120 and $480 under U-shaped.
  • The build is 5 steps in a fixed order: server-side click capture, a visitor ID, an identity link at signup, one stored row per touch, and a payment join. The credit rule comes last.
  • Safari deletes cookies created in JavaScript after 7 days without a visit to the site, so set the visitor ID from your own server and carry it into checkout.
  • TrackRev offers last touch (the default), first touch and linear on paid plans from $29 a month, with a lookback window of 1 to 365 days that defaults to 30.

How does multi-touch attribution work?

Multi-touch attribution works from 2 inputs: one buyer's touches in order, with timestamps, and a conversion with a dollar value. For a subscription, use the first paid charge as the conversion, since a free signup has no revenue to divide.

Google Analytics Help defines an attribution model as "a rule, a set of rules, or a data-driven algorithm" for assigning credit along the path. The shares sum to the charge, so the report ties back to what your processor collected.

Rules differ only in the weights: first touch gives 100% to the first row, last touch 100% to the last, linear 25% to each of 4 touches, and U-shaped 40%, 10%, 10% and 40%.

One $1,200 sale under 4 rules

TouchDayFirst touchLast touchLinearU-shaped
Podcast link1$1,200$0$300$480
LinkedIn post9$0$0$300$120
Newsletter16$0$0$300$120
Affiliate review link24$0$1,200$300$480
Total28$1,200$1,200$1,200$1,200

Illustrative journey for an annual plan paid on day 28. U-shaped gives 40% to each end and shares the other 20% between the 2 middle touches.

First touch and last touch put $1,200 on 1 row, so the podcast is the whole story under one rule and worthless under the other. Linear gives every row $300.

How credit thins from 3 to 10 touches

The same $1,200 sale spread over 3 to 10 touches. Linear slices shrink in proportion, and U-shaped middle slices shrink faster because the 2 ends keep $480 each.

TouchesLinear, each touchU-shaped, each endU-shaped, each middle touch
3$400$480$240
4$300$480$120
5$240$480$80
6$200$480$60
8$150$480$40
10$120$480$30

Which multi-touch attribution model should you use?

A multi-touch rule is a weighting scheme, and 6 rules are in common use, as the table shows. Pick the rule by the decision it feeds.

First touch shows where buyers first met you, last touch shows what closed, and linear gives every channel that appeared a share. According to HubSpot's documentation, U-shaped gives 40% to the first touch, 40% to lead conversion and 20% between.

RuleCredit splitWhere it is offered
First touch100% to the first touchTrackRev, HubSpot
Last touch100% to the last touchTrackRev, HubSpot, Google Analytics 4 (as last click)
LinearEqual shares across all touchesTrackRev, HubSpot
U-shaped40% first, 40% lead conversion, 20% betweenHubSpot
W-shaped30% each to first, contact-creating and deal-creating, 10% betweenHubSpot
Data-drivenEstimated from your conversion pathsGoogle Analytics 4

As documented by HubSpot and Google, October 2026. Google removed first click, linear, time decay and position-based from Google Analytics 4 in November 2023.

At 20 paid conversions a month, 1 customer is 5% of the month's revenue, so position weights are fitted to a handful of journeys.

I would read first touch and last touch side by side first, then add linear once most journeys have 3 or more touches. The attribution models comparison covers time decay and data-driven credit.

What are the benefits of multi-touch attribution?

Journey openers become visible. In the $1,200 example the podcast earns $0 under last touch, so a team reading only last touch would cut it, while first touch gives it $1,200 and linear $300.

Two rules side by side sort channels: high under first touch and low under last touch marks an opener, and the reverse marks a closer.

The model also matches how long SaaS buyers take. In our Q2 2026 attribution benchmarks, the median time from first tracked click to first paid charge is 6.3 days across 4,217 workspaces.

The 75th percentile is 21.0 days and the 90th is 48.2, so 1 buyer in 10 takes longer than about 7 weeks, with room for many touches a last-click report never sees.

Commission rules get an explicit basis. On the sale above, an affiliate program paying 20% of credited revenue owes these amounts, so the rule belongs in the partner terms:

RuleAffiliate's creditPayout at 20%
First touch$0$0
Linear$300$60
U-shaped$480$96
Last touch$1,200$240

What can multi-touch attribution not tell you?

A multi-touch report is a model of credit, not an experiment. Credit follows a fixed rule, so it can't show whether a channel caused a sale.

Google Ads describes Conversion Lift as an incrementality experiment: 1 audience sees your ads, a control group does not, and the gap in conversions is the lift the ads caused.

A multi-touch report has no control group, so test large budget moves with a holdout.

The report also sees only recorded touches. A private recommendation, a conference conversation or an unlinked podcast mention leaves nothing to credit and lands under Direct, even when the podcast started the buyer's search.

Asking buyers directly catches some, and the self-reported versus tracked attribution guide covers weighing the answers.

How to set up multi-touch attribution in 5 steps

1. How do you capture every click on your own server?

Server-side click capture is a 302 redirect on a domain you own that writes the click before forwarding the visitor. Send every link you control through the redirect: newsletters, ads, partner links, QR codes.

A blocked script can't lose the click, because the write happens first. According to WebKit, script-written cookies are deleted after 7 days without a visit, so a server-side row is the one copy that cannot expire in 2026.

Store the visitor ID, link, channel, timestamp, user agent and a bot flag.

The first click mints the visitor ID, a random UUID set as a 365-day cookie in the redirect's response and appended to the destination URL as a parameter such as _vid.

A pixel on your site reads it, so the click and later page views share 1 identity. Accept only values shaped like your own IDs, or a crafted link can plant someone else's.

TrackRev pixel tag
<script async src="https://app.trackrev.io/p.js" data-id="YOUR_WORKSPACE_ID"></script>

An identity link is the stored match between a visitor ID and an email. Anonymous clicks become usable once the visitor ID sits beside something a payment carries, usually an email.

With the TrackRev pixel the match is 1 call on the signup success page, after the pixel's trk:ready event fires.

Every earlier click from that browser then belongs to a named account, whether the click came from a podcast link on day 1 or a newsletter on day 16.

Run on the signup success page
window.trk.identify("buyer@example.com");

3. Why keep every touch as its own row?

A touch row is one stored click with a timestamp, a channel and a bot flag. Store 1 row per click and never update one.

A source field on the user, rewritten at each visit, is last-touch data under a multi-touch label. A journey of 10 touches is 10 rows, and the credit rule reads all 10 later.

Flag bot clicks when you write them and filter on the flag, or link-preview crawlers and email security scanners collect credit as if they were buyers.

4. How do you join the payment to the visitor?

A payment join is the step that attaches a visitor ID to a charge. A log tied to signups ranks channels by signups, and joining the payment ranks them by revenue.

Carry the visitor ID into checkout, and fall back to the customer's email. Each processor has its own field, and the table lists 5 of them.

CheckoutField that carries the IDWhat the docs say
Stripe Payment Linksclient_reference_id URL parameterUp to 200 characters; sent in the checkout.session.completed webhook
Stripe Checkout Sessionsclient_reference_id fieldA unique string, such as a customer ID or cart ID, for reconciling the session
Paddle BillingcustomData in Paddle.Checkout.open()Copied to the subscription and its later transactions
Lemon Squeezycheckout[custom] URL parametersReturned in the webhook's meta.custom_data
Polarreference_id query parameterAttached to the checkout session's metadata

Fields as each processor documents them, October 2026.

Decide here how renewals inherit credit and make refunds reverse their credit. For example, a $1,200 charge with a client_reference_id in Stripe returns the ID in the checkout.session.completed webhook, so all 4 touches can be credited.

The Stripe Payment Links attribution guide shows the wiring.

5. Which credit rule and lookback window should you choose?

The lookback window is the number of days a touch stays eligible for credit. The window decides which touches count, because a click older than it earns nothing.

Set the window past the 90th percentile of your own days from first tracked click to first charge.

In our Q2 2026 benchmarks across 4,217 workspaces, the 75th percentile is 21.0 days and the 90th is 48.2, so a 30-day window misses between 1 buyer in 10 and 1 in 4.

Google Analytics 4 attribution settings default to 90 days for most key events and offer 30, 60 or 90.

WindowWorkspaces using itBuyers who pay inside it
7 days22%Just over 50% (median is 6.3 days)
14 days18%50% to 75% (75th percentile is 21.0 days)
30 days41%75% to 90% (90th percentile is 48.2 days)
60 days12%90% to 95% (95th percentile is 73.5 days)
90 days or longer7%Over 95%

From TrackRev's Q2 2026 benchmarks across 4,217 workspaces, where the median window is 27 days. Percentiles are bounded by each workspace's own window, so the real tail is longer.

How does multi-touch attribution work without cookies?

Cookieless multi-touch attribution is built on a click log that needs no cookie. Safari's Intelligent Tracking Prevention is the best-documented source of cookie loss. WebKit's tracking prevention policy includes 3 caps that touch attribution.

What is cappedCapTrigger
JavaScript cookies, LocalStorage and IndexedDBDeleted after 7 daysNo interaction with the site in that time
JavaScript cookies on a landing pageExpire after 24 hoursITP detects link decoration, such as click IDs in the landing URL's parameters
Cookies in third-party HTTP responsesExpire after 7 daysThe request uses CNAME or IP address cloaking

Intelligent Tracking Prevention as WebKit documents it, October 2026.

The click log needs no cookie, because the redirect records the click on your server before the destination loads. A cookie only links that click to a later purchase, and 3 carriers outlast the caps:

  • A cookie your own server sets in an HTTP response. The caps name script-written cookies and cloaked third-party requests, and a redirect on your domain is neither.
  • The ID in the URL, appended by the redirect, read by the pixel and carried into the payment by the checkout field from step 4. Apple's Link Tracking Protection strips some known parameters, and the iOS 17 link tracking guide covers which.
  • The buyer's email or login, which no browser setting clears.

A first-party ID is still a persistent identifier, so for EU or UK visitors ask a legal adviser whether the ID needs consent. The TrackRev pixel waits for window.trk.grantConsent() when its script tag carries data-requires-consent="true".

Probabilistic matching on IP address and browser fingerprints breaks on shared office networks and mobile data, so I would not pay commissions on it. The affiliate compliance guide covers FTC and GDPR rules for partner programs.

How do you track buyers who switch devices?

Cross-device matching is a join on a shared identity, never on a cookie. A cookie lives in 1 browser, so a phone click and a desktop payment look like 2 strangers.

Only a shared identity joins them: the email from a signup form, or a login. Store the visitor ID with the email at signup, and credit that ID's clicks when a charge arrives with the same email.

The join fails when the signup email and the card email differ. Key on your own user ID instead, passed as client_reference_id when you create the Stripe Checkout Session, or collect the work email before the upgrade.

TrackRev's email fallback reads only the most recently active visitor with that email, so 2 identified journeys, one on a phone and one on a laptop, are not merged.

How do you test the pipeline with a known journey?

A known-journey test is a scripted purchase whose credits you can predict. Click 2 tagged links in 1 browser 1 day apart, sign up, then pay a small charge and refund it, once in Safari and once in Chrome.

Expect 2 touches in both browsers, and a missing touch in Safari points at the cookie cap. Each symptom points at 1 step:

  • Safari loses early clicks and Chrome keeps them: the ID is written only by JavaScript, so Safari's 7-day cap applies.
  • No earlier clicks on the signup: identify ran before the pixel loaded, or never ran.
  • Only the last click appears: a source field is overwritten at each visit.
  • A charge with no credit: checkout carried no ID and the card email differs from the signup email.

How does multi-touch attribution work in TrackRev?

TrackRev is SaaS affiliate software with link tracking and revenue attribution built in, and it covers the 5 steps. We built tracked links to redirect on your domain and log each click server-side

In our rules, last touch is the default, with first touch and linear beside it and a lookback window of 1 to 365 days that defaults to 30.

A rule applies as each charge arrives, so changing the rule affects later charges only. Renewals reuse the first charge's split, and refunds drop out of channel revenue.

A visit that skips your tracked links counts as a page view, not a touch.

PlanPriceWhat it covers here
Free$0Link tracking for 50 links and 1,000 events a month; no revenue figures
Indie$29 a monthRevenue by channel, 3 credit rules, 1 workspace
Growth$299 a yearThe same, across up to 10 workspaces and 10 tracked domains

Plans from the TrackRev pricing page, October 2026.

The revenue attribution page shows the channel report. The trade-off is rule choice: pick another tool for position-based, time-decay or data-driven credit, or when the decisive touches happen in meetings and email threads.

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 founded TrackRev.io, SaaS affiliate software with no limit on tracked revenue, and Contant.io. He writes about affiliate programs.

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

Run your affiliate program without a revenue cap.

Affiliate software for indie hackers and small SaaS teams: $29 a month flat, 0% fees, link tracking and revenue attribution built in. Free to start, no card.