Revenue Attribution for SaaS: Which Channels Bring Paying Customers
Counting signups by channel tells you where traffic comes from. Counting revenue tells you where customers come from. How to connect a payment to the visit behind it, and how to handle renewals, upgrades, and refunds.
5 min read
Most attribution reports stop at the signup or the lead. That is the easy part to measure, and it can point you the wrong way. A channel that brings a thousand free signups and three customers looks better than a channel that brings fifty signups and ten customers, until you count the money.
Revenue attribution carries the source through to the payment.
Three Things Have to Connect
- The source of the visit. Where the person came from: a search, a campaign link, a referral.
- The identity. The moment an anonymous visitor becomes a known person or account.
- The payment. The charge in your billing system.
Each link can break. The guides that rank for this topic mostly describe attribution through a CRM, where a salesperson marks a deal as won. For a product people buy with a card, the payment happens in a billing system, and the link you have to build is between a browser session and a charge.
Where the Chain Breaks
At checkout. If payment happens on a hosted checkout page on another domain, the visitor's session does not follow them there unless you pass an identifier along. This is the most common reason revenue shows up with no source.
Between people. In a company, the person who found you is often not the person who enters the card. Attributing at the account level fixes this: the payment belongs to the company, and so does the first visit from anyone there.
Over time. A trial that converts after sixty days may have outlived the cookie that remembered where the visitor came from. Store the source on your own records at signup, not only in the browser.
Subscriptions Need a Few Decisions
A one-time sale is one event. A subscription is many. Decide in advance how to count them. There is no standard for these choices, and we did not find an independent reference that sets one, so the rules below are our suggestions:
- Renewals. Give them the same source as the first payment. The channel that brought the customer brought the renewals too. Then lifetime revenue by channel adds up.
- Upgrades and expansion. Same account, same original source. Report expansion separately as well, because it usually reflects the product and not marketing.
- Refunds. Subtract them from the source of the original sale. A channel with high refunds should look worse.
- Annual and monthly plans. An annual payment makes one month look large. Compare channels over a long enough period for that to even out.
What matters is that you pick a rule and keep it.
Fix the Attribution When the Payment Happens
If a customer's source can change after they pay, your reports for last quarter will change every time you open them. Record the first and last touch on the payment itself at the moment it happens, and leave it alone.
Reading the Report
With revenue by channel in front of you, look at four things:
- Revenue per channel, not signups per channel.
- Number of paying accounts per channel. One large customer can make a channel look better than it is.
- Revenue per account by channel. Some channels bring bigger customers.
- How much revenue has no source. If it is more than a small share, fix tracking before drawing conclusions.
Be careful with small numbers. If a channel has four customers, one more or one fewer changes the picture. Look at a quarter or longer before moving budget.
How Leapio Fits
Leapio records revenue in the same place as the rest of your analytics. Connect Stripe with a read-only connection, or record payments from your own code. Passing the visitor's Leapio ID in your checkout metadata ties a payment to the visit behind it. Without it, Leapio links the payment to a company by the customer's email domain. Revenue rolls up to the account, attribution is fixed at payment, and refunds net against the original sale. It is available on every plan. See Revenue Tracking and Attribution.