Revenue Attribution for SaaS: Which Traffic Sources Actually Make Money?

A channel can win on visits and still lose on business value. Revenue attribution exists to answer a more useful question than where traffic came from: which acquisition source created sessions that converted into money?

Start with a simple model

Early-stage teams often reach for multi-touch attribution too soon. A simpler session-acquisition model is easier to understand and usually good enough to decide whether a channel deserves more attention. Capture the source and campaign when the session starts; when a purchase event occurs, attach the revenue to that session.

• Session starts with source, medium and campaign context.
• Primary conversion marks the session as converted.
• Purchase event contains explicit revenue and currency.
• Source report aggregates sessions, conversions, conversion rate and revenue.

UTMs should win over ambiguous referrers

Referrers are useful but imperfect. Email clients, apps, redirects and payment providers can make them noisy. When a campaign deliberately provides UTM source, medium or campaign values, those explicit values should generally take priority over inferred source labels.

Revenue per session changes the channel conversation

Suppose one channel sends 1,000 sessions and another sends 100. The larger channel looks better until you learn it created two purchases while the smaller one created eight. Comparing conversion rate and revenue alongside sessions prevents traffic volume from becoming a vanity metric.

Know the limitation

Session attribution is not a perfect description of a long customer journey. A person may discover the product from one source and purchase later from another device or session. The model is still useful as long as you label it honestly and use it consistently rather than pretending it proves causality.