Why revenue-first analytics
Visitors are a means, not the goal. Here's what changes when every source, page and campaign in your analytics carries a revenue number.
Sunny Bundel2 min readAnalytics tools grew up around advertising, where the visit was the product. For a business that sells something, the visit is only the start. Measuring it as if it were the end leads to predictable mistakes.
Traffic is a proxy, and proxies drift
Visitors, bounce rate and time on page are proxies for “this is working”. They correlate with revenue sometimes, but the correlation is weakest exactly where decisions are hardest: comparing channels with very different audiences.
Say a viral post brings 5,000 visitors and one customer, while a niche newsletter brings 150 visitors and four customers. By traffic, the post won by a mile. By revenue per visitor, the newsletter is many times better, and it's the one worth repeating.
Revenue per visitor is the comparison you want
Total revenue by channel tells you where money came from. Revenue per visitor tells you how good each channel's traffic is, independent of its size. That's the number to look at when deciding where to spend the next hour or dollar.
| Question | Traffic-first answer | Revenue-first answer |
|---|---|---|
| Which channel is best? | The one with the most visitors | The one with the highest revenue per visitor, at enough volume to matter |
| Which post should I update? | The most-read one | The one whose readers convert |
| Did the launch work? | We had a spike | It brought N customers and $X, with this many still in trial |
- Question
- Which channel is best?
- Traffic-first answer
- The one with the most visitors
- Revenue-first answer
- The one with the highest revenue per visitor, at enough volume to matter
- Question
- Which post should I update?
- Traffic-first answer
- The most-read one
- Revenue-first answer
- The one whose readers convert
- Question
- Did the launch work?
- Traffic-first answer
- We had a spike
- Revenue-first answer
- It brought N customers and $X, with this many still in trial
Why it has to be joined, not side by side
Looking at your analytics in one tab and your payments in another doesn't answer these questions, because nothing connects a given payment to the visit before it. The join is the hard part, and it needs evidence:
- an id passed from the visit into the checkout (the most reliable),
- the checkout id seen on your own thank-you page,
- or the customer's email, if you identify signed-up users.
Trakily uses all three, strongest first, and retries unmatched payments as new evidence arrives. The revenue docs explain each one.
What attribution can't tell you
Attribution credits a payment to the visit that led to it. It can't see the podcast someone heard before typing your URL, or the friend who recommended you. Treat channel revenue as a strong signal for comparing channels you can measure, not as a full account of why people buy. Customer journeys help here: they show every visit before a payment, not just the last one.
Trying it
If you already take payments through Stripe or another supported provider, connecting it takes a minute and imports your history. The guide Track revenue by channel with Stripe in 5 minutes walks through it.
Trakily shows which channels bring paying customers, not just visitors. Start a 14-day free trial; no card needed.