Revliu – Multi-touch attribution from acquisition to revenue

Hacker News

Share card

Revliu – Multi-touch attribution from acquisition to revenue

I’m a founder and I just built RevliI’m a founder and I just built Revliu. After building several products, I always wanted to understand how my customers were actually finding me. Which campaign brought them in, which source they came from, and what their full journey looked like. There are already tools for this, but one problem I kept running into is that they often stop at first touch or last touch. That’s why I built Revliu around multi-touch attribution and the full customer journey. As soon as someone lands on your website, Revliu gives them an anonymous ID and starts tracking their journey. Once they sign up, that journey can be connected to the actual customer. From there, you can see if they’re on a trial, how often they come back, how many sessions they open, and eventually when they pay. For me, this also makes it easier to talk to that user and understand why they decided to move forward at that specific moment. Today, Revliu tracks acquisition sources, returning visitors, sessions, touchpoints, and revenue. Instead of just knowing that a campaign got a certain number of impressions, I want to know how much money it actually brought in. Impressions are not really what I care about. The app itself is pretty simple. The main page gives you an overview of revenue by source. Traffic shows visitors, their journey, and their sessions. Campaigns shows the acquisition funnel. For a SaaS, that can be visitor → lead → trial → paying customer. For an online store, it can simply be acquisition → purchase. Customers lets you look at each customer individually, see their touchpoints, where they came from, their journey, and when they bought. The technical side is simple in principle. It starts with an anonymous visitor who gets an ID. We keep track of their visits and touchpoints. When they sign up, that anonymous journey is connected to the customer. Stripe is connected as well, so when the customer pays, the revenue can be linked back to the same journey. The goal is basically to connect acquisition → visits → signup → customer → revenue. Right now, the app is still in its first phase. I haven’t built all the integrations I want yet. What I want to build next is something that does more than just show data. If someone leaves their email but never finishes signing up, comes back several times without buying, or shows real interest without converting, I want to use that information to try to recover that potential customer. The idea would be to reach them again by email or, depending on the integrations, through other channels like LinkedIn. That’s why I still see the app as limited today. I first want to test this attribution part and see if there’s real traction around the problem before building everything else. The part I’m really interested in for the future is revenue recovery. By combining it with AI, the goal would be to adapt to different customers, understand which ones are hesitating, and do more than just display data. I want the data to actually do something inside the product. And I’d really like to know how you’re handling this today. Coding has become much easier than it used to be, but the difference between a good product that sells and a good product nobody uses often comes down to marketing and distribution. I’d really like your feedback on Revliu, the way I’m approaching the problem, and what you would do differently.